Hotel Websites and the ADA: Site Accessibility vs. Room Booking Rules
Short answer: Hotel websites can raise two distinct ADA issues: general website accessibility (evaluated against WCAG guidelines) and a specific reservations regulation, 28 CFR 36.302(e), which requires hotels to describe accessible room features online and let guests book those rooms the same way as any other room. Addressing one does not automatically address the other.
Two different problems, often confused
Hotel websites sit at the intersection of two separate accessibility obligations, and it's easy to conflate them. The first is general website accessibility: can a visitor using a screen reader, keyboard-only navigation, or magnification actually use the site? This is typically measured against the Web Content Accessibility Guidelines (WCAG), currently the reference standard courts and regulators point to even though the ADA itself doesn't name a specific technical standard.
The second is narrower and specific to lodging: a Department of Justice regulation, 28 CFR 36.302(e), that addresses how hotels describe and let guests reserve accessible rooms. This rule exists independently of general web accessibility and applies even to a site that scores well on a WCAG audit.
A hotel can have a reasonably accessible website in the WCAG sense and still be out of compliance with the reservations rule, or vice versa. Fixing a color-contrast issue doesn't touch the reservations requirement, and adding accessible-room descriptions doesn't fix a broken screen-reader experience. They need to be handled as two separate checklists.
This guide walks through both. It is general information, not legal advice — if you've received a demand letter or are unsure how a specific requirement applies to your property, talk to an attorney who handles ADA matters.
Part 1: The reservations rule (28 CFR 36.302(e))
What the rule covers, in general terms
The Department of Justice's regulations implementing Title III of the ADA include a provision specific to places of lodging. In general terms, it requires hotels to:
- Identify and describe accessible features in the hotel and guest rooms in enough detail for a guest to reasonably assess whether a room meets their needs
- Make accessible rooms bookable through the same reservations channels used by everyone else — website, phone, third-party booking sites, and so on
- Ensure accessible rooms are actually held for guests with disabilities and not released to general inventory in ways that undercut their availability
- Reserve the specific accessible room type booked, not just "an accessible room" in some general category
This is a simplified summary. The regulatory text and DOJ guidance go into more detail than fits here, and how a given requirement applies can depend on the number of rooms, the type of property, and other specifics. If you want the source language, ada.gov publishes the regulation and related guidance documents.
What "describing accessible features" tends to mean in practice
Common gaps found on hotel booking pages include:
- Accessible rooms listed by name only ("ADA King") with no description of what makes them accessible
- No mention of specific features: roll-in shower vs. tub with grab bars, bed height, doorway width, visual alarms, or communication features for guests who are deaf or hard of hearing
- Accessible room types bundled into a generic "special requests" field instead of being a selectable room category
- Accessible rooms shown as unavailable on the online booking engine while the same room type is available by phone, or discovered only to be available by phone at all, which conflicts with the same-channel booking requirement
A simple internal check
| Question | Why it matters |
|---|---|
| Can a guest see which specific accessible features a room has before booking, not just an ADA label? | Guests need enough detail to judge fit for their own needs |
| Can accessible rooms be booked online, the same as any other room, without calling a separate line? | The rule requires the same reservations channels |
| Does the description match what's actually in the room? | Mismatches between the listing and reality are a recurring complaint source |
| Is the specific room type booked actually held for that guest? | Releasing accessible rooms to general inventory undercuts the requirement |
This is a general orientation, not a compliance audit. Confirming your specific booking flow meets the regulation is a legal and operational question best reviewed with counsel or a specialist familiar with hospitality reservations systems.
Part 2: General website accessibility (WCAG)
Separately from the reservations rule, the hotel's website as a whole — homepage, room pages, gallery, amenities pages, dining, spa, event booking — is a website like any other, and gets evaluated the same way: against WCAG 2.1 Level AA. For a fuller walkthrough of what that standard covers, see the WCAG 2.1 AA checklist.
Where hotel sites commonly run into trouble
Image-heavy content without text alternatives. Hotel sites lean heavily on photography — room interiors, pools, event spaces — and it's common for none of it to have meaningful alt text, which fails WCAG 1.1.1 Non-text Content.
Booking widgets that don't work with a keyboard. Date pickers, guest-count steppers, and room-type selectors are frequently built as custom widgets that trap keyboard focus or can't be operated at all without a mouse, which relates to WCAG 2.1.1 Keyboard and WCAG 2.4.7 Focus Visible.
Low-contrast text over photo backgrounds. Overlaying white or light-colored text on hero images looks clean but often fails WCAG 1.4.3 Contrast (Minimum), especially on room-rate banners and promotional callouts.
Video content for virtual tours or amenities without captions. Property tour videos and promotional reels are increasingly common and are frequently posted without captions, which relates to WCAG 1.2.2 Captions (Prerecorded).
Forms without clear labels. Reservation forms, event inquiry forms, and newsletter signups sometimes rely on placeholder text instead of real labels, which fails WCAG 3.3.2 Labels or Instructions.
Vague or repeated link text. "Book Now" repeated dozens of times across a page without distinguishing context can leave screen reader users unable to tell one link from another out of context, relevant to WCAG 2.4.4 Link Purpose (In Context).
Other structural basics worth checking include page titles that identify each page (WCAG 2.4.2 Page Titled), a way to skip repeated navigation (WCAG 2.4.1 Bypass Blocks), a correctly declared page language (WCAG 3.1.1 Language of Page), proper heading and landmark structure (WCAG 1.3.1 Info and Relationships), text that can be resized without breaking layout (WCAG 1.4.4 Resize Text), and interactive components that expose their role and state to assistive technology (WCAG 4.1.2 Name, Role, Value).
Third-party booking engines complicate things
Many hotels don't control their own booking flow directly — it's handed off to a third-party reservations platform or a property management system's hosted widget. This matters for both parts of this guide: accessibility problems in a booking engine you don't control still affect your guests and your site's overall accessibility, and the same-channel requirement in 36.302(e) doesn't go away just because the reservations system belongs to a vendor. It's worth asking any booking-engine vendor directly whether their platform has been tested for WCAG conformance and whether accessible room types and descriptions can be configured and booked through the same interface as standard rooms.
If you received a demand letter
Hotels are a frequent target of ADA website demand letters, partly because lodging has this additional, specific regulatory requirement beyond general web accessibility. If you've received one, our guide on understanding an ADA website demand letter walks through typical next steps, and ADA website lawsuits explained covers the broader legal landscape. You can also see aggregate filing trends on our federal filing tracker.
Whatever the letter alleges, the two issues in this guide are worth checking separately: is the general site accessible, and does the reservations flow actually meet the accessible-rooms requirement? A demand letter focused on WCAG issues doesn't tell you whether your booking engine is compliant with 36.302(e), and vice versa.
Keeping a dated record of when accessibility issues were identified and addressed can also help demonstrate a good-faith, ongoing effort. See our guide on keeping a dated accessibility audit record for more on why that matters. If you want a starting point for the WCAG side of your site, you can run a free scan to get a baseline.
Frequently asked questions
Does WCAG conformance satisfy the ADA's hotel reservations rule?
No. WCAG conformance addresses general website usability — things like alt text, keyboard access, and contrast — while the reservations rule in 28 CFR 36.302(e) is a separate, specific requirement about describing accessible rooms and letting guests book them through the same channels as anyone else. A site can conform well to WCAG and still fail to meet the reservations rule if, for example, accessible rooms can't be booked online.
Do small, independently owned hotels have to follow the reservations rule?
The ADA's Title III requirements generally apply to places of lodging that qualify as public accommodations, which covers most hotels and motels, though details can depend on size and other factors. Because the specifics vary and the regulation has real operational consequences, it's worth confirming your obligations with an attorney rather than assuming based on property size alone.
What counts as "the same reservations channels" for accessible rooms?
In general, it means a guest shouldn't have to call a separate phone line or email a special-requests inbox to book an accessible room if other guests can book standard rooms online. If your accessible room types aren't selectable and bookable through your normal website or app flow, that's typically a sign the requirement isn't being met, though exact application can depend on your booking setup.
Are third-party booking engines exempt from these rules?
No. Handing reservations off to a third-party platform doesn't remove the hotel's obligations under either WCAG-style accessibility expectations or the reservations regulation. It's reasonable to ask a booking-engine vendor directly whether their platform supports accessible room descriptions and same-channel booking, since you may need to work with them to fix gaps.
Where can I read the actual regulation instead of a summary?
The Department of Justice publishes the ADA's Title III regulations, including the lodging-specific reservations rule, at ada.gov. Reading the source text — or having an attorney review it against your specific booking setup — is a good next step if a demand letter or an internal review has raised questions about compliance.
Related
- Got an ADA website demand letter? What to do in the first two weeks
- WCAG 2.1 AA checklist for business websites
- Restaurant website accessibility: menus, ordering and reservations
- Why a dated accessibility audit record matters
Proof of Access provides technical accessibility assessments. We are not a law firm and nothing on this page is legal advice. If you have received a demand letter or a lawsuit, talk to an attorney.