The European Accessibility Act covers specific elements of passenger transportation services, focusing on the digital touchpoints riders use to plan, book, and complete trips. Websites, mobile apps, electronic ticketing systems, real-time travel information, and self-service terminals all fall within scope. Operators offering air, bus, rail, and waterborne passenger transport in the EU market are responsible for making these touchpoints meet the EAA’s accessibility requirements, which align technically with EN 301 549 and WCAG 2.1 AA. The EAA went into effect on June 28, 2025.
| Area | What Applies |
|---|---|
| Modes Covered | Air, bus, rail, and waterborne passenger transport |
| Digital Assets in Scope | Websites, mobile apps, e-ticketing, real-time travel info, self-service terminals |
| Technical Standard | EN 301 549, which maps to WCAG 2.1 AA for web and mobile content |
| Effective Date | June 28, 2025 |
| Urban and Suburban Transport | Partial scope, primarily self-service terminals and ticketing |
| Documentation Required | Accessibility statement and supporting conformance records |
Which Transportation Services Fall Under the EAA?
The EAA applies to passenger transport services across air, bus, rail, and waterborne modes operating in the EU market. The obligations focus on the service elements riders interact with directly, not the vehicles themselves.
Urban, suburban, and regional transport have a narrower scope. For these operators, the EAA primarily covers self-service terminals, ticketing machines, and check-in technology rather than the full set of digital touchpoints.
Long-distance and cross-border operators carry the full set of requirements. That includes the public-facing website, the mobile app, the booking flow, account management, and any post-purchase service interactions.
What Digital Assets Are Covered?
The EAA specifies the categories of transport-related digital content that must be accessible. Operators should map each one to their actual product surface.
Websites: Marketing pages, booking flows, account areas, and customer support content.
Mobile apps: Native iOS and Android apps used for booking, boarding passes, and trip management.
Electronic ticketing: Purchase flows, ticket delivery, and digital ticket display.
Real-time travel information: Departure boards, service alerts, delay notifications, and route updates.
Self-service terminals: Ticket vending machines, check-in kiosks, and information terminals in stations and airports.
Each asset has its own technical considerations. A mobile app is evaluated against the mobile portions of EN 301 549. A self-service terminal carries hardware criteria in addition to the software interface.
What Standard Do Transport Operators Need to Meet?
EN 301 549 is the harmonized European standard referenced by the EAA. For websites and mobile apps, EN 301 549 incorporates WCAG 2.1 Level AA as the core technical baseline.
For self-service terminals, EN 301 549 adds hardware-specific criteria covering reach, controls, audio output, and assistive technology compatibility. Operators with kiosks and ticket machines need to evaluate both the software interface and the physical product.
Conformance is determined through an accessibility audit conducted by qualified auditors, not through automated scans. Scans only flag approximately 25% of issues and cannot verify conformance with EN 301 549 or WCAG 2.1 AA.
What Does Conformance Require in Practice?
The path for a transport operator typically follows a clear sequence. Each step builds on the prior one.
- Take inventory of every digital asset in scope, including third-party booking engines and white-labeled apps
- Conduct a manual accessibility audit against EN 301 549 / WCAG 2.1 AA for each asset
- Prioritize the identified issues using Risk Factor or User Impact prioritization formulas
- Remediate the issues, working through the audit report
- Validate the fixes through follow-up evaluation
- Publish an accessibility statement and maintain supporting documentation
Third-party components deserve attention. Many transport operators rely on booking platforms, payment processors, and CRM tools they did not build. Each vendor relationship needs an accessibility review, and operators should request an ACR from vendors providing in-scope technology.
What Happens With Existing Self-Service Terminals?
The EAA includes a transitional provision for self-service terminals already in lawful use before June 28, 2025. These can continue to be operated until the end of their economically useful life, up to a maximum of 20 years after the EAA’s effective date.
New terminals deployed after the effective date must meet the EAA requirements from day one. Operators planning fleet refreshes should treat accessibility as a procurement requirement, not a post-purchase remediation project.
How Does the EAA Connect to National Enforcement?
The EAA is an EU directive, which means each member state transposes it into national law and designates enforcement authorities. Penalties, reporting requirements, and complaint mechanisms vary by country.
Operators serving multiple member states need to track the national rules in each jurisdiction where they sell tickets or operate routes. The underlying technical standard is consistent across the EU, but the enforcement posture is not.
Accessible.org tracks EAA developments as member states finalize their national approaches. The technical work, audits, remediation, documentation, applies regardless of which country’s authority is reviewing the service.
Frequently Asked Questions
Does the EAA apply to transport operators based outside the EU?
Yes, when those operators offer passenger transportation services in the EU market. A non-EU airline selling tickets to passengers departing from EU airports is providing a service covered by the EAA, and its booking website and mobile app fall within scope.
Are public transport authorities covered the same way as private operators?
The EAA applies based on the service category, not ownership structure. Both public and private operators of in-scope transportation services carry the same accessibility obligations for their digital assets.
Do operators need a separate accessibility statement for each digital asset?
The accessibility statement should cover each in-scope asset clearly. Some operators publish a single statement that addresses the website, app, and ticketing flow together, while others use separate statements per product. Either approach works as long as the documentation is specific and findable.
What about onboard Wi-Fi portals and in-vehicle information displays?
Digital content delivered through these channels can fall within scope when it forms part of the transportation service, particularly travel information and ticketing functions. Operators should evaluate each surface against EN 301 549 rather than assuming it sits outside the EAA.
Transport operators preparing for EAA conformance benefit from starting with a clear inventory and a qualified audit of each digital asset in scope.
Contact Accessible.org to discuss an EAA audit for your transportation service: Contact Accessible.org.
