EAA 2026 for Transport Operators: Passenger Document Accessibility Requirements
The European Accessibility Act has entered its enforcement phase. For compliance and accessibility teams at rail operators, airlines, ferry companies, and bus carriers, the deadline has arrived. As of June 28, 2026, the EAA is enforceable across EU member states — and transport is one of the sectors named directly in the legislation.
Transport Is Explicitly in Scope Under EAA Article 2
Unlike many accessibility frameworks that apply broadly and leave sector interpretation to regulators, the EAA is unusually precise. Article 2 names transport directly: rail services, air transport, water-borne passenger transport, and bus services operating within the EU are directly within scope. The legislation covers both the services themselves and the documents that support those services.
The standard that applies is WCAG 2.2 Level AA. Any document a passenger might reasonably need to access, understand, or act upon is subject to this requirement.
Which Passenger Documents Are Affected
Ticket terms and conditions. These govern the contractual relationship between the operator and the passenger. Routinely distributed as PDFs at the point of purchase or via confirmation emails.
Timetables. Whether provided in print-ready PDF format on a website or attached to a booking confirmation, timetables are functional documents that passengers depend on to plan and complete journeys.
Booking confirmations. Automated PDF confirmations sent to passengers after purchase. These often contain critical information about departure times, seat allocations, and special service arrangements.
Accessibility service guides. Documents describing assistance services for passengers with disabilities — wheelchair boarding procedures, assistance request processes, contact information for accessibility services.
Delay and disruption communications. PDFs distributed during service disruptions, explaining passenger rights, compensation procedures, and alternative travel arrangements.
Safety information. Safety briefing cards, emergency procedure documents, and hazardous materials notices distributed digitally or provided via QR code during travel.
Why PDF Cannot Satisfy EAA Requirements
The EAA references WCAG 2.2 AA, which includes WCAG 1.4.10 Reflow. This criterion requires that content can be presented in a single column at 320px equivalent width without horizontal scrolling — the requirement that makes documents usable for people with low vision who zoom heavily.
Transport PDFs typically use multi-column timetable layouts, compact typography, and table-heavy structures. These cannot reflow at 320px. This is not a tagging problem — it is a format problem. PDF is fixed-layout by design. No accessibility remediation workflow produces a PDF that satisfies WCAG 1.4.10 for a complex transport document.
EPUB3 is reflowable by design. A timetable converted to EPUB3 renders in a single column at any viewport width. Tables are marked up semantically. Screen readers can navigate by heading. This is the accessible format transport operators need.
Practical Compliance Steps
Step 1: Audit your document portfolio. Identify every passenger-facing document currently distributed as PDF. Timetables and booking confirmations typically have the highest volume and most complex layouts — prioritise these.
Step 2: Assess current accessibility status. Run existing PDFs through PAC (PDF Accessibility Checker) or Adobe Acrobat’s accessibility tool. This surfaces WCAG 1.4.10, 1.3.2, and 1.4.3 failures quickly. Screen reader testing will be necessary for reading order and table markup issues.
Step 3: Convert high-risk documents to EPUB3. For documents that fail Reflow — which will be the majority of complex transport PDFs — conversion to EPUB3 is the most efficient path. toolkit.bot/pdf2epub converts PDFs to EPUB3 free, with no account required.
Step 4: Build EPUB3 into document production. For documents updated regularly (seasonal timetables, policy documents), build EPUB3 conversion into the production process rather than treating it as a one-time remediation task.
Step 5: Test with assistive technology. Test EPUB3 files with NVDA on Windows, VoiceOver on iOS, and TalkBack on Android before distributing. Verify reading order, table navigation, and heading structure.
Step 6: Document your compliance posture. Maintain records of accessibility assessments, conversion logs, and testing results. Regulators expect evidence of systematic compliance activity, not just assertions of conformance.
Convert passenger-facing transport PDFs to accessible EPUB3. Free tier: 5 conversions/month, no account required.
Try free → API: EUR 29/month