Once a booking is done, the hotel experience moves into apps and mobile sites: contactless check-in, in-stay messaging, and digital guides. It is the same shut-out that shows up across self-service platforms, from chain-restaurant ordering to hotel stays, and here is what this one looks like from the customer's side.
This is the second post in a series on hotel website accessibility. The first looked at browsing room options before you book.
Beyond Hotels: The Same Barriers Live in Any Mobile App
Nothing in the account below is specific to hospitality. A code rendered as a styled image instead of real text, a form field with no label, a submit button floating loose at the bottom of the screen, and a confirmation that flashes and vanishes before it is announced are the same defects that appear in banking apps, patient portals, order tracking, and two-factor login screens. If your product asks customers to enter something, confirm something, or read a message that appears on its own, check it on your own screens.
These are also the failures automated testing tends to miss. A scanner can flag a missing label in the code, but it will not tell you that a decorative code is unreadable, that a notification disappeared too fast to hear, or that a button is technically present yet impossible to reach by swipe. That is the gap that catches teams off guard: the audit looked fine, the experience was still broken, and screen reader users, who file the majority of digital accessibility complaints, were the ones who hit it.
Mobile changes constantly, too, and every app release can undo earlier fixes, so this is rarely a one-and-done task. So, as you read one blind traveler's account of using a hotel app, the useful test is whether a screen reader user could finish their own core mobile task, whether that is check-in, checkout, or messaging, with the screen off.
With hotels, the line between the digital and the physical world gets really blurry. Chains, resorts, and smaller properties alike now push almost everything online, from check-in to in-stay requests to check-out. That flexibility is genuinely useful, but every one of these features is only as good as its accessibility, and a lot of them leave me shut out.
In this post, I want to walk through the ones that trip me up most, coming at it as a blind screen reader user and focusing on mobile accessibility, since that is where nearly all of this happens.
Contactless Check-in and Check-out
One of the most useful things modern hotel software does is let me check in at the start of a stay and check out quickly at the end. It is also where I hit some of the worst accessibility problems.
At some properties where the rooms are in separate buildings, I can check in without ever speaking to a front desk agent. I open the hotel's app, connect to the Wi-Fi, finish check-in, and the app gives me a code for the keypad lock on my door.
The first problem is how that code is shown. To make it look nice and catch the eye, it is often set in a large decorative font, sometimes in a very bright color. My screen reader usually cannot read the digits at all, because they are processed as an unlabeled image.
So I am left unable to hear the code to my own room. I understand why hotels want decorative numerals, but for me, it means the one thing I need is the one thing I cannot get.
Some hotels are starting to experiment with using a phone's NFC antenna to talk to the door lock. In theory, I hold the phone near the sensor with the right page open in the app, and the door unlocks.
That only helps me if the button to start it is something my screen reader can find and activate, and so far, that's been hit-or-miss.
Switching to check-out, I can sometimes finish it through the app without going to the lobby. Part of that flow is a prompt to leave an extra tip for housekeeping, and I have found these especially hard to use.
If I want to type a custom tip amount, the text field is sometimes not labeled in the code, so my screen reader skips right over it. Other times, the submit button floats near the bottom of the screen, which makes it very hard to find by touch and almost impossible to reach by swiping.
In-Stay Messaging
Another really useful feature is the ability to message guest relations staff during a stay. I use it for housekeeping, general questions, and checking on room service orders.
The messaging systems are usually proprietary and share little in common, and in my experience, that is where the accessibility problems pile up.
When I send a general question, the hotel often replies with a canned, automated response. For some reason, my screen reader sometimes treats that reply text as an unlabeled image and never reads it out.
In other apps, an incoming reply pops up near the top of the screen for a second and then disappears on its own if I don't act. My screen reader often doesn't announce that anything arrived, so I only find the message by checking the thread manually, which slows down the whole exchange.
Maps, Schedules, and Property Information
Hotel and resort sites and apps usually contain a lot of useful information for mid-stay. That includes amenity hours for the pool or gym, event and shuttle schedules, property maps, and last-minute notices about weather or other changes.
Getting at any of it with a screen reader is often maddening. Calendars and schedules are often built as graphics, which makes them very hard to navigate.
Even when I can hear the numbers and text in a schedule, it usually makes no sense out of order, because moving through it chronologically often breaks, and my focus jumps all over the interface.
At larger resorts, the site often has a facility map showing the layout and marking key spots. I have almost never come across an accessible alternative to those maps, something that would describe in words what the property has and where things sit in relation to each other.
For me, the tools a hotel hands me during a stay matter just as much as the polished website that got me to book. When I can't use them, the trip stops being relaxing and starts being work.
Hotel App Accessibility: Common Questions
Can a screen reader read a hotel's digital room key code?
Screen readers often cannot read a digital room key code when it is displayed as decorative styled text. Hotels frequently display keypad codes in large, colorful fonts that screen readers treat as unlabeled images, leaving a blind guest unable to hear the code for their own room.
Why are hotel contactless check-in and check-out hard for blind guests?
Contactless check-in and check-out often break for blind guests when key steps rely on unlabeled or hard-to-reach controls. Unread key codes, NFC unlock buttons, a screen reader can't activate, and unlabeled tip fields or floating submit buttons can each stop the process cold.
Do hotel in-app messaging systems work with screen readers?
Hotel in-app messaging often fails with screen readers, even when the feature itself is available. Automated replies can be treated as unlabeled images and never read aloud, and pop-up notifications may vanish before a screen reader announces them, causing guests to miss messages entirely.
Are hotel property maps and schedules accessible to screen reader users?
Graphical hotel maps and schedules are frequently inaccessible to screen reader users. Calendars built as images are hard to navigate, chronological order often breaks, so focus jumps around, and property maps rarely offer a text-based alternative describing the layout.
If guests at your own property manage check-in, messaging, or in-stay information through an app or mobile site, these are exactly the barriers worth checking. UsableNet Assistive is a managed service where UsableNet's developers remediate and maintain issues like these on your live site to reduce your legal and operational risk. Speak with a UsableNet accessibility expert to review your guest-facing apps.
