Hotel Website Accessibility: Booking and Rooms

Opening answer

Hotel website accessibility has two halves that are easy to confuse. One half is the room information itself: room kind, bed count, bathing facility type and communication features. The other half is the booking path: room galleries, a date picker, a booking form and a confirmation step that a guest can complete with a keyboard or a screen reader. The first half fails when room details live only in a photo or a PDF. The second half fails when a date picker cannot be used with a keyboard. Fix room information in HTML first, then work through the booking path in guest order.

Room information belongs in HTML, with enough detail to decide

A guest who needs an accessible room has to judge, from the website, whether a room will work for them. A room card that says only "accessible room" does not give that guest enough to decide. Write room details as plain HTML text on the room page: room type, bed size and count, bathing facility type such as roll-in shower or tub with grab bars, and communication features such as visual alarms. Add route details where they matter, such as step free entry or the path from check-in to the room.

Do not hide those details in a photo caption that a screen reader never reads, and do not hide them only in a PDF fact sheet. Axeazy does not scan PDFs, so a PDF only room fact will not appear in a scan report. Put the room facts in HTML, and offer a PDF only as a print copy of the same facts.

Keep room information consistent across channels. If the hotel site lists a roll-in shower and a third party listing lists a tub, a guest cannot tell which one is right. Send the same descriptions to every booking channel, and update them in the same edit when a room changes.

This is general information, not legal advice. If you received a demand letter or were sued, talk to a qualified attorney.

Room galleries: name what the photo shows

Room galleries fail when every photo has the same alt text, such as "room photo", or no alt text at all. The WAI Images Tutorial sorts the fix by purpose: informative images get a short description, decorative images get an empty alt value so assistive technology skips them, and functional images name the action or destination. A room photo that shows bed layout, bathroom type or step free entry is informative. A thumbnail that opens a larger photo is functional, and its alt text should name the photo it opens.

Do not put bed size, shower type or floor level only inside a photo. Put those facts in text beside the gallery, and let the photo support the text. Keep gallery controls keyboard usable: previous and next buttons need clear names, a visible focus indicator and a target size that meets WCAG 2.2 criterion 2.5.8. A gallery that auto advances also needs a pause control that a keyboard user can reach.

Date pickers are the booking bottleneck

The date picker is the step where most hotel booking flows break for keyboard users. A calendar built from table cells with click handlers and no keyboard support leaves a keyboard user unable to pick a check-in date at all. Test the picker with the mouse put away: tab into the check-in field, open the calendar, move through dates with arrow keys, select a date, and move to check-out without losing focus. If any step traps focus or announces dates with no month or year context, the picker needs work from its provider.

WCAG 2.2 criterion 2.4.11 asks that a component receiving keyboard focus is not entirely hidden by author created content, which covers a sticky booking bar that covers the focused date field. A simple native date input, with a clear label such as "Check-in date", often beats a custom calendar widget, because the browser supplies the keyboard behavior. If a custom picker is kept, it needs a label, a keyboard path to every date, a clear announcement of the selected date, and an error message in text when a date range is invalid.

Booking forms need the same discipline as any other form. The WAI Forms Tutorial pattern applies directly: label each control, group related controls, give instructions before the user acts, validate input and notify the user about errors. ADA guidance on web accessibility makes the same point: online forms need labels that screen readers can convey, clear instructions, and error indicators that state what the error is and how to resolve it. A guest details form should group contact, stay and payment details under clear group labels, state required fields in words, and show errors beside the field in text, not only in red colour.

Booking forms, totals and confirmation

A booking form that asks for the same guest name and address twice wastes time and creates errors. Keep each detail on one step, carry it forward, and show a review step before payment where the guest can check dates, room type, guest count and total, with taxes and fees broken out in text, not only in a small image or a hover tooltip.

Contrast and target size matter most on the payment step. WCAG 2.2 criterion 1.4.3 asks for at least 4.5 to 1 for normal text and 3 to 1 for large text. A light grey total on a white card, or a pale "Pay now" button label, can fail that test while looking clean. Axeazy detects contrast problems and calculates a correct colour, but a visible colour change is never applied without owner approval. Check the pay button target size as well, under criterion 2.5.8, and practice judging small controls with the contrast quiz.

Confirmation needs a plain text page, not only a modal that disappears. After payment, show the booking reference, dates, room type and cancellation terms as HTML text, and send the same details by email. If a modal is used, focus must move into it, and closing it must return focus to a sensible place on the page.

What Axeazy helps with on a hotel site

Axeazy scans with 98 automated checks and fixes code in 14 categories, including form labels, link names, button names and table header structure, per WCAG 2.2. That covers labeled booking fields, named gallery buttons and room rate tables built with proper header cells. For a site with a GitHub repo, fixes arrive as a real pull request with a visible diff to review and merge. Paid plans monitor weekly.

Start with the free scan on Axeazy homepage, which takes about 60 seconds, is homepage only and needs no signup and no card. Then read the Axeazy capabilities page for the full list of scanned categories and limits, including the PDF limit above. That page lists Starter at $29 a month, Pro at $79 a month and Agency at $199 a month as listed figures, so confirm the checkout total before paying, since paid prices are shown at checkout and annual billing saves 20 to 25 percent. For a wider comparison, see best accessibility tools for small business and how to choose an accessibility tool, 10 criteria.

FAQ

What room details should a hotel page list for an accessible room?

List room type, bed size and count, bathing facility type, communication features and any route detail that affects use of the room, in HTML text on the room page. A single word such as "accessible" does not let a guest judge whether the room will work for them.

Why do custom date pickers fail so often?

Because a custom calendar is a complex widget, and keyboard support, focus order and date announcements must be built by hand. A native date input gets much of that behavior from the browser. If a custom picker is kept, test it with a keyboard from check-in to check-out.

Should room facts live in a PDF fact sheet?

No, not as the only copy. Put room facts in HTML on the room page, and offer the PDF as a print copy. Axeazy does not scan PDFs, so a PDF only fact will not show up in a scan report.

What should a hotel do if it receives a demand letter about its website?

This is general information, not legal advice. If you received a demand letter or were sued, talk to a qualified attorney. Keep a dated record of scans and fixes ready for that conversation.

Last checked and sources

Last checked: October 31, 2026.

Sources: WCAG 2.2 from the World Wide Web Consortium, ADA guidance on web accessibility from the Department of Justice, WAI Forms Tutorial, WAI Images Tutorial, Axeazy pricing page, Axeazy capabilities page.

For a first check of the homepage, room pages and booking form, start with the free scan on Axeazy pricing and confirm the checkout total for any paid plan.

Related reading

• Nonprofit Website Accessibility: Donation Forms