Accessibility Certified – Home

Industry · Passenger transport and mobility

Ticket, seat, connection: bookable by every passenger

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.

A woman on a sunlit street looks closely at the smartphone she holds in both hands.

What the EAA covers in passenger transport

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

Does the EAA apply to you?

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.

Who are your customers?
How big is your company?

A first orientation, not legal advice. Nothing is stored.

Where passengers get stuck online

Patterns we find in almost every journey planner and booking flow.

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.

Date and time pickers

Calendar widgets that ignore the keyboard, days without an accessible name, and no way to simply type the date.

Results and timetables

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.

Seat and cabin maps

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.

Hold timers and payment

The countdown on a reserved seat runs out with no warning and no way to extend it. Add picture puzzles and embedded payment frames.

E-tickets and disruption notices

Tickets sent as an image or untagged PDF, and platform changes or cancellations in banners that vanish or grab the focus.

The criteria that get passengers on board

  • 2.1.1Keyboard

    Seat map, calendar and suggestion list must all work with a keyboard, all the way to payment.

  • 1.4.1Use of Color

    Delays, cancellations and taken seats must not rely on colour alone. Add text or a named icon.

  • 4.1.2Name, Role, Value

    Custom comboboxes and seat buttons need a name, role and state, such as “Seat 42, window, available”.

  • 4.1.3Status Messages

    “12 connections found” or “Train cancelled” must reach screen reader users without moving their focus.

  • 2.2.1Timing Adjustable

    When a reservation is about to expire, people need a warning and the chance to extend it.

  • 2.5.7Dragging Movements

    New in WCAG 2.2: if a map or time slider only works by dragging, there must be a simple click or tap alternative.

How we test your booking flow

  1. Agree the journeys

    Find a connection, book a ticket, pick a seat, retrieve the ticket, read a disruption notice: together we decide which journeys the audit covers.

  2. Scan the public pages

    Timetables, fares, accessibility information and help pages are checked automatically. The scanner never books or submits anything.

  3. Book by hand

    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.

  4. Report and certificate

    Every finding with its location and a fix hint. When nothing fails, the certificate follows, with a public verification page for the tested scope.

What the law says, and what it leaves open

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.

Frequently asked questions

Do you test our app?

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.

What about ticket machines?

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.

Our booking engine comes from a supplier. Who is responsible?

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.

Live data changes all the time. What does a certificate say?

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.

Related