From, to and stop search
Autocomplete fields whose suggestions a screen reader never announces, or that only respond to a mouse. We check that role, state and the number of matches come through.
Applies to this website and is saved in your browser.
Good to know: this website is built to work well without these switches. They are personal preferences only: they do not change the code and do not replace accessibility, even though overlay widgets promise that. Why overlays do not help · Our accessibility statement
Tip: zoom (Ctrl/Cmd and +), contrast and read-aloud can also be set in your browser and operating system, then for every website.
Plain EnglishIndustry · Passenger transport and mobility
A passenger who cannot work the calendar with a keyboard, or who sees a delay only as red text, is left on the platform. We test your journey planner, booking flow and live travel information the way people with screen readers, zoom or a keyboard use them.

The European Accessibility Act does not cover a transport operator as a whole. It names certain elements of air, bus, rail and waterborne passenger transport services (Article 2(2)(c) of Directive (EU) 2019/882): websites, mobile services including apps, electronic tickets and ticketing services, transport information including real-time travel information, and interactive self-service terminals in the EU.
For urban, suburban and regional transport, only the last of these applies: interactive self-service terminals such as ticket machines. For the other services, Annex I adds information duties: on the accessibility of vehicles, stations and assistance, on smart ticketing, real-time timetables, disruptions and connections, and on things like station staffing and lifts that are out of order. Checked on 10 November 2026.
Each member state applies these rules through its own law, in Germany the BFSG for example. Not sure whether you are covered? The two questions below take you straight to the EAA check.
Two questions, one answer
Your industry is already selected. Answer two questions and the EAA check shows an assessment, the reasons and next steps. You can change every answer there.
Patterns we find in almost every journey planner and booking flow.
Autocomplete fields whose suggestions a screen reader never announces, or that only respond to a mouse. We check that role, state and the number of matches come through.
Calendar widgets that ignore the keyboard, days without an accessible name, and no way to simply type the date.
Departure, arrival, changes and duration need a structure people can move through. A delay shown only as a red or struck-through time is lost on many passengers.
Graphical seat maps often work only with a mouse and tell free, taken and selected apart by colour alone. We check for an equivalent way to choose.
The countdown on a reserved seat runs out with no warning and no way to extend it. Add picture puzzles and embedded payment frames.
Tickets sent as an image or untagged PDF, and platform changes or cancellations in banners that vanish or grab the focus.
Seat map, calendar and suggestion list must all work with a keyboard, all the way to payment.
Delays, cancellations and taken seats must not rely on colour alone. Add text or a named icon.
Custom comboboxes and seat buttons need a name, role and state, such as “Seat 42, window, available”.
“12 connections found” or “Train cancelled” must reach screen reader users without moving their focus.
When a reservation is about to expire, people need a warning and the chance to extend it.
New in WCAG 2.2: if a map or time slider only works by dragging, there must be a simple click or tap alternative.
Find a connection, book a ticket, pick a seat, retrieve the ticket, read a disruption notice: together we decide which journeys the audit covers.
Timetables, fares, accessibility information and help pages are checked automatically. The scanner never books or submits anything.
A reviewer walks the flow with keyboard and screen reader, using a test account and test payment method from you. We never buy real tickets.
Every finding with its location and a fix hint. When nothing fails, the certificate follows, with a public verification page for the tested scope.
The rules apply to services provided to consumers after 28 June 2025. Micro-enterprises that provide services are exempt: fewer than 10 employees and an annual turnover or balance sheet total of no more than EUR 2 million.
Article 5 of the Directive links it to the EU passenger rights regulations: services that meet their requirements on accessible information and on information about accessibility are deemed to meet the corresponding requirements of the Directive. That presumption concerns those information duties.
One question stays open for local transport: whether selling urban or regional tickets online counts as an e-commerce service. The Directive does not say so expressly; recital 43 states that the e-commerce obligations apply to the online sale of any product or service. Ask a lawyer about your case. More in our law overview.
We test everything that runs in a browser: website, web app, booking flow and ticket retrieval on the web. We do not currently test native iOS or Android apps, and we issue no certificate for them. If your app shows web content, we can test that content.
Interactive self-service terminals are covered, even in local transport. Testing them is not part of our service, though: we test websites, web apps and PDF documents.
The rules address whoever provides the service to consumers. Whether that is you or your partner depends on your contracts; ask a lawyer if in doubt. We test what your passengers actually get and describe every finding so you can pass it on to your supplier.
It confirms the tested state on the test date: templates, controls and flows. The data changes, the templates stay. Monitoring scans regularly and tells you when a new release makes things worse.
Dashboards, customer areas, SPAs
Hotels, trips, tickets online
EAA check in five questions
Duties, deadlines, enforcement