Accessibility
Accessible to everyone.
LopoRail aims to meet WCAG 2.2 level AA. Rail information should be usable by everyone — including people using screen readers, keyboards, magnification or reduced-motion settings.
What we do
Built in, not bolted on.
Keyboard first
Every control is reachable and operable by keyboard, with a visible focus state and a skip-to-content link.
Screen-reader support
Semantic landmarks, labelled controls, live regions for status, and a logical heading order on every page.
Contrast in both themes
Text and controls are contrast-checked against WCAG AA in light and dark themes; colour is never the only signal.
Motion & zoom
Animation respects prefers-reduced-motion, and layouts reflow without loss of content up to 400% zoom.
Plain language
Headings, labels and error messages are written to be understood, with images given meaningful alternative text.
Tested on the way out
Contrast and layout-overflow checks run automatically as part of every release, across all pages.
Known limitations
Where we are still working.
We would rather tell you than have you find out — these are the areas we know are not perfect yet.
- A few third-party embeds (maps, live widgets) are owned elsewhere and may lag behind our own standard.
- The "What's That Train?" listening room is sound-based; it always shows a written suggestion and a path to confirm by text, so it is usable without hearing the audio.
- Some historic archive tables and long timetables are dense; we are improving their structure and labelling.
Everyone should be able to read the railway.
If something here does not work for you, that is a bug — please tell us and we will fix it.
Contact usHelp keep this directory complete.
Know a line, place or listing we’re missing — or spotted a mistake? Add it in a minute.