Travel Website ADA Compliance 2026

Airlines (U.S. Carriers & Foreign Carriers Operating to U.S.)

U.S. airlines and foreign carriers serving U.S. routes are subject to the Air Carrier Access Act (ACAA) and DOT regulations at 14 CFR Part 382, which require core website and app functions to conform to WCAG 2.0 Level AA. Required accessible functions include: booking flights, checking in, accessing flight status, and managing reservations. DOT has issued enforcement actions with civil penalties against multiple carriers. Airlines also face ADA Title III exposure for their websites as places of public accommodation.

Hotels, Motels & Lodging Properties

Hotels are subject to ADA Title III as places of public accommodation, which extends to their websites and online booking systems. WCAG 2.1 Level AA is the current compliance standard. Hotels must also ensure that accessible room features (roll-in showers, lowered beds, TTY, hearing loops) are accurately and accessibly represented on their websites. The DOJ has specifically noted that inaccessible hotel booking flows — including date pickers and room selection — are a frequent source of complaints.

Online Travel Agencies (OTAs)

OTAs (Expedia, Booking.com, Kayak, Priceline, Google Flights, Hotels.com) are primarily subject to ADA Title III as places of public accommodation. Because OTAs integrate airline seat selection, hotel booking, and car rental in a single flow, they aggregate the accessibility failure points of all sectors into one interface. OTAs have been named in ADA web accessibility lawsuits; their complexity makes thorough WCAG compliance both more critical and more difficult to achieve.

Cruise Lines

Cruise lines have a complex legal status: the ADA generally does not apply to foreign-flagged vessels on the high seas, but ADA Title III applies to cruise line websites and shoreside operations (including U.S.-based booking offices and terminals). Major cruise lines have been targets of ADA web accessibility lawsuits related to their booking websites, shore excursion tools, and deck plan interactive maps. WCAG 2.1 Level AA applies to cruise company websites and apps.

Vacation Rentals (Airbnb, Vrbo, Direct Booking Sites)

Vacation rental platforms and direct-booking property sites are subject to ADA Title III where they operate as commercial booking services for properties that are places of public accommodation. Property owners renting short-term accommodations have additional obligations to accurately represent accessibility features. The DOJ has investigated Airbnb regarding accessibility disclosures for properties with claimed accessibility features.

WCAG 2.0 Level AA Requirement

14 CFR 382.43 requires that U.S. carriers and foreign carriers operating flights to/from the U.S. ensure the core functions of their primary websites and kiosks conform to WCAG 2.0 Level AA. 'Core functions' specifically include booking, check-in, flight status, and seat selection. This is a federal regulatory requirement with civil penalty exposure — separate from private ADA lawsuits.

Enforcement Authority

DOT's Office of Aviation Consumer Protection (OACP) enforces Part 382 airline accessibility requirements. DOT has issued consent orders and civil penalties against carriers including American Airlines, United Airlines, and others for ACAA violations. Penalties can reach $75,000 per violation per passenger for willful noncompliance.

Scope: What Must Be Accessible

Required accessible functions under Part 382 include: booking flights (search, select, purchase), online check-in, accessing flight status information, managing reservations, and any functions equivalent to those available in person at a ticket counter. The rule applies to airline-operated booking engines; DOT has been expanding its interpretation to cover all digital booking touchpoints.

Mobile Apps

DOT's Part 382 requirements extend to airline mobile apps. Airlines must ensure their iOS and Android apps conform to WCAG 2.0 Level AA for core booking functions. Mobile app accessibility testing requires platform-specific methods (iOS VoiceOver, Android TalkBack) in addition to automated scanning.

EU European Accessibility Act (EAA)

The EU's European Accessibility Act (EAA) entered enforcement phase in June 2025. U.S. airlines and travel companies operating in the EU, serving EU customers, or with EU-facing booking interfaces face new obligations under the EAA, which requires WCAG 2.1 Level AA compliance for transport services booking systems.

Date picker failures drive high litigation volume

Interactive date pickers — used in virtually every travel booking flow — are chronically inaccessible. They often require mouse-based interaction, fail keyboard navigation, and don't announce selected dates to screen readers. A single inaccessible date picker on a booking flow is sufficient grounds for an ADA complaint.

Seat selection maps are near-universal failures

Airline seat selection interfaces using interactive SVG or canvas-based seat maps are among the most commonly failed interactive elements in travel website accessibility audits. Few seat map implementations have meaningful keyboard alternatives. This is a known, documented failure across the industry.

Price filter and search tools create compounding violations

OTA price filtering tools — with sliders for price range, star rating toggles, filter checkboxes, and sort options — frequently fail accessibility testing. Dynamic result updates that don't announce to screen readers compound the problem. Users depending on assistive technology often can't effectively search for or compare travel options.

Destination imagery without alt text

Travel websites are image-heavy by nature — destination photos, hotel property images, room photography, and activity shots. Missing or generic alt text ('image001.jpg') on these images is a pervasive violation that both fails WCAG 1.1.1 and prevents screen reader users from forming a meaningful picture of their destination options.

Accessible room filtering is frequently inaccessible

The deeply ironic situation: hotel websites that offer accessible room options (roll-in showers, lowered beds) frequently present those filters in inaccessible ways — keyboard users can't activate checkboxes, filter selections don't persist across searches, or accessible room type descriptions aren't read to screen reader users.

Search & Date Selection

• Date picker operable entirely by keyboard (no mouse required)
• Selected dates announced to screen reader users when changed
• Origin/destination search fields have accessible autocomplete (ARIA combobox pattern)
• Passenger count controls keyboard-accessible with proper ARIA labels
• Search submission accessible by keyboard (Enter key on form)

Search Results & Filtering

• All filter controls (price, star rating, amenities, stops) keyboard-operable
• Filter selections announced to screen readers when applied
• Price range sliders have accessible keyboard alternatives (number inputs)
• Sort options accessible by keyboard with clear selected-state announcement
• Result count updates announced to screen readers ('143 flights found')
• Results cards have sufficient structure for screen reader navigation

Selection & Configuration

• Seat selection has keyboard-accessible alternative (dropdown or text input)
• Seat availability status conveyed by more than color alone
• Add-on selection (baggage, meals, upgrades) keyboard-operable
• Room/cabin type selection keyboard-operable with accessible descriptions
• Accessible room/cabin option filtering works for keyboard users
• Price change notifications visible to keyboard and screen reader users

Booking & Checkout Forms

• All form fields have visible, programmatic labels
• Required fields indicated by text label (not only asterisk or color)
• Form error messages identify specific failed fields and remediation steps
• Session timeout warned in advance with accessible countdown or extension option
• Payment form fields properly labeled (card number, expiry, CVV)
• Multi-page checkout maintains logical focus order through steps

Multimedia & Visual Content

• All destination, property, and activity images have descriptive alt text
• Video tours and property walkarounds have accurate closed captions
• Auto-playing video/audio can be paused, stopped, or muted by user
• 360-degree room/cabin viewer has keyboard-accessible controls or text alternative
• Property maps have text-based alternative (address, directions, landmarks)

Global Site Requirements

• Skip navigation link at top of each page goes to main booking content
• Color contrast meets WCAG 2.1 AA (4.5:1 normal text, 3:1 large text)
• Keyboard focus visible on all interactive elements at all times
• Page titles are unique and descriptive for each step in booking flow
• Session state changes (cart update, price change) announced to screen readers

Continuous Monitoring Platforms

Travel sites update frequently (seasonal content, price tools, new landing pages). Continuous monitoring is essential:

• RatedWithAI Pro — scheduled monitoring with violation trend tracking and PDF compliance reports
• Silktide — site-wide accessibility monitoring with strong content team workflow features
• Siteimprove — comprehensive platform used by major travel brands for continuous WCAG monitoring
• Deque axe Monitor — enterprise automated WCAG scanning with CI/CD pipeline integration

Manual Testing Essentials

Travel booking flows require mandatory manual testing — automated tools cannot evaluate the complex interactions:

• Complete a full booking using only keyboard — Tab/Shift+Tab for navigation, Enter/Space for activation, Arrow keys for date pickers
• Test seat selection with VoiceOver (Mac/iOS) or NVDA (Windows) — confirm seat availability and selection are announced
• Verify session timeout behavior — is a 5-minute warning given? Can keyboard users easily extend the session?
• Test all filter controls with keyboard — especially price sliders and star rating toggles

Are airline websites required to be ADA compliant?

Yes, with specific regulatory requirements. U.S. airlines and foreign carriers operating to/from the U.S. must comply with 14 CFR Part 382, which requires WCAG 2.0 Level AA compliance for core website functions (booking, check-in, flight status, seat selection). Airlines also face ADA Title III exposure. DOT has issued civil penalties against carriers for Part 382 violations.

What WCAG standard applies to travel websites?

Airlines must meet WCAG 2.0 Level AA under DOT Part 382. All other travel businesses — hotels, OTAs, cruise lines, vacation rentals — should target WCAG 2.1 Level AA, which is the current ADA litigation and compliance standard and the level required by the EU European Accessibility Act. WCAG 2.1 AA adds mobile and cognitive accessibility requirements not in WCAG 2.0.

What's the most commonly sued accessibility failure on travel sites?

Inaccessible date pickers and seat selection maps are the most commonly cited violations in travel industry ADA web accessibility complaints. These interactive elements are essential to the booking flow and almost universally fail keyboard navigation testing. If you can only fix one thing on your travel site this quarter, make your date picker keyboard-accessible.

How do DOT rules interact with ADA Title III for airlines?

DOT Part 382 and ADA Title III create overlapping obligations for airlines. DOT Part 382 is enforced by the Department of Transportation with civil penalties; Title III is enforced through private lawsuits and DOJ actions. An airline can be simultaneously cited by DOT and sued under Title III for the same website accessibility failure. DOT enforcement is regulatory; ADA Title III litigation includes potential monetary damages and injunctive relief.

Do accessible room filters need to be accessible?

Yes — and this is a common irony. Hotel websites that offer accessible room options (roll-in showers, lowered fixtures, visual alerts) must present those options in an accessible way. Inaccessible filter interfaces that block screen reader users from finding accessible rooms represent both a WCAG violation (1.3.1, 2.1.1) and a potentially more serious ADA accommodation failure. Accessible room discovery must itself be accessible.