QR Codes and Accessibility: Who Cannot Scan, and What to Do About It

A QR code is a visual object that requires a camera, a modern phone, a working data connection, steady hands and enough light. Each of those is a filter, and the filters overlap. This is the article the industry does not write, because the honest version says a code excludes people and most of the remedies involve doing slightly less with it, not buying something.

Who actually cannot scan

• Blind and low-vision customers. A code gives no clue that it exists, no clue where it is, and no clue what it will do. A screen reader cannot see a square on a table tent.
• People with tremor or limited dexterity. Scanning means holding a phone steady at a distance for a couple of seconds. That is not free for everyone.
• Wheelchair users and children. A code at standing eye level on a wall may be unreadable from a seated position at an angle, and reach matters as much as height.
• Older customers. Not because of capability — because of unfamiliarity, older cameras that focus poorly at close range, and small print in the caption.
• Anyone without a usable phone right now. No data, no battery, no signal in a basement restaurant, a work phone with the camera locked down, a child, a tourist avoiding roaming.

The rule that matters more than all the others

A QR code should be a shortcut, never the only route. If the information behind it is something a person needs — the menu, the price, the safety instructions, the timetable, the way to pay, the way to complain — then it must also exist in a form that does not require a scan.

Everything below is detail. This is the principle, and it is the one most often broken by exactly the businesses that adopt codes fastest.

Fixes that cost nothing

• Print the address. One short line under the code. It rescues the dead battery, the borrowed device, the person who will type but not scan, and the one whose camera app refuses.
• Say what it does. "Scan for the menu" is not decoration — it is the only way a person can decide whether the effort is worth it. It also lets a companion read it aloud.
• Size and contrast generously. The size that works for a low-vision customer is the size that works in bad light for everyone. Our editor measures contrast by luminance rather than colour, which is the same reason a pale-on-pale code fails for a camera and for a human eye.
• Put it where a seated person can reach it. Roughly waist-to-chest height on a wall, or on the table rather than above it. A code at 1.8 m is a code for tall standing adults.
• Do not put it behind glass in a dark corner. Reflection and low light hurt everyone, and hurt low-vision customers first.
• Never make it time-pressured. A code on a slide that vanishes in four seconds, or at a queue where people are waiting behind, is a code most people will not attempt.

The destination is where most of the accessibility lives

This is the part almost everyone gets wrong, and it defeats every good decision above.

• A photo of a menu is not a menu. A JPEG or a scanned PDF of a printed card is unreadable to a screen reader, cannot be enlarged without going blurry, and cannot be re-flowed to a phone screen. It is the single most common accessibility failure in the entire category — and restaurants are the biggest users of QR codes. Real text, in HTML, is the fix.
• It has to work on a phone. Every scan is mobile by definition, so a desktop layout that needs pinching is a page that fails everybody, disabled or not.
• Do not require an app. "Download our app to see the menu" turns a two-second task into a five-minute one, and excludes anyone short of storage or on an old device.
• Do not require a login for information that was public on paper a year ago.
• Let people zoom. A page that blocks pinch-zoom is hostile to low-vision users and is trivially avoidable.

Where a physical alternative earns its place

• NFC alongside the code. A tap needs no aiming, no focus and no light, which makes it easier for tremor, low vision and old cameras alike. It is a genuine complement — but it is not universal either, so it does not replace the printed address.
• A tactile marker. A raised symbol or braille label beside the code tells a blind customer that something is there at all. The code itself gives no such signal.
• Keep some paper. A handful of printed menus behind the bar costs almost nothing and covers every case at once. Businesses that removed paper entirely usually did it to save money and quietly lost customers who could not say why they stopped coming.
• A person. Staff who will read the thing aloud, without being asked twice, is a real accessibility feature and the one nobody budgets for.

Codes in documents and on screens

• Give the code an alt text when it sits in a web page, an email or a PDF — describe the destination, not the picture: "QR code linking to the summer menu" and, better still, put the link next to it as text. A screen reader can follow a link; it cannot scan a square.
• Do not put a code in a document that will be read on a screen. The reader is already holding the device. A link is one tap; a code is a manoeuvre with a second phone.

A short checklist

1. Is there a route to this information without a phone? If not, fix that first.
2. Is the address printed under the code?
3. Does the caption say what the code does?
4. Can someone seated reach and read it, in the light that is actually there?
5. Is the destination real text on a mobile page, not an image or a PDF?
6. Does it work without an app and without a login?

Quick answers

• Are QR codes accessible? Not on their own. They are usable for many people and impossible for some, which is why they belong beside another route rather than in place of one.
• Can a blind person scan a QR code? Some can with assistive apps, but the code gives no signal that it exists or where. A tactile marker and a printed address help; removing the alternative does not.
• What is the single biggest mistake? A photo or PDF of a menu instead of real text.
• Is NFC better? Easier for many people, and worth adding — but not universal, so it is an addition, not a replacement.
• What height should a code be? Reachable and readable from a seated position — roughly waist-to-chest on a wall, or on the table itself.
• Do we have to keep paper menus? Nothing here forces it, but a few printed copies cover every failure case at once and cost almost nothing.