Directive (EU) 2019/882 · Annex I, section IV(c)
Booking a journey is a named service, and the machine at the station is a product
Air, bus, rail and waterborne passenger transport services appear in the directive, together with the websites, apps, electronic tickets and interactive self-service terminals used to deliver them. For an airline, an operator or an online travel agency, that means two regimes running side by side and one customer journey crossing both.
What is covered, and what is carved out
The directive covers the service elements: websites, mobile applications, electronic tickets and ticketing services, delivery of transport service information including real-time travel information, and interactive self-service terminals located within the Union. Urban, suburban and regional transport services have a narrower scope: for them only the self-service terminals are covered.
Separate passenger rights rules on assistance for persons with reduced mobility continue to apply on their own terms. Meeting one does not discharge the other, and a complaint about a booking barrier can travel down both routes at once.
Where a booking flow fails
| Step | Typical barrier |
|---|---|
| Date selection | Calendar widget that cannot be operated from the keyboard |
| Fare comparison | Price grid announced as a wall of numbers with no headers |
| Seat map | Drag-only interaction, seats announced only as letters and colours |
| Passenger details | Autofill blocked, errors shown by colour alone, session timing out mid-form |
| Payment | Third-party iframe stealing focus, one-time code with a short timer |
| Ticket delivery | PDF with no text layer, QR code with no alternative reference |
| Disruption | Real-time updates in a live region no screen reader announces |
The self-service terminal is a product file
Machines at stations, airports and stops are covered as products. That means a conformity assessment, technical documentation under Annex IV, an EU declaration of conformity and CE marking, not a published statement. The obligation follows whoever places the machine on the market and whoever brands it, so an operator that buys terminals and puts its own name on them takes on manufacturer duties.
Real-time information is part of the service
Delays, platform changes and cancellations are exactly the information a passenger with a disability cannot afford to miss, and they are usually the least tested part of a product because they only appear when something goes wrong. Test them deliberately, with the screen reader running, on a device, using the same status mechanism the live site uses.
Agencies, aggregators and who answers
An online travel agency provides a service of its own: the search, the booking and the ticket it issues. It cannot point at the carrier for a barrier in its own funnel, and the carrier cannot point at the agency for a barrier in the check-in it runs. In a complaint each provider answers for what it controls, and the passenger does not care which of you owns the screen.
Documents passengers actually receive
Booking confirmations, boarding passes, fare conditions and disruption notices are part of the service. Sending them as images or as untagged PDFs is a common and avoidable failure, and it is the one a passenger notices at the gate rather than at home.
What the statement should say for a transport provider
The scope, naming the website, the app, the ticketing service and any terminal estate covered elsewhere by a technical file. The standard, EN 301 549 with WCAG 2.2 AA and clause 11 where an app is included. How a passenger using assistive technology completes a booking end to end. The known limitations with a reason and a horizon. The contact point that reaches a human, with the response time you actually keep.
Kiosks, gates and the physical edge of the service
The digital journey ends at a machine: a check-in kiosk, a gate reader, a ticket validator. Those are products with a technical file, but the passenger does not experience them separately from the app that sent them there. Test the handover deliberately, the QR code that has to be scanned, the reference number that has to be read aloud, the screen that times out while someone is finding it.
Where the machine belongs to an airport or a station operator rather than to you, say so in the statement and name the boundary. Buyers and authorities accept a clear boundary; they do not accept silence.
Group bookings, assistance requests and refunds
Three flows that carry real complaints and that almost never appear in a test scope. Group booking forms multiply every field problem by the number of passengers. Assistance requests are the one form where the customer is, by definition, a person with a disability, and it is frequently the least usable page on the site. Refund and change flows arrive at the worst moment, often on a phone, in a station, with a screen reader.
Include them deliberately. They are cheap to test alongside the main funnel and expensive to explain when a regulator asks why a disability assistance form was unusable.
How we test a travel product
We book a real journey end to end with the screen reader on, at the largest system font, in both themes, and we run the disruption path deliberately rather than waiting for it. Terminals are assessed separately against the product requirements, with the Annex IV file assembled from the same test. See the product file and the app side.
Questions we get before buying
Are all transport operators covered?
Air, bus, rail and waterborne passenger transport are covered for their digital services. Urban, suburban and regional services are covered only for self-service terminals.
Does this replace passenger rights rules on assistance?
No. Assistance obligations for persons with reduced mobility continue separately, and both can be raised in the same complaint.
Our terminals were bought from a supplier. Who owes the file?
The manufacturer, unless you place the machines on the market or market them under your own name, in which case the duty is yours.
Is an e-ticket covered?
Yes. Electronic tickets and ticketing services are named, which includes how the ticket is delivered and read.
What about our loyalty programme?
If it is part of the booking or check-in journey, test it. Barriers there produce the same complaints as the funnel itself.
Do we have to test the disruption flow?
Yes, and it is where most providers have never looked. Live regions that never announce are a frequent finding.
Are we exempt as a small operator?
Service microenterprises under 10 staff and up to 2 million euro are exempt for services. Terminals as products are not covered by that exemption.
Who is responsible, the airline or the agency?
Each for what it controls. The agency answers for its funnel, the carrier for check-in and for its own site and app.
Does the statement cover the terminals too?
Name them and point to the technical documentation. Products carry a file, not a published statement.
How long does a booking journey test take?
Five business days from your scope answers for the core journey. Terminal estates are quoted after a first look.
Test the whole journey, disruption included
Search, booking, payment, ticket and live updates, on a real device, with the record signed and verifiable.