Accessibility statement.
An independent practice selling accessibility services owes its visitors a clear statement about its own site. This is mine. I take it seriously, I update it honestly, and I want to know when I fall short.
My commitment.
What I’m trying to do on this site, and why.
Digital Dimensions is committed to making digitaldimensions.us accessible and usable to the widest practical audience, including people who use assistive technologies. I build this commitment into the design and development of the site itself — rather than treating it as a statement to be made after the fact — and I regard any failure to meet that commitment as a defect to be fixed, not a limitation to be lived with.
This commitment is both professional and personal. Selling accessibility services from an inaccessible site would be absurd. If a page here fails for someone using a screen reader, keyboard, magnifier, or any other assistive technology, I want to know — and I’ll fix it. This site serves as both my business presence and a demonstration of the accessibility standards I implement for clients.
Current conformance status.
The standard I target, and the honesty about where I am against it.
This site is designed and built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, published by the W3C. WCAG 2.2 AA is the technical standard most commonly referenced in U.S. accessibility regulations, and it is the baseline I work against for my own projects and for the work I deliver to clients.
The conformance status of this site is partially conformant, self-assessed against WCAG 2.2 Level AA as of the date above. “Partially conformant” means that most parts of the content conform fully to the standard, but there may be specific issues identified in the limitations section below that I am actively working to resolve.
| Standard | WCAG 2.2 Level AA |
|---|---|
| Status | Partially conformant, self-assessed |
| Assessment method | Automated scanning (axe-core, WAVE, Lighthouse) combined with manual review: keyboard-only traversal, screen-reader testing, cognitive and low-vision review |
| Last reviewed | |
| Review cadence | Quarterly, and whenever substantial new content or functionality is added |
What I’ve built in.
Specific accessibility measures applied to this site during design and development.
- Semantic HTML with correct heading hierarchy on every page
- Proper landmark regions (header, nav, main, footer)
- Skip-to-main-content link on every page
- Keyboard-navigable interactive elements
- Visible focus indicators throughout
- Text color contrast targeted at AA minimums or better
- Responsive layout reflowing cleanly to 320 CSS pixels
- Support for browser zoom up to 400% without content loss
- Animations respect
prefers-reduced-motion - Forms use associated labels and programmatic error handling
- Disclosure widgets (FAQ) built with native
<details>/<summary>for robust assistive-tech support - Descriptive link text; no bare “click here” or “read more”
- All decorative images are aria-hidden; meaningful images have descriptive alt text
- Language declared at the document level
- No auto-playing media; no content that flashes above threshold
Technical specifications.
What the site is built with, and which assistive technology pairings I test against.
Accessibility of this site relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your device:
- HTML (semantic markup)
- CSS (with
prefers-reduced-motionand high-contrast-mode support) - JavaScript (progressive enhancement; core functionality works without it)
- WAI-ARIA where it adds value beyond semantic HTML
These technologies are relied upon for conformance with the accessibility standards used. The site is tested with the following assistive technology pairings:
- NVDA with Firefox and Chrome (Windows)
- JAWS with Chrome (Windows) — periodic checks
- VoiceOver with Safari (macOS and iOS)
- TalkBack with Chrome (Android)
- Keyboard-only navigation across all tested platforms
- Browser zoom up to 400% and forced-colors mode
Known limitations.
Honest disclosure of areas I’m aware of and working on.
Despite my best efforts, some content on this site may not yet be fully accessible. I am actively working to improve the following areas:
- Case study imagery: As I add more detailed case study content with diagrams and technical illustrations, I am committed to providing comprehensive text descriptions and alt text for all meaningful visuals.
- Embedded third-party content: Where I embed scheduling tools or other third-party widgets, I select vendors based in part on their accessibility posture, and I will note any known limitations here.
- Document downloads: Any PDF or other documents I publish here will meet the same WCAG 2.2 AA standard as the site itself. If you encounter a document that doesn’t, please let me know.
If you encounter an issue that isn’t listed here, that’s exactly the kind of report I want to receive. It’s also a test case for how I handle such reports in my own practice.
If something doesn’t work.
If you experience any accessibility barrier on this site — anything at all — please tell me. I treat accessibility reports as bug reports: they get logged, prioritized, and worked on, and I reply to let you know what I’m doing and when.
When reporting, the most helpful information includes:
- The page or URL where you encountered the issue
- A description of what you were trying to do
- What happened instead, or where you got stuck
- The browser and assistive technology you were using (if relevant and known)
None of these are required; even a brief note is useful. You can reach me by any of the following:
I respond within one business day.
Email is my preferred channel — it gives me a clean record, and I can respond at length if your report needs investigation.
For the record.
The details an auditor, procurement officer, or curious visitor might want.
| Statement applies to | digitaldimensions.us and all subpages under this domain |
|---|---|
| Statement created | |
| Last reviewed | |
| Assessment approach | Self-evaluation with internal review. A formal third-party audit is a direction I’m open to as the site grows. |
| Feedback contact | jared@digitaldimensions.us |