All industries » Hotel website accessibility

Hotel website accessibility: DOJ reservation rule, booking widgets, room-feature descriptions

Hotels are commercial public accommodations under ADA Title III, and the DOJ has issued a specific hotel reservation rule (28 CFR 36.302(e)) that requires reservation systems to identify and describe accessible features of accessible guest rooms in enough detail to allow a person with a disability to assess whether the room meets their needs. The reservation rule has been the basis for a sustained line of plaintiff-side cases against independent hotels and small chains since 2018, when a wave of Title III cases against hotel websites cited the rule directly. The website must work for the reservation rule to work. Site Brace audits any hotel for $149 flat.

The rules that apply to hotels

1. ADA Title III

Hotels are explicitly named in the Title III definition of public accommodation at 42 U.S.C. 12181(7)(A). The 9th Circuit's Robles v. Domino's precedent is the canonical authority that a customer-facing website is part of the public accommodation, and it has been applied in hotel cases across multiple circuits. Plaintiff-side firms file steady volume against independent hotels and small chains; large chains tend to settle quickly with confidential terms.

2. The DOJ hotel reservation rule (28 CFR 36.302(e))

The DOJ regulation requires reservation systems (the website, the call center, and third-party platforms the hotel works with) to:

• Identify which guest rooms are accessible.
• Describe accessible features in enough detail to allow a guest with a disability to determine whether the room meets their needs. "ADA accessible" alone is not enough; specifics like roll-in shower vs. tub with grab bars, door-width clearance, visual-alarm presence, and bed transfer height are the kind of detail the rule contemplates.
• Hold accessible rooms back from general inventory until all non-accessible rooms of that type are booked.
• Reserve accessible rooms in the same manner as non-accessible rooms (same booking flow, same confirmation, same payment terms).

The rule applies to every reservation channel the hotel uses, including third-party booking platforms (Expedia, Booking.com, Hotels.com). The hotel cannot delegate the substantive accessible-room-description responsibility to those platforms; the hotel is the source of the room-feature data the platforms display.

3. State human-rights laws

State equivalents of Title III apply. California's Unruh Civil Rights Act provides statutory damages of $4,000 per violation, and California has been a high-volume jurisdiction for hotel-reservation Title III cases. New York and Illinois also have meaningful state-law layers. See the relevant state Title II guide for the public-entity dynamics; hotels fall under the state-law equivalents of Title III, not Title II.

The high-risk surfaces specific to hotel sites

The booking widget iframe

Most independent hotels and small chains use a third-party booking engine embedded as an iframe (Synxis, SiteMinder, Mews, RoomKey, Cendyn, or a chain-specific engine). The booking widget is the highest-interaction element on the site and the most-frequent place keyboard navigation fails. Common failures: the iframe has no title attribute (axe-core frame-title), date pickers inside the widget have no keyboard support, the rate-comparison table headers are not associated with the data cells, and the accessible-room filter (if it exists) is poorly labeled. The hotel is the responsible party even when the underlying widget is third-party.

Accessible-room-feature descriptions

This is the DOJ reservation-rule surface specifically. Most hotel websites have a "Rooms" or "Accommodations" page with a card per room type. The accessible-room card frequently reads only "ADA accessible" or "wheelchair accessible" without the substantive detail the rule requires. The fix is to include, on each accessible-room page: shower configuration (roll-in vs. tub with grab bars), door width, visual-alarm presence, bed transfer height, and any other distinguishing accessible feature. Automated scanners cannot evaluate this content; a human review is required.

Photo galleries

Hotel sites are photo-heavy. The gallery widget is typically a Lightbox or carousel; the same patterns that fail on dental and real estate sites fail here. Photos of amenities (pool, restaurant, fitness center, conference rooms) often have filename-style or generic alt text rather than descriptive content.

Downloadable PDFs (restaurant menus, event-space brochures, spa menus)

Restaurant menus, event-space and meetings brochures, and spa menus are commonly distributed as PDF files. Hotels are responsible for those PDFs as part of the website experience. PDFs exported from Word or InDesign without accessibility tagging are unreadable to screen readers and fail Title III for the same reason a missing alt text fails.

Event and meeting-room request forms

"Request a proposal" and "Plan an event" forms collect contact information, event date, guest count, and meeting-room preferences. They are usually built in the CMS's form builder with the placeholder-as-label pattern that breaks screen-reader use.

What we typically find on a hotel website

A note on the reservation-rule paragraph

Of every Title III line item, the reservation-rule paragraph is the one most often missing entirely. A hotel can pass automated WCAG scanning end-to-end and still fall short of 28 CFR 36.302(e) because no scanner reads the room-description content. A Site Brace audit flags missing or thin reservation-rule descriptions as a manual finding on each accessible-room page, with suggested copy patterns drawn from the rule's preamble and the DOJ technical assistance materials.

Notes on hotel-website platforms

Chain-affiliated property sites (Marriott, Hilton, IHG, Hyatt, Wyndham, Choice, Best Western) run shared platforms whose accessibility is iterated by the chain's web team; individual property pages have limited customization, but the accessible-room description on each property page is still the property's responsibility. Independent hotels typically run custom WordPress or a small-CMS platform (Squarespace, HubSpot CMS, Webflow) with a third-party booking widget embedded; WordPress accessibility plugins often add aria-label on generic elements (the aria-prohibited-attr failure). Boutique and lifestyle hotels typically run design-heavy custom sites with full-bleed photography and bespoke booking flows; these surface more color-contrast and reduced-motion findings than the chain platforms.

Why overlays are a poor fit for hotels

Accessibility overlays are heavily marketed to hotels. We have written about why accessibility overlays do not actually make sites WCAG-compliant in detail. For hotels specifically:

• Overlays cannot reach inside the booking-widget iframe. The reservation surface is untouched.
• Overlays do not write substantive accessible-room-feature descriptions; the reservation-rule content is human-authored or it is missing.
• Overlays do not tag downloadable PDFs (restaurant menus, event brochures) for screen readers.
• The FTC's April 2025 settlement with accessiBe ($1 million) makes overlay compliance claims a documented liability the hotel cannot delegate to the vendor.

How Site Brace audits a hotel website

The standard page mix for a hotel audit:

• Homepage
• Rooms or Accommodations landing page
• Individual room-type pages (Standard, Deluxe, Suite, Accessible - the accessible room page is required)
• Booking page (where the third-party widget loads)
• Restaurant or dining page (including downloadable menus)
• Spa, pool, or fitness amenity pages
• Meetings and events page (including the proposal-request form)
• Local-area or things-to-do page
• Contact, directions, and parking
• Accessibility statement (if one exists)

That mix covers up to 25 pages for a typical independent or small-chain hotel. The audit runs axe-core 4.10 against each page, captures element-level screenshots of every contrast failure, manually reviews the accessible-room descriptions against the reservation-rule criteria, and packages findings into a written report with copy-paste fix code and 12 re-scans included over 12 months.

Pricing is $149 flat, one-time. To see what the report looks like, view a sample report we built for a fictional ecommerce site. The findings shape (iframe titles, photo alt, color contrast, form labels) is the same shape hotel audits surface; the reservation-rule paragraph is the hotel-specific manual finding layered on top.

Start a hotel website audit, $149

Related:

• Real estate brokerage website accessibility - the iframe-vendor dynamic and photo-gallery patterns overlap heavily
• Restaurant website accessibility - the PDF-menu pattern from restaurants applies directly to hotel restaurant menus
• Free single-page WCAG check
• Why accessibility overlays do not make sites WCAG-compliant
• aria-label on a div: why screen readers ignore it