Accessibility statement
Last reviewed 29 September 2026
What RailPilot does today to work with screen readers, zoom and other assistive technology, what we have not finished, and how to tell us when something gets in your way.
Our commitment#
RailPilot is built to make rail travel less stressful. A companion that tells you which train you are on, and whether you will make your connection, in plain language, helps most the people for whom that uncertainty is hardest. That includes blind and low-vision passengers, and anyone who finds unfamiliar journeys stressful. We want RailPilot to work well with assistive technology, and we treat problems that get in the way of that as bugs.
What works today#
- Plain-language journey updates. You do not need to read a diagram or a departure board to follow your journey.
- Screen readers speak live updates on the journey screen. Each new instruction is read out once, when it changes, and waits for your screen reader to finish what it is saying. This works while the journey screen is open. A locked phone or a page in the background will not speak.
- Buttons that show only an icon, such as share and close, have spoken labels. Copying a share link is confirmed out loud.
- You can move through the app with a keyboard, and the focused control is clearly outlined.
- Light and dark themes that follow your device setting.
- Tube line names sit on the line’s own colour, with black or white text picked by the standard contrast formula.
- Pinch and browser zoom are never blocked.
- Standard web markup (real buttons, headings and links), so assistive technology has something meaningful to work with.
- A self-hosted typeface with clear, evenly spaced numerals for times, so columns of times line up. It does not depend on a third-party font service.
- No autoplaying audio and no flashing content.
- If your device is set to reduce motion, sliding and sweeping animations stop. A few status dots still fade gently in and out (see known issues).
Known issues#
These are the problems we know about. We will update this list as we fix them.
- We have not yet tested every screen from start to finish with VoiceOver on iPhone and TalkBack on Android. That covers choosing a destination, the list of trains and live tracking. Parts of the first two screens may not read well.
- Most text is set at fixed sizes. A larger default text size in your browser settings may not make it bigger. Pinch or browser zoom will.
- We have not checked the contrast of every colour on every screen against a published standard. Only the tube line colour chips are checked automatically.
- With reduce motion turned on, some small status dots still fade in and out slowly. They do not move or flash.
- We have not tested how pages reflow at very high zoom. The bar fixed to the bottom of the screen may cover content.
How we test, and what we claim#
We have not yet tested the whole journey with VoiceOver and TalkBack. Until that testing is done, we are not claiming that RailPilot meets any level of the Web Content Accessibility Guidelines (WCAG). When the testing is done, we will update this page with the date and the results.
Tell us what isn’t working#
If something is hard or impossible to use with the tools you rely on, please tell us. It helps us fix the right things first. Email us at:
It helps to include:
- what you were trying to do
- the phone or computer, and the assistive technology, you were using
- what went wrong.
You do not need to include all of this. A short description is enough to start.
What happens next
We aim to reply within 5 working days and will prioritise problems that stop you completing a journey.
Something here unclear or out of date? Tell us.