Accessibility for hotels, restaurants and travel booking — built for the most-litigated digital sector.

In the United States, hotels are the dominant ADA Title III defendant industry alongside ecommerce and restaurants. Serial-plaintiff filings specifically target the reservation flow and the room-description page — that is where the duty defined by ADA Title III most visibly attaches to web content, and where a single inaccessible widget can support dozens of near-identical complaints. The Acheson Hotels v Laufer case briefly looked like it would narrow tester-plaintiff standing; in October 2023 the Supreme Court dismissed it as moot, leaving the underlying access duty intact.

The DOJ's reservation-system rule at 28 CFR 36.302(e) already imposes a specific obligation: identify accessible rooms, describe their accessibility features in enough detail to permit informed booking, and make them reservable through the same channels as non-accessible rooms. That rule has been in force since 2010 and is enforceable against hotels regardless of their web-accessibility posture in general. Treat it as a separate compliance line item that runs parallel to WCAG.

Restaurant chains face the same shape of risk, with the menu as the recurring target. PDF-only menus — a habit inherited from print operations — are the single most-cited issue in restaurant-website complaints; QR-code menus that resolve to inaccessible PDFs are a near-second. Online ordering and reservation flows (OpenTable, Resy, Tock embeds) add their own audit surface on top of the chain's own marketing site.

In the European Union, the European Accessibility Act names "passenger transport services" in its scope list, and the broader tourism economy is covered through national implementing regulations. Airlines are covered separately under the ECAC framework and EU passenger-rights regulations, with their own technical conformance expectations on booking and check-in surfaces. The accessibility duty sits across the entire travel-purchase journey, not just the website that takes the credit card.

OTAs — Booking.com, Expedia, Agoda, Trip.com, Hotels.com, Vrbo, Airbnb — bear the duty for the surfaces they own. A hotel cannot offload its 28 CFR 36.302(e) obligation by feeding accurate accessibility data into an OTA that strips or hides it; the hotel remains the public accommodation. But the OTA, as a separate digital service provider, owes its own ADA Title III duty (in the US) and EAA duty (in the EU) on its own website and app. Both sides of the handoff have to be accessible.

The cost of getting this wrong is concrete. Hotel and restaurant ADA settlements typically land in the $20,000–$50,000 range for first-time defendants and materially higher for repeat targets. In the EU, enforcement moved from the warning-letter phase that dominated most of 2025 into the fine-issuing phase in 2026 across Germany, France, Italy, Spain, and the Netherlands. Hospitality is squarely in the crosshairs of both regimes.

Hospitality sites change constantly. Properties launch seasonal packages on Tuesday, the F&B team swaps the dinner menu on Thursday, marketing ships a holiday hero over the weekend. A one-time accessibility fix lasts about as long as your next room-type launch — which is why the model that actually holds is three layers, not one.

First, run a free WCAG 2.2 scanner against your live site today to establish a baseline across the booking engine, the room-description pages, and the menu surfaces. Second, plug in continuous automated monitoring against every preview build and every production deploy — this is the layer that catches regressions before the customer does, and the layer most teams skip until they receive their first demand letter. Third, commission a manual audit by testers with disabilities at least annually, and after any major redesign, OTA-integration rollout, or PMS replatform. Automated tooling will never catch screen-reader legibility on a wine-list page, focus-order intent on a multi-room booking flow, or whether the accessible-room request workflow is actually usable end-to-end.

For the monitoring + manual-audit handoff specifically, our monitoring buyer's guide covers the platforms that handle the scan-to-audit workflow end-to-end — Qualibooth, axe Monitor, Siteimprove, and Level Access. Pick on integration fit with your CI and on whether the platform's manual-audit network actually includes testers with the disabilities your guests have — not all of them do. For the PDF surface that hospitality teams cannot avoid (group-rate sheets, banquet menus, accessibility statements), pair the monitor with our accessible PDFs end-to-end playbook.