Keyboard accessibility allows people to operate website functions through a keyboard or an input that acts like one. W3C’s keyboard criterion covers functionality without requiring particular timings for individual keystrokes, with a limited exception for functions that depend on the path of movement. Source: W3C: understanding keyboard accessibility

Test a real enquiry journey

Try opening the menu, choosing dates, changing the passenger count and reaching the enquiry form without a mouse. Use the same journey a customer would need, because testing the homepage alone leaves the booking controls unexamined.

Note where focus is visible and whether you can move forwards and backwards through the controls. If a calendar opens, check that you can choose a date and leave it again. Record the exact point where you become stuck so the website team can reproduce it.

Know the limit of the check

This is an initial review, not proof of complete accessibility. W3C describes its easy checks as a way to identify some barriers and recommends a more thorough assessment for a full evaluation. Use specialist testing when you need a conformance assessment. Source: W3C WAI: preliminary accessibility checks

Written and updated by Travelgenix. Sources checked on 16 October 2026. Worked examples and checklists are editorial illustrations and recommendations, not customer results.