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. Accessibility is built in from the first page: semantic HTML, keyboard-operable interactions, visible focus states, alt text on meaningful images, and color contrast that clears AA pairs across the site.
We describe this as a goal because we test a sample of pages after each change. Claiming full conformance would take ongoing testing of every page, so this statement only says what we have checked.
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 used on the site (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 [email protected]. 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 two business days and resolve fixable issues as quickly as the fix allows.