The European Accessibility Act and passenger transport: what is covered, and where audio actually helps
Directive 2019/882 covers transport websites, apps, e-tickets and terminals since 28 June 2025. What falls in scope, what falls out, and why an audio version helps without ticking the compliance box on its own.
Passenger transport is one of the sectors the European Accessibility Act names explicitly, and one of the most misread. You will see claims that "transport has to make everything accessible" or, the other way round, that "transport is exempt." Both are wrong. Directive (EU) 2019/882, applicable since 28 June 2025, targets specific digital elements of transport services, with equally specific exceptions. Here is what is covered, and where an audio version of your content is genuinely useful without pretending, on its own, to bring a service into compliance.
What the directive targets in transport
The European Accessibility Act covers air, rail, bus and waterborne passenger transport services. It does not regulate the vehicles themselves, but the digital touchpoints through which a traveller plans and completes a journey. In practice, the scope includes: websites, mobile device-based services (including apps), electronic tickets and electronic ticketing services, and the delivery of transport service information, including real-time travel information. Interactive self-service terminals, such as ticketing or check-in machines, are also covered, except where they are installed as integral parts of a vehicle, aircraft, ship or rolling stock.
It follows the shape of a journey: wherever a traveller looks up a schedule, books, pays, receives a ticket and follows a trip, the interface has to be usable by a person with a disability. The reference standard is digital accessibility (the criteria carried by the European standard EN 301 549, which builds on WCAG), not a list of mandated features.
What falls out of scope, and why it matters
Not every line sits under the same rules. Urban, suburban and regional transport services benefit from exemptions on most elements: for them, it is mainly interactive self-service terminals that remain in scope. A municipal bus network is therefore not held to the same digital obligations as a national rail or air carrier. Microenterprises providing services are also exempt. Knowing this boundary avoids two symmetrical mistakes: thinking you are out of scope when you are not, and over-investing in a framework that does not apply at your scale. When your exact situation is in doubt, the directive text and its national transposition override any summary, including this one.
Where an audio version helps, and where it does not
Let us say it upfront to avoid overpromising: offering an audio version of your content does not, on its own, make a site compliant with the European Accessibility Act. Compliance turns on structure, keyboard navigation, contrast, labels, and how the page works with a screen reader. An audio track laid over a poorly structured page fixes none of that.
Where audio is genuinely useful is on the editorial and informational content around the service: traveller information pages, line updates, practical guides, conditions of carriage, an operator blog. These texts get read, are hard to follow while moving, and benefit from being listenable for a traveller whose hands are busy, whose eyes are tired, or who reads with difficulty. It is a usability complement, not a compliance checkbox, and it is better presented that way internally. For this content, what matters is reading quality: getting station, airport and line names right, a subject we cover on our French text to speech page, where targeted correction lets you fix the pronunciation of a recurring proper noun once and for all.
Proper nouns, the sensitive point in transport
Transport content is saturated with proper nouns: stations, airports, towns, lines, rolling stock. That is exactly where a text-to-speech engine can stumble, and where an operator should check before publishing. The rule is the same as for any proper-noun and place-name pronunciation in audio: you set the recurring names in advance, once, and the tool then respects them everywhere. On a network, that list is finite and known, so the work is done once and holds over time.
Where to start, concretely
The right sequence does not begin with audio. It begins by placing your service within the directive's scope (national or urban, company or microenterprise), then addressing the underlying digital accessibility of your booking and information interfaces. Audio for editorial content comes next, as a service to the traveller, measurable and honest. If you want to understand what this framework imposes on the rest of a public site, our article on the public sector web accessibility directive sheds light on the neighbouring rules that target public bodies. And to hear what well-tuned French reading does to your own text, the simplest thing is to try it on one page before equipping the whole site.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo