Accessibility

Our commitment

We build Stratatouille to the WCAG 2.1 Level AA standard. Accessibility is a first-class goal, not an afterthought — but we’re honest that we’re an early-stage product still working toward full conformance. This page says plainly where we are.

Conformance status

Partially conformant. Most of the app meets WCAG 2.1 AA; some known issues remain (below). We have not yet had an independent third-party audit, so we describe this as a self-assessment, not a certification.

What’s in place

• Semantic HTML and a logical heading structure.
• Keyboard-operable interfaces, with visible keyboard-focus indicators — with the gaps below.
• Labeled form controls, with errors announced to assistive technology.
• Never color alone: in the comparison view, every lane pairs its color with a distinct shape marker, so lanes are distinguishable without relying on color.
• A screen-reader text-table equivalent of the visual timeline, so the same information is available non-visually.
• A committed, repeatable automated accessibility check (pa11y-ci with axe and HTML_CodeSniffer) covering every public page.

Known limitations (being addressed)

• No independent audit yet. Our conformance is self-assessed.
• The interactive comparison view hasn’t had a full audit — it relies on keyboard focus and its text-table equivalent, and we’re still refining screen-reader parity.
• Keyboard panning of the timeline isn’t implemented yet — you can zoom, fit, and tab between events, but not pan by keyboard.
• Mobile accessibility of the dense comparison view hasn’t been fully verified.
• In-chart text contrast. In the dense comparison timeline, some small labels fall below the contrast minimum at certain zoom levels. The same information is available at full contrast in the screen-reader text-table equivalent — the accessible path for the visualization — and we’re improving the in-chart labels over time.
• Homepage banner. The large decorative tricolor banner has one color pairing slightly below the contrast minimum for large text. It’s decorative — the page’s real heading is exposed to assistive technology — and it’s on our list to bring fully into line.

How we test

We combine automated tooling with manual keyboard checks. A committed, repeatable sweep (pa11y-ci with axe + HTML_CodeSniffer, run with bun run a11y) covers every public page: our content and legal pages pass it, with the homepage banner and the interactive timeline the documented exceptions noted above. The signed-in app is checked manually. Automated tools are valuable but catch only a portion of possible issues — they don’t fully cover keyboard journeys, focus order, or screen-reader experience — so a passing scan is a floor, not a guarantee. (Last run 8 July 2026.)

Report a problem

Found a barrier? Please tell us — it genuinely helps. Email hello@stratatouille.com with the page and what went wrong, and we’ll prioritise it.