Accessibility

The target

WCAG 2.2 Level AA, and the honest position is that we test a subset of it automatically on every build rather than claiming conformance we have not audited.

What is checked automatically, on every page

• Every page has one h1, and headings descend without skipping a level.
• Every page has a skip link, a main landmark and a language declared.
• Body text and interface text meet the 4.5:1 contrast ratio in both the light and dark palettes, computed from the tokens rather than eyeballed.
• Every form control has a label, every link has discernible text, and every generated illustration carries a role and an accessible name.
• Nothing relies on colour alone to convey state.
• No page overflows horizontally at 390 CSS pixels, tested in a real browser.
• prefers-reduced-motion disables every transition and hover movement.

What is not yet done

• No audit with a screen reader by a person who uses one daily. That is the gap that matters most and cannot be automated away.
• No keyboard-only walkthrough of the planner by an independent tester.
• No accessibility information about the places themselves — step-free access, hearing loops, accessible toilets. The planner already tells you it cannot take account of accessibility needs; the honest fix is data we do not have yet, and inventing it would be worse than the gap.

If something here excludes you

That is a defect, not a preference, and we would rather hear it bluntly. How to reach us →