Accessibility
This site is built to WCAG 2.2 Level AA. Below is what that means in practice, including the parts we have not finished, because a statement that only lists successes tells you nothing about what it left out.
What we build to
WCAG 2.2 Level AA. We target 2.2, not the older versions most regulations name, because WCAG is backward compatible: meeting 2.2 AA also meets the WCAG 2.0 AA that Section 508 references and the 2.1 AA referenced by the Department of Justice rule for state and local government and by EN 301 549 in Europe.
We do not describe the site as “ADA compliant”. The Americans with Disabilities Act sets no technical standard for private websites, so the phrase would imply a certification that does not exist. WCAG 2.2 AA is a target we can state precisely and you can check.
How we test
Automated accessibility checks run on every build, across desktop and mobile breakpoints, and a failure stops the build. Nothing reaches review broken. Color contrast is checked at the design-token level, so a passing color cannot quietly become a failing one on a differently shaded section.
Automation is not enough on its own. Published research puts automated coverage at roughly 57 percent of issue instances, and the ones it misses skew severe: keyboard traps, focus order, alt text that exists but says nothing. So a person also walks each page by keyboard and inspects the accessibility tree, which is what a screen reader reads from.
What we have not done yet
A published VPAT accessibility conformance report. If your organization needs one for procurement, ask and we will tell you honestly where we are.
A listening session with a real screen reader. On 6 August 2026 every page was checked for reflow at 400 percent zoom, walked by keyboard, and had its accessibility tree inspected, which is the structure a screen reader reads from. Two problems were found and both are fixed: a scrollable table a keyboard user could not reach, and buttons that slid underneath the sticky header when reached by keyboard. But nobody has yet sat down with NVDA or VoiceOver and listened to these pages, and inspecting the structure is not the same as hearing the result.
Accessibility is a practice, not a state. While building this site we introduced two color-contrast failures in a single afternoon and caught them with the automated gate, and a manual pass then found a keyboard problem the automated gate could not see by construction. Any page claiming to be finished with accessibility is describing a moment, not a property.
Tell us when we get it wrong
If something on this site is difficult or impossible to use, we want to know, and a description of what happened is more useful to us than a standards citation. Get in touch and we will tell you what we can fix and when.