ADA Compliance for Hotels, Resorts, and Vacation Rentals

Hospitality is the only industry the Department of Justice has singled out with its own specific reservation-system rule. Under 28 CFR § 36.302(e), every place of lodging must make reservations for accessible rooms available in the same manner and during the same hours as reservations for non-accessible rooms, and must describe the accessible features of the property and rooms in enough detail to let a guest with a disability assess independently whether the room meets their needs. That disclosure obligation runs through your direct booking site, your mobile app, your phone reservations script, and crucially every third-party channel where your inventory appears — Booking.com, Expedia, Hotels.com, Airbnb, Vrbo, and the whole long tail of metasearch and channel managers. The combination of Title III web liability plus this distribution-channel disclosure rule makes hotel websites one of the most heavily-targeted categories in 2025-2026 ADA litigation.

What 28 CFR § 36.302(e) actually requires

The DOJ promulgated § 36.302(e) in the 2010 ADA Title III revisions and clarified its application to digital booking in successive guidance documents. The rule has four operative requirements that hotel operators frequently miss. First, you must modify your reservation policies and procedures to ensure that individuals with disabilities can make reservations for accessible guest rooms during the same hours and in the same manner as individuals who do not need accessible rooms. That includes 24/7 self-serve booking — telling a wheelchair-using guest to call between 9 and 5 to book an accessible room is itself a violation.

Second, you must identify and describe accessible features in the hotel and guest rooms offered through the reservation system in enough detail to permit individuals with disabilities to assess independently whether a given hotel or guest room meets their accessibility needs. "Accessible room available" is not enough; you have to specify which features (roll-in shower with bench, 32-inch door clearance, visual notification devices, lowered closet rods) are actually present. Third, you must reserve, upon request, accessible guest rooms or specific types of accessible guest rooms and ensure that the rooms are held back from the standard inventory until the request is cancelled or completed. Fourth, you must guarantee the specific accessible room reserved by the guest — the practice of reassigning at check-in based on availability is not allowed.

DOJ enforcement under this rule has produced settlement agreements with Marriott, Hilton, Best Western, and others that specifically prescribe what an accessible-features disclosure page must contain and how it must be linked from each room listing. Those settlements function as the practical compliance template for the rest of the industry.

OTA distribution: where your liability multiplies

Booking.com exposes hotel inventory through a unified room-detail UI. The accessibility-features section is populated from the property data feed you push through your channel manager (SiteMinder, Cloudbeds, RateGain, Sabre SynXis). If your channel-manager template does not include specific accessible features per room, the OTA listing inherits a generic "contact property" placeholder that fails § 36.302(e). The DOJ has made clear in commentary that the property is ultimately responsible for what appears in third-party listings.

Expedia and Hotels.com (same parent inventory) present similar issues plus their own widget-level WCAG failures. The accessibility filter on Expedia is a checkbox with a generic "Accessible" label that does not specify mobility versus hearing versus vision; properties that do not push detailed accessibility codes through GDS get mapped into the broadest bucket and then mis-matched to travelers with specific needs.

Airbnb introduced a granular accessibility- features taxonomy in 2018 (35+ specific features per listing) that hosts must self-attest to. The hosting platform itself has been the subject of lawsuits where blind users could not navigate the booking flow with a screen reader; for hosts who list multiple properties or operate as a hospitality business, the per-listing disclosure and the platform's own widget issues can compound.

Vrbo has a less developed accessibility taxonomy than Airbnb and historically pushes property managers toward free-text descriptions, which routinely under-disclose actual features. Vrbo property managers operating multiple units are increasingly named in ADA cases alongside Airbnb superhosts.

Reservation widget failures plaintiffs cite

Hotel booking widgets — whether built directly by the brand, licensed from Sabre, Amadeus iHotelier, Pegasus, or Windsurfer CRS, or embedded from an OTA — fail accessibility audits in recognizable ways. The list below covers what shows up in the majority of recent hospitality demand letters:

1. Date pickers built as visual calendar grids without keyboard navigation. The arrow-key paradigm for moving between days is missing in roughly 60 percent of custom hotel widgets we audit, violating WCAG 2.1.1.
2. Room comparison tables presented as divs-with-grid-CSS rather than semantic <table> markup. Screen readers cannot announce row/column relationships, so guests cannot compare accessible features across room types.
3. Accessibility filter that does nothing. Many widgets show a checkbox labeled "Accessible rooms only" that filters the visible list but does not update the result count announced to assistive tech and does not refocus the heading.
4. Booking calendar availability tiles with insufficient contrast. Disabled (sold-out) dates are typically shown in light gray on white, failing the 3:1 ratio for non-text contrast under WCAG 1.4.11.
5. Room photo galleries without alt text and lightbox modals that trap focus or fail to return focus to the trigger on close.
6. Virtual tour iframes from Matterport, Cloudpano, or proprietary 360 viewers that have no keyboard alternative and no descriptive transcript of the room layout.
7. Guest review widgets from TripAdvisor or Trustpilot embedded as third-party scripts that load custom shadow DOM components inaccessible to screen readers.
8. Loyalty program portals (Marriott Bonvoy, Hilton Honors, World of Hyatt, IHG One Rewards) where the points-balance dashboard, redemption flow, and member communication preferences each have their own WCAG violations.
9. Accessible-feature description page that is actually a PDF. Linking to a scanned PDF of the hotel's ADA features document defeats the entire point of § 36.302(e).
10. Mobile app parity gaps. Many chains pass their web audit but ship native iOS and Android apps with VoiceOver and TalkBack failures in the booking flow.

Vacation rentals and short-term rental operators

The vacation-rental category sits in a legal gray zone that is rapidly shrinking. Individual homeowners renting a single property occasionally are generally not considered places of public accommodation under Title III. But once you cross into commercial operation — multiple properties, a brand site, a booking engine, a property-management LLC — courts have increasingly treated the operation as covered. Property management companies that aggregate inventory across owners (Vacasa, Evolve, Awning, RedAwning) face direct exposure on their own platforms and on the OTAs they distribute to.

For STR operators, the practical compliance baseline is the same as a small hotel: an accessible direct-booking site if you have one, accurate and detailed accessibility disclosure on every channel where your inventory appears, an alternative contact path (phone or accessible form) for guests who cannot complete the standard booking flow, and a documented process for honoring accessible-room reservations. The Title III analysis is fact-intensive, and the safer assumption for any operator with three or more units is that you are covered.

Cost and timeline reality for hospitality

Hospitality remediation costs vary enormously based on whether the brand controls its own booking engine or relies on a CRS vendor. Independent properties on third-party CRS platforms have less direct code to fix but more channel- distribution work to do; brands with proprietary platforms have more code to remediate but more control over the result.

What to do today

Pull up your own property on Booking.com and Expedia. Look at the accessibility-features section of each room type. If it says "Contact property" or lists generic categories without specific feature detail (roll-in shower vs. accessible tub, visual smoke alarm, hearing-impaired kit availability), you have a § 36.302(e) gap that any tester can document in ten minutes. Update your channel-manager template to push specific accessibility codes per room type, and create a dedicated /accessibility page on your direct site that lists every accessible feature in detail and is linked from the room-detail pages.

Then keyboard-test your direct booking flow from search to confirmation. The date picker is usually where keyboard navigation fails first. If you cannot pick check-in and check-out using only Tab and arrow keys, no screen reader user can either, and that single failure has driven dozens of hotel settlements in the last 24 months.