[ ACCESSIBILITY ]
Accessibility statement
Conformance target
Trades Navigator targets WCAG 2.2 Level AA conformance across all routes. We aim higher where it costs nothing extra (AAA contrast on body text, 44 CSS px touch targets across the chrome, full WAI-ARIA combobox/listbox patterns), but the published conformance line is AA 2.2.
How we test
- axe-core across a 20-page sample on every audit run (
npm run audit:axe). - Design-token contrast against bg.page, bg.card, and bg.subtle on every defined token (
npm run audit:contrast), with a CSS-var ↔ design.ts parity check that fails the build on token drift. - Image dimensions + 320 CSS px reflow regression checks in CI.
- Manual screen-reader smoke tests (NVDA + Firefox on Windows, VoiceOver + Safari on iOS) against eight canonical flows on a quarterly cadence. Documented in
content/a11y-at-smoketest.md.
Known gaps
Honest list of what is currently below the AA bar and on a fix queue:
- Real-AT smoke-test cadence. Documented quarterly cadence is being established. First documented run is scheduled and tracked in
content/a11y-at-smoketest.md. - Forced-colors mode (Windows High Contrast). Some active/selected states rely on background tint; explicit forced-colors @media blocks are being added.
- Heading IDs in long-form content. Pre-hydration (no-JS) anchor links to in-page headings are being moved from client-side slugify to build-time generation.
Report a barrier
If a page is not usable with your assistive technology, your zoom level, your input method, or your color-perception profile, please tell us — we want to know. Contact email rolls out with the next release; this page will list it as soon as it is wired.
Last reviewed 2026-05-15. We re-publish this statement every quarter or when the audit surfaces a material change.