Accessibility

Finding, comparing, opening and sharing a route must work with a keyboard and assistive technology, at narrow widths and high zoom, and without a map or photograph. Important instructions and route details stay in ordinary page content.

Editorial photographs are decorative context. Their empty alternative text avoids duplication, while headings, actions and journey stages remain ordinary semantic content on contrast-controlled surfaces.

Maps will be secondary and expandable. A provider failure must leave the route list and detail usable.

Release checks will cover keyboard-only use, focus order, visible focus, zoom and reflow, reduced motion, colour contrast and representative screen-reader journeys. Automated checks support this work but do not replace hands-on review.

The compatibility target is the latest two desktop releases of Chrome, Edge, Firefox and Safari, plus iOS Safari 16 and newer and Android Chrome 110 and newer. Other or weaker devices should still receive the functional static, list-first experience.

A staffed accessibility feedback channel has not yet been published. One will be added before public release so reports can be acknowledged, tracked and answered rather than sent to an unattended address.