Blank checklist, printable form
Transport & Booking Accessibility Checklist
EAA Annex I Sections II\u2013III Compliance Checklist
Blank checklist for offline completion.
Tick one box per row. Add comments and evidence references in the Notes column as needed.
Journey Search & Planning
EAA Annex I §II–III, Journey planners and timetable information must be accessible.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| WCAG 2.1.1 | Critical | Journey planner / route search is fully keyboard-operable.Origin/destination fields, date pickers, time selectors, and search buttons must all work with keyboard alone. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.1 | Critical | Timetable data is available in text, not image-only.Schedule tables must use proper HTML tables with headers. PDF timetables must be tagged. No image-based schedules. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 4.1.3 | Critical | Real-time departure/arrival updates use aria-live regions.Live departure boards that auto-update must announce changes to screen readers, 'Flight BA123 now delayed to 14:30'. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.1 | Major | Multi-leg journey information has clear heading structure.Each leg of a journey (flight 1, connection, flight 2) must be clearly separated with headings and presented in sequential order. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.1 | Major | Price comparison is presented in accessible table format.Fare class comparisons with features (baggage, flexibility) must use properly structured tables, not image-based grids. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Booking & Seat Selection
The booking flow including seat maps and passenger details.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| WCAG 2.1.1 | Critical | Seat selection interface is keyboard-accessible.Interactive seat maps must support keyboard navigation, arrow keys to move, Enter to select. Provide a list-based alternative if the map is complex. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.1.1 | Critical | Seat map has text alternatives for seat status (available, occupied, premium).Each seat cell must have aria-label describing its status, 'Seat 12A, window, available, €45', not just colour coding. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 3.3.2 | Critical | Passenger detail forms have clear labels for all fields.Title, name, date of birth, passport number, all must have <label> elements. Group related fields with fieldset/legend. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 3.3.4 | Critical | Booking summary with review step before payment.Show all journey details, passenger info, and total cost for review before processing payment. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Accessibility Assistance
EAA requires transport operators to provide accessible assistance booking.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| EAA Annex I §III | Critical | Accessibility assistance booking is available online, not phone-only.Wheelchair assistance, meet-and-greet, and special needs requests must be bookable through the website, not just a phone number. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EAA Annex I §III | Major | Station/stop accessibility information is published online.Which stations have step-free access, lifts, accessible toilets, and assistance points must be published and searchable. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EAA Annex I §III | Major | Vehicle accessibility information is available (wheelchair spaces, audio announcements).Users should know before booking whether the vehicle has wheelchair spaces, hearing loops, and audio/visual announcements. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |
Post-Booking & Travel
Confirmations, boarding documents, and disruption information.
| Ref | Severity | Requirement | Status | Notes / Evidence |
|---|---|---|---|---|
| EAA Annex I §III | Critical | Booking confirmation is in accessible format (HTML email, not image receipt).Confirmation emails must be HTML with proper structure. Attached PDFs must be tagged. No image-only receipts. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 1.3.1 | Critical | Mobile boarding pass / e-ticket is screen-reader compatible.QR codes need text alternatives. Boarding details (gate, time, seat) must be available as real text, not embedded in an image. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| WCAG 4.1.3 | Critical | Disruption alerts (delays, cancellations, gate changes) are available in text.Push notifications and in-app alerts must include full text, not just 'Alert' with details in an inaccessible overlay. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EAA Annex I §III | Major | Rebooking and cancellation processes are accessible.If a journey is disrupted, the rebooking flow must be as accessible as the original booking, not a degraded experience. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EAA Annex I §III | Critical | Real-time travel information displays provide both visual and audio output.Departure boards, platform indicators, and gate displays must provide information visually on screen and via audio announcements. Information must not be conveyed through a single sensory channel. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EAA Annex I §III | Critical | Audio announcements include destination, stops, delays, and safety information.On-board and at-station audio must announce upcoming stops, final destination, delays, and safety instructions. This serves blind passengers and those who cannot read displays. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A | |
| EAA Annex I §III | Major | Disruption notifications are available in multiple formats (app, SMS, email, display).When services are disrupted, notify passengers through multiple channels, not just a screen at the station. Mobile push notifications, SMS, and email ensure users receive the information regardless of their location or abilities. | ☐ Pass ☐ Partial ☐ FAIL ☐ N/A |