Statement dated 10/07/2026

Accessibility is part of the route.

The aim is WCAG 2.2 AA. This early pilot has not yet had an independent accessibility audit, so it should not claim full conformance.

What has been designed in

  • Semantic headings, landmarks and labelled controls.
  • Visible keyboard focus and touch targets of at least 44×44px.
  • Light and dark themes with text contrast considered in both.
  • Reduced motion when your device requests it.
  • Route information presented as text, not only through colour or maps.

Known limitations

The finder and full route detail currently use JavaScript. Essential summaries remain visible without it, but the complete interactive experience requires JavaScript. Forms are not yet connected.

Testing still required

Before public launch the key flow should be checked with keyboard-only navigation, VoiceOver, 200% zoom and an automated axe or Lighthouse pass at 360px.

Report a barrier

A dedicated accessibility contact will be published before the public pilot. Until then, report problems through the same contact channel that supplied your test link.