Accessibility

Last updated: August 25, 2026

We're targeting WCAG 2.1 Level AAacross Compass. This page states where that stands today, honestly: what's been checked, what's been fixed, and what we haven't verified yet.

What we've done

• Automated checks (eslint-plugin-jsx-a11y) run on every change, catching missing labels, invalid ARIA, and non-interactive elements with click handlers before they ship.
• The assessment's answer controls (multiple choice, this-or-that, and the 1–5 agreement scale) are built as labelled radio groups, reachable and answerable entirely from the keyboard, with arrow keys moving between options as expected for a radio group.
• Your report's results chart has a text equivalent read by screen readers — the same six scores the chart shows, not just a description of a shape.
• The site declares its language (lang="en") and has well-formed page titles throughout.

What we haven't verified yet

We have not completed a full manual audit, and we have not done a screen-reader pass with NVDA or VoiceOver. We haven't formally checked colour contrast across every token in both of the app's two design systems (the newer Compass components and the legacy assessment/report CSS), and checkout and sign-in haven't had a dedicated pass for error announcements or keyboard traps. We're not claiming AA conformance yet — we're telling you what we've checked so far.

Something not working for you?

If you use assistive technology and something on Compass doesn't work the way it should, we want to know. Email us at support@compass.appwith what you were trying to do and what happened — that report is the most useful audit input we can get.

This statement reflects the state of the codebase, not a third-party audit. Replace the placeholder contact email with a real one before relying on it in production.