Before a blind traveler can compare a single flight, they have to fill out the search form, and that is exactly where many airline sites break down. Here are the input barriers to check on your own site. First in a five-part series on airline booking accessibility by Michael Taylor.
The summer travel season is here, and many people are booking flights, hotels, and event tickets now. From what I've run into, poor accessibility can derail any part of that. I'm starting a new miniseries where I go through each task on common travel sites one at a time, beginning with airline websites and the process of entering flight search details. As always, everything here is about screen reader accessibility, and this reflects what these sites are like for me in the middle of 2026.
Departure and Arrival Selection
The input screens on most airline sites follow the same pattern. To pick departure and arrival airports, I type into a text field, and the site shows suggestions below it that I can select to lock in a choice. My screen reader usually tells me I can move through those suggestions with the arrow keys. In practice, that works maybe half the time.
Often, the moment I try to arrow into the list, the suggestions vanish, and focus jumps back to an empty field. When I do manage to make a selection, the airport name sometimes appears as plain static text rather than an editable field. At that point, I can't change the airport without starting the whole entry over.
Most of these designs put a small icon button between the two fields that swaps departure and arrival when activated. On the sites I've used, that button is often unlabeled in the code, so my screen reader skips it. On my phone, it's worse because reaching the suggestions list is hard, and any focus I put on it makes the options disappear.
Date Selection
Date entry is another rough spot. Most airlines use a calendar grid, a visual month-by-month layout you're meant to click through. Moving through that grid with a screen reader is slow and clunky. Each date is often read as just a number, with no sense of which weekday or month I'm on.
Once I pick my dates, coming back to the calendar usually gives me no readout of what I actually selected. The little arrow buttons that flip between months are sometimes mislabeled, so my screen reader doesn't handle them right.
The fields that open the calendar are often announced as editable text, which suggests I can just type a date and skip the grid. Almost every time, typing does nothing. Either the text isn't accepted or there's no way to lock in the date after I enter it. If I can't actually type a date, announcing the field as editable only misleads me.
Item Pickers
Several steps ask me to choose between options, such as one-way versus round-trip, the number of travelers, or the cabin class. Most sites handle this with selectable buttons in a horizontally scrolling row. Sometimes those buttons aren't labeled at all, so my screen reader misses them or reads them wrong.
Other times, there's no spoken cue for which option is currently selected, so I can't tell what I've picked or change it on the fly. With some expandable menus, the choice snaps back to the default once I make a selection and close the menu. If I don't catch that before I run the search, I get results for the wrong trip.
Here's the bottom line for me. If I can't get the search details in, I can't move forward at all. On every airline site I've tried, at least one of these steps has stopped me cold before I've even seen a flight.
Airline Flight Search Accessibility: FAQ
Why can't screen reader users enter flight search details on some airline websites? Flight search forms fail screen reader users when core controls aren't built for assistive technology. In Michael's experience, airport suggestion lists collapse when he arrows into them, selected airports read back as uneditable text, and swap buttons go unlabeled. Each of those is a discrete bug you can look for in your own search form, and catching them early is part of building an accessibility mindset into design and QA.
What makes a calendar date picker inaccessible to a screen reader? A date picker becomes inaccessible when its grid can't be navigated or announced meaningfully. Michael describes dates read as bare numbers with no weekday or month, no confirmation of what he selected, and manual date fields that claim to be editable but reject typed input. For a structured way to test this yourself, see UsableNet's step-by-step guide to running a web accessibility audit.
How are flight search fields tested for accessibility? Testing starts with completing the entire search using only a screen reader and keyboard, no mouse. The signals to watch for are unlabeled buttons, options with no selected-state announcement, and fields that misreport whether they're editable. An automated accessibility testing tool catches a share of these before manual testing begins.
Barriers like these are also what draw ADA web accessibility claims, since screen reader users file most of them, and partial fixes don't remove the exposure.
UsableNet's Accessibility as a Service pairs an expert WCAG 2.2 AA audit with a prioritized remediation plan your team implements, backed by testing from people who use assistive technology and litigation support. If a screen reader can't complete your flight search, talk to a UsableNet accessibility expert.
