01Date pickers that cannot be typed into
Calendar widgets that only accept mouse clicks make booking impossible without a mouse.
What to do: Allow a typed date as well. If your engine will not, say so to the vendor and publish a phone alternative.
Hotel website accessibility: the booking engine is the whole business
Hotel sites are mostly a shell around a third-party booking engine, and that engine is where the failures live. It is also the part you control least.
Why it matters here specifically. Guests with accessibility needs research harder than anyone else because the stakes of getting it wrong are higher for them. A site that will not tell them whether a room is accessible loses them at the research stage.
What fails on sites like yours
02No accessibility information about the rooms
Not a WCAG failure, but the single most common complaint from disabled travellers: they cannot find out whether the bathroom has a step.
What to do: Publish a clear accessibility page: step-free routes, doorway widths, bathroom layout, lift access. This wins bookings.
03Image galleries with no descriptions
Room photographs carry the information the booking decision rests on.
What to do: Describe what the room contains, not 'room 1', 'room 2'.
04Auto-playing background video
Motion that cannot be paused causes discomfort for people with vestibular conditions.
What to do: Respect the reduce-motion setting and add a pause control.
Check your own site in fifteen seconds
Free, no signup, and the report explains every finding in plain English rather than developer shorthand.
Scan my page