ADA Compliance for Airline and Travel Booking Websites

Airline websites are not regulated under Title III of the ADA. They sit under the Air Carrier Access Act (49 U.S.C. § 41705) and the DOT's implementing rules at 14 CFR Part 382, which since the November 12, 2013 final rule have required US and foreign carriers operating to or from the United States to make their public-facing websites conform to WCAG 2.0 Level AA. The DOT — not the Department of Justice — is the enforcement authority.

That single jurisdictional difference reshapes everything about how an airline manages accessibility risk. There is no private right of action under the ACAA — the Supreme Court closed that door in Love v. Delta Air Lines, 310 F.3d 1347 (11th Cir. 2002) — so the demand-letter shakedown industry that defines ecommerce ADA litigation does not target carriers directly. Instead, complaints funnel through the DOT Office of Aviation Consumer Protection, which investigates patterns and issues consent orders that can assess civil penalties up to $34,936 per violation per passenger, as adjusted for inflation under 49 U.S.C. § 46301. Online travel agencies live in a different world: Expedia, Kayak, Priceline, Hotwire, Booking Holdings properties, and metasearch sites such as Skyscanner are not air carriers, so they remain in the same Title III crosshairs as ecommerce. This guide walks through both regimes, the booking-flow elements DOT actually cites, the airport-kiosk obligation almost nobody outside aviation knows about, and what real remediation costs across the carrier and OTA stack.

This page is informational and is not legal advice. ACAA, ADA, Section 504, and state-law obligations vary by carrier type, jurisdiction, and business model — consult qualified counsel for case-specific guidance.

How DOT enforcement differs from a typical Title III lawsuit

A Title III plaintiff in federal court typically wants injunctive relief and attorney's fees. The mechanics — demand letter, quick settlement, code remediation promise — encourage volume and small per-case payouts. DOT enforcement is structurally different. The Office of Aviation Consumer Protection investigates patterns across many flights and many passengers, builds a consent-order record that often spans thirty or more cited violations, and negotiates a single civil penalty that captures the entire pattern. The consent orders are public and read like a compliance audit transcript.

Recent enforcement orders illustrate the pattern. In April 2023, the DOT issued Order 2023-4-3 against Lufthansa for $1.1 million in civil penalties relating to wheelchair-handling and seating- accommodation failures, building on the carrier's 2016 record. In January 2024 the DOT levied a $50 million order against American Airlines covering wheelchair damage and disability assistance, including digital-channel disclosure failures that touched the mobility-aid declaration form on aa.com. Hawaiian Airlines settled a 2017 enforcement order for $300,000 covering accessibility of its booking functions. JetBlue entered into Order 2017-2-9 with a $200,000 civil penalty for a related set of violations involving disability-assistance request handling. Each of these touched website or app surfaces in some way — typically the special- assistance request form, the mobility-aid declaration, or the wheelchair-dimension input field.

Because the ACAA preempts state-law direct claims against carriers on accessibility-of-air-travel issues, plaintiffs who would otherwise sue a hotel under California's Unruh Act for $4,000 per visit cannot do the same to an airline. They can, however, file a DOT complaint that goes into the carrier's record and contributes to the next consent-order settlement. The DOT publishes its monthly Air Travel Consumer Report which itemizes disability complaints by carrier, which itself functions as a reputational enforcement tool.

What does the 14 CFR Part 382 website rule actually require?

The 2013 final rule (78 FR 67882) added § 382.43 requiring covered US and foreign carriers to ensure their public-facing websites marketing passenger air transportation conform to WCAG 2.0 Level AA for the following functions: booking, checking flight status, checking in, accessing flight schedules and fares, accessing the carrier's contract of carriage and customer service plan, requesting refunds and managing reservations, frequent-flyer account access, retrieval of receipts, and obtaining information about services for passengers with disabilities. The rule applies to carriers that sell air transportation in the US and operate at least one aircraft with 60 or more seats — a threshold that pulls in essentially every scheduled passenger carrier.

Under 14 CFR § 382.43(c), the rule extended to mobile apps in 2017 for new app development and December 2021 for legacy apps. Carriers must designate at least one accessibility coordinator (§ 382.43(c)(4)) and provide an alternative accessible communication method — typically a phone line — that does not charge any premium and offers equivalent service. Notice that this phone-alternative obligation is not an excuse to ignore the website; the carrier must do both, and the website must work.

The technical standard is WCAG 2.0 Level AA, which is older than the 2.1 AA standard that DOJ now references in Title III settlements and that ADA Title II adopted in the 2024 final rule for state and local governments. Several DOT enforcement orders have nonetheless cited 2.1-era criteria where the failure also implicates a 2.0 criterion, particularly 1.4.3 (contrast minimum), 2.4.3 (focus order), and 4.1.2 (name, role, value). Treating WCAG 2.1 AA as the functional baseline closes the gap and is what most carriers' outside accessibility consultants now recommend.

What WCAG violations do airline booking flows have most often?

Carrier booking flows are uniquely complex. A single passenger search produces fare-class chips, brand-fare cards, ancillary upsells (bag fees, seat upgrades, lounge passes, carbon offsets), origin-destination pairings, multi-leg itineraries, codeshare disclosures, and a stack of regulatory disclosures (DOT 24-hour refund rule, baggage fee transparency, full-fare advertising). Each of these surfaces is a place where accessibility fails. The patterns repeat across Sabre-powered carriers (American, Air Canada, JetBlue, Alaska), Amadeus-powered carriers (United, Lufthansa Group, Qantas, Singapore Airlines), and Travelport carriers (Delta, Hawaiian, the legacy Worldspan and Apollo footprint).

• Seat selection maps rendered as SVG with no alternative text or accessible name, no programmatic indication of which seats are exit rows, bulkhead, premium economy, or already taken. Screen-reader users cannot independently choose a seat. WCAG 1.1.1 and 4.1.2 fail simultaneously.
• Calendar and date pickers with custom div-based widgets that intercept Tab and arrow keys. WCAG 2.1.1 (Keyboard) fails. The fix is the native HTML5 date input or a properly- authored ARIA grid pattern with role="grid", role="row", and role="gridcell".
• Fare-class comparison cards where Basic Economy vs Main Cabin vs Premium are colored chips with text contrast ratios as low as 2.4:1. WCAG 1.4.3 (Contrast Minimum, 4.5:1 for normal text). Carriers regularly use brand colors that do not meet AA at small sizes.
• Special-needs request forms — the screens where a passenger declares a wheelchair, oxygen, service-animal, or cognitive-disability accommodation. These are precisely the forms most likely to be used by disabled passengers, and they regularly fail label association under WCAG 1.3.1 and 4.1.2. Several DOT orders have cited this surface specifically.
• Mobility-aid declaration inputs for wheelchair dimensions and battery type. Custom dropdowns without proper ARIA, weight-input sliders without keyboard support, and auto-advancing focus that strands screen-reader users mid-form.
• Refund and change flows behind a captcha that has no audio alternative, in violation of WCAG 1.1.1 and the 1.4 Distinguishable family. The DOT 24-hour-refund rule does not relax for inaccessible captchas.
• Codeshare and operating-carrier disclosureshidden behind a tooltip or info icon with no programmatic relationship to the flight segment. Required disclosures must be perceivable, which closes off the icon-only pattern under WCAG 1.3.1.
• Baggage fee tables rendered as a graphic image with no text equivalent — a direct WCAG 1.1.1 failure that also implicates DOT's baggage transparency rule under 14 CFR Part 399.
• Multi-passenger itinerary lists built with non- semantic divs instead of an ordered list or table. Screen-reader users cannot tell which passenger is associated with which itinerary segment. WCAG 1.3.1.

OTA exposure: where Title III still bites

Online travel agencies, metasearch engines, and tour operators are not air carriers, which is the analytical fact that carries most of the accessibility weight in this segment. Expedia Group (Expedia, Hotels.com, Vrbo, Travelocity, Orbitz, Hotwire), Booking Holdings (Booking.com, Priceline, Kayak, Agoda), Trip.com Group, and metasearch players like Skyscanner, Momondo, and Google Flights sell air transportation as a third party. They are subject to the same Title III analysis as any other consumer ecommerce site, and in California the same Unruh Civil Rights Act $4,000-per-visit statutory damage exposure that drives volume hotel and ecommerce litigation.

Several of the major OTAs have entered into structured-negotiation agreements with the National Federation of the Blind committing to WCAG 2.1 AA conformance and ongoing third-party audits. Priceline settled in 2017 with the NFB after litigation over screen-reader access to its travel-booking flows. Hotwire reached a similar agreement. Where the OTA hosts third-party hotel content, the OTA inherits the accessible-feature description obligation under 28 CFR § 36.302(e) for the hotel side of its inventory — even though that DOJ rule does not reach the airline side of its inventory. That bifurcation is one of the more confusing aspects of mixed travel-marketplace compliance.

For tour operators, cruise-line sites, rail carriers (Amtrak under Section 504), and rental-car booking surfaces (Enterprise, Hertz, Avis, Sixt, Turo), the analysis tracks ordinary Title III. Cruise lines have additional ADA exposure under Spector v. Norwegian Cruise Line Ltd., 545 U.S. 119 (2005), which extended Title III to foreign-flagged cruise vessels in US waters and creates parallel exposure for the cruise line's booking website.

Airport kiosks: the obligation almost nobody outside aviation knows about

14 CFR § 382.57 requires that automated airport kiosks installed at US airports on or after December 12, 2016 conform to a published technical standard, and that until full fleet replacement at least 25 percent of self-service kiosks at each location be accessible. The standard incorporates the Section 508 Information and Communication Technology criteria. The kiosk obligation runs jointly between the carrier (which owns the software stack and the user interface) and the airport operator (which controls placement and physical reachability). This dual-responsibility model is unusual in accessibility law.

Practical kiosk failures DOT has cited: missing audio output for blind users (a basic § 382.57(c)(2) failure), tactilely discernible controls absent or non-conforming, headphone jack placement that is unreachable from a wheelchair, screen contrast that fails at outdoor terminal lighting conditions, and kiosk software that rebrands frequently and breaks accessibility regression tests between releases. Carriers that operate at hundreds of airports must coordinate accessibility testing across kiosk vendors (NCR Aviation, Embross, Materna IPS, SITA, Elenium, Amadeus ACUS) and across airport-operator deployment cycles. The kiosk stack often shares a code base with the carrier's mobile check-in flow, so a kiosk fix usually has app-side spillover.

What does airline accessibility remediation cost?

Airline-side remediation is expensive because the booking surface is unusually complex, the GDS layer (Sabre, Amadeus, Travelport) sits in between the airline's code and the customer screen, and every fix has to flow through change management for an FAA- regulated entity. OTAs are closer to ordinary ecommerce remediation cost.

Cost ranges assume real code remediation plus a documented accessibility-conformance program (designated coordinator, annual third-party audit, accessible-procurement language for new vendors). Carriers that try to bolt on a JavaScript overlay widget instead of fixing the underlying code see those overlays explicitly rejected in DOT consent-order remediation requirements; the overlay-as-compliance model has never satisfied DOT. For a deeper look at why, see our analysis of why overlay widgets fail under DOT and DOJ scrutiny.

Frequently asked questions

What to do today

If you are a US carrier, pull your most recent third-party WCAG 2.0 AA conformance report for the booking, check-in, status, and special-services surfaces — the four areas DOT cares most about. If the report is older than twelve months, schedule the next one now. The DOT does not announce investigations until they are already in flight, and the inflation-adjusted civil-penalty schedule published annually in 14 CFR Part 383 makes a single bad cycle expensive at scale. Confirm your designated accessibility coordinator under § 382.43(c)(4) is current and reachable.

If you are an OTA, your exposure is Title III private litigation and California Unruh Act state suits. The fastest risk-reduction move is to scan your booking flow for the standard ten plaintiff- attorney findings, fix the cart-equivalent (passenger-information page) first, and document a real WCAG 2.1 AA conformance program. See our state guide for California-specific Unruh Act exposure and our broader breakdown of what to do when you receive an ADA demand letter.