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.
• Full keyboard operability, with visible keyboard-focus indicators.
• Labelled form controls, with errors announced to assistive technology.
• Never colour alone: in the comparison view, every lane pairs its colour with a distinct shape marker, so lanes are distinguishable without relying on colour.
• A screen-reader text-table equivalent of the visual timeline, so the same information is available non-visually.
• Automated accessibility checks (axe) run against the site as part of our process.

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.

How we test

We combine automated tooling (axe / pa11y) with manual keyboard checks. Our public pages currently pass an automated axe sweep (last run 4 July 2026); 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.

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.