Our commitment
[Replace with attorney-reviewed text before launch.] We design and build this website with the goal of meeting Web Content Accessibility Guidelines (WCAG) 2.2 at the AA level. We treat accessibility as part of the build, not a feature added afterward — semantic HTML, keyboard-operable interactions, visible focus states, alt text on meaningful images, and color contrast that clears AA pairs across the site.
The goal-oriented language is deliberate. We don't claim full conformance because conformance requires sustained testing and our testing is sampled, not exhaustive. We hedge so the statement is accurate, not aspirational.
How the site is built
- Semantic HTML5 landmarks (header, main, footer, nav) on every page.
- Single H1 per page; heading hierarchy preserved without skips.
- Visible focus indicators on every interactive element via :focus-visible with a 2px outline at 4px offset.
- Skip-link as the first focusable element of every page, targeting the main landmark.
- Alt text on meaningful images; decorative images use alt="".
- Forms use visible labels (not placeholders), aria-describedby for help and error text, and error messages that name the field, what is wrong, and how to fix it (WCAG 3.3.3).
- Mobile menu uses focus trap, escape-to-close, and returns focus to the trigger on close.
- prefers-reduced-motion is honored — every animation and transition collapses to a no-op under reduced motion.
- Color contrast meets AA on every foreground/background pair actually used (verified pair list lives in the design-direction reference).
Testing
[Replace with attorney-reviewed text before launch.] We test with axe DevTools on every major page before launch and again before significant content changes. We test keyboard navigation manually. We sample screen-reader output (NVDA on Windows, VoiceOver on macOS) on the homepage, contact form, and one work-detail page.
Sampled testing means we may miss issues. If you find a barrier, please let us know.
Known limitations
[Replace with attorney-reviewed text before launch.] At launch, we know of no specific accessibility barriers. This section will list any known issues we are working to resolve, with target resolution dates.
Report a barrier
If you encounter an accessibility barrier on this site, email hello@marenholloway.example. Tell us:
- The page URL.
- The browser and screen reader (or other assistive technology).
- What you were trying to do.
- What happened instead.
We aim to acknowledge accessibility reports within i reply within 2 business days and resolve fixable issues as quickly as the fix allows.