Our commitment
Accessibility Statement
We build for people who get let down by inaccessible things. Shipping an inaccessible website would be its own kind of answer, so we hold this site to the standard we'd want from anyone else.
Effective August 2026
Conformance target
This website targets WCAG 2.1 Level AA. We consider it substantially conformant. That's a claim we're willing to be held to, so here is what it actually rests on.
What we've done
- Color contrast is computed, not eyeballed. Every text and background pair in the design system was solved in the OKLCH color space to hit at least 4.5:1, and a script re-checks every pair on each build. A build that would ship failing contrast fails instead.
- Color is never the only signal. Access ratings carry a distinct dot shape as well as a distinct color, so they're still tellable apart without color vision.
- Real pages, real HTML. The site is statically rendered — every guide is an ordinary document with a correct heading order, not a client-side route swap. It works with JavaScript off.
- Full keyboard operation, with a visible focus ring on everything focusable, and a skip link.
- Interactive targets are at least 44×44 px (WCAG 2.5.8).
- Motion respects
prefers-reduced-motion— animation and smooth scrolling are switched off when you've asked for that. - Light and dark themes, both contrast-checked, following your system setting unless you override it.
- Text reflows to 320 px and scales to 200% without loss of content.
What we know is imperfect
Listing these is more useful than claiming they don't exist.
- The community forum runs on Discourse, third-party software we configure but don't control the internals of. Its accessibility is good but not identical to this site's, and its known issues are upstream.
- Guide content was written before this design system existed. The prose is sound, but a handful of guides use emoji in headings where a text label would read better on a screen reader.
- Per-dimension access ratings are unpopulated for most destinations. That's deliberate — we'd rather show an empty field than a guess — but it does mean the summary panel is less useful than it will eventually be.
- We have not yet had this site audited by a third party. We'd like to.
Assistive technology we test with
VoiceOver on macOS and iOS, NVDA on Windows, keyboard-only navigation, 200% browser zoom, and Windows High Contrast mode.
Reporting a barrier
If something here doesn't work for you, we want to know — and we'd rather hear about a small annoyance than have you assume it's not worth reporting. Email [email protected]. We aim to reply within two working days and to tell you plainly whether we can fix it and when.
If you'd like a page's content in another format, ask and we'll send it. That includes any of the destination guides.