Accessibility
What has been built in, what has been tested, and what has not. Written honestly, because an accessibility statement that overclaims is worse than none.
Last updated Fri, 23 October 2026
The standard we aim at
WCAG 2.2 level AA. We believe the site substantially meets it on its main routes, and the list below says exactly what has and has not been checked.
What is built in
- A skip link to the main content, and semantic landmarks on every page.
- One
h1per page and a heading order that does not skip levels. - Full keyboard operation — every control, filter, dialog and map station is reachable and operable without a mouse, with a visible focus ring.
- Reordering your LDN Line is done with buttons, not drag-and-drop. Dragging is never the only way to do anything here.
- Every diagram and route map has a list equivalent carrying the same links, and the list is the default below 768 pixels.
- State is never carried by colour alone: a selected filter also shows a marker, a saved item also changes its label, an urgent deadline also says how many days are left.
- Touch targets are at least 44 by 44 pixels.
- Form errors are announced, tied to their field, and focus moves to the first problem.
- Everything respects
prefers-reduced-motion: route drawing, parallax and reveal animations all stop, and state changes happen instantly instead. - Content does not depend on JavaScript to be visible. If the script fails, every section still renders.
- Text is real text, never an image of text, and the page is usable at 200% zoom and down to 320 pixels wide.
Images
Photographs carry descriptive alternative text. Decorative diagram elements are hidden from assistive technology; the diagrams themselves have a title and a description explaining what they show and pointing at the list view.
What has not been done
This is where most statements go quiet, so: the site has been checked by its builder with automated tooling and by keyboard, at the viewport sizes listed in the build notes. It hasnot been tested with a screen reader by someone who uses one daily, and it has not had a third-party audit. Those are the two things that would most improve it, and neither has happened yet.
There is no audio content on the site at present. When there is, every recording will be published with a transcript — that rule is enforced by the content schema, not by good intentions.
Tell us
If any part of this site is hard to use, pleasetell us through our contact form. We treat accessibility problems as corrections, which means they go to the front of the queue.