A QR code is accessible only if everyone who encounters it can physically reach it, see or sense it, scan it, and use the page it opens. That means thinking about placement height, size, contrast and glare, alternatives for people who cannot scan at all, and an accessible destination once the scan succeeds. This article walks through each step and ends with a checklist you can apply before printing or publishing anything.
Start with the question: is a QR code the right tool?
Before worrying about placement and contrast, ask whether a QR code is needed at all. A code is a shortcut, not a requirement. If the information behind it is essential — a restaurant menu, a bus timetable, safety instructions, a form people must complete — the code cannot be the only path to it. People with no smartphone, a flat battery, a damaged camera, low vision that makes camera aiming difficult, or simple reluctance to scan will all be locked out unless you provide another route.
A good rule of thumb: treat the QR code as a convenience layer on top of a fully accessible base, never as the base itself. That base can be a printed short link, a phone number, a staffed counter, a paper copy, or a sign with the same content written out. Adding a code on top of that costs little; removing the base costs some customers everything.
Physical placement: height, distance, and reach
Scanning is a physical act. Someone has to hold a phone steady at a workable distance, aim the camera, and hold still long enough for the camera to focus. That is hard to do when the code is mounted where a person cannot comfortably stand or sit while facing it.
Height
A commonly used rule of thumb for signs and interactive elements is to keep them roughly between 40 and 120 centimetres (about 16 to 48 inches) from the ground. This range works for people seated in wheelchairs, people of short stature, and people who simply cannot bend or reach upward. Codes placed very low — near the floor on a wall or on a step — force people to crouch or bend, which is difficult or impossible for many. Codes placed above head height are worse: the camera angle becomes awkward and the distance grows.
If the code sits on a table, on a counter, or on a product, the same thinking applies: put it where a seated person can bring their phone to it flat-on, without leaning across something or reaching behind glass.
Distance and angle
The larger the code, the farther away it can be scanned. A rough guide many printers use is a scanning distance of about ten times the code's width: a 10 cm code is comfortable from about a metre, a 25 cm code from about 2.5 metres. For codes meant to be scanned from a queue or from a seat — on a wall, a pillar, a table tent — size generously. A code that only scans from 20 centimetres away is useless on a poster.
Also consider the angle. Codes behind glass, on curved surfaces, or recessed into displays often fail because of reflection or distortion. Mount the code flat where possible, and test it from a seated position, not just standing.
Obstruction
Nothing should cover the code or require a step to reach. A code on the inside of a door that must be pulled open, a code behind a counter people cannot approach, or a code tucked under a shelf lip all create barriers. Walk the route a first-time visitor would take and check the code is reachable and scannable at every point where you expect it to be used.
Size and quiet zone
Small codes fail in two ways: the camera cannot resolve them, and people with tremors, limited hand control, or low vision struggle to aim at a tiny target. For anything scanned by the public from a distance, keep the printed code at least 2 by 2 centimetres even at close range, and scale up with distance as described above. Codes on business cards or receipts can be small; codes on signage should not be.
Leave a clear margin — the "quiet zone" — around the code. Most generators add this automatically; if you crop the code tightly into a design, scanners may refuse it. A margin of roughly four modules (the small squares) of the code on each side is the usual guidance.
Avoid placing text, logos, or decorative elements so close that they crowd the code. A cluttered sign makes it harder for people with low vision or cognitive disabilities to find and target the code in the first place.
Contrast, colour, and glare
QR scanners read the contrast between the dark modules and the light background. Dark code on a light background works best. Reversed codes (light on dark) can work but are less reliably scanned by some cameras, so test thoroughly before committing.
Practical rules:
- Use dark modules on a plain light background. Black on white is the most reliable combination.
- Avoid low-contrast pairings such as pale grey on white, pastel on pastel, or light gold on cream.
- Avoid placing the code over photographs, patterns, or gradients. If a design overlay is unavoidable, put the code in a solid, plain box.
- Do not rely on colour alone to distinguish the code from its surroundings; colour-blind users and washed-out printing both break that assumption.
- Matte finishes beat glossy ones. Glossy paper, laminated surfaces, and glass create glare that hides modules from the camera, especially under direct lighting or sunlight. If lamination is required for durability, choose a matte or anti-glare finish.
- Test the printed code in the actual lighting conditions of the location — a code that scans under office light may fail under a window's backlight or a spotlight.
Tactile and audio alternatives
Some people cannot see the code at all, and some cannot use a touchscreen camera reliably. For them, the code itself is invisible; what matters is what surrounds it and what else is available.
Tactile cues
A raised or textured border around the code, or a braille label beside it saying what it is and where it leads, helps blind and low-vision people find and understand it. Tactile signage standards exist in many countries; a local signmaker or accessibility consultant can advise on braille dot sizing and placement. Even without braille, a raised frame signals "there is something here to interact with."
Note that a QR code itself is not reliably readable by touch — the modules are too small and flat. Do not treat the printed code as a tactile feature.
Audio alternatives
Where audio is feasible — a staffed reception, a help point, a phone line — offer it. Printing a phone number next to the code is the simplest version: someone who cannot scan can call and get the information or be directed to it. In venues with staff, brief the team on what each code opens so they can help on request.
NFC and other options
NFC tags, which trigger a link when tapped with a phone, can complement QR codes and are easier for some people with low vision to use, since tapping a marked spot requires less aiming than scanning. They are not a universal replacement — not all phones or situations support them — but as one of several paths they can help.
Always pair the code with plain text
Every public QR code should be accompanied by:
- A short label saying what it opens: "Scan for today's menu", "Scan to view the bus timetable", "Scan to report a fault". Never leave a bare code without explanation.
- The destination as a printed short link, e.g. a short, memorable URL that can be typed by hand. Keep it genuinely short — a long, cryptic URL defeats the purpose.
- Where relevant, a phone number or the name of a staffed location where the same information is available.
This pairing serves multiple groups at once: people without smartphones, people who cannot scan, people who prefer to type, and people who want to know what they are about to open before opening it. The last point matters for trust as well as accessibility — a labelled code is a code people will actually use.
For essential information such as menus, timetables, and safety instructions, also provide a non-digital copy: a printed menu on request, a posted timetable, a paper safety sheet. Digital-only delivery of essential information excludes people without devices and fails people in a hurry.
The landing page must be accessible too
A perfectly placed, high-contrast, well-labelled code leading to an inaccessible website has only moved the barrier. Before linking a code to any page, check the basics:
- The page works with a screen reader: meaningful headings, text alternatives for images, labelled form fields, and a sensible reading order.
- Text can be resized without breaking the layout, and colour contrast between text and background is strong.
- The page is usable on a small phone screen, since every visitor arrives on one.
- Forms have clear labels, visible error messages, and do not depend on tiny tap targets.
- Video content has captions; audio content has a transcript where practical.
- The page does not hijack zoom, block scrolling, or auto-play loud media.
If you do not control the destination — for example, a third-party booking system — choose one that is accessible, and if it is not, keep a human alternative available. When sending people to a page, prefer a dedicated, simple landing page over a sprawling homepage; fewer distractions help everyone, especially screen-reader users and people with cognitive disabilities.
Also make the link behave sensibly: the code should open a mobile-friendly page directly, not a PDF (which is often poorly accessible and awkward on phones), not an app-store wall, and not a page requiring an account for basic information.
Testing with real people and real conditions
Test the way your users will, not the way you print. Stand where a visitor stands; sit where a seated visitor sits. Scan with an older phone if you can. Try in bright sun, under artificial light, and at night for outdoor codes. Ask someone who uses a screen reader to try the landing page. Ask someone who has never seen the sign whether the label tells them enough to want to scan.
Small usability failures — a code that needs three attempts, a label that doesn't say what the page is, a link that opens slowly on mobile data — disproportionately affect people with disabilities, older adults, and anyone in a stressful or rushed situation. Fixing them helps everyone.
Pre-publish checklist
Use this list before printing or mounting any public QR code:
- The code is placed roughly 40–120 cm from the ground, or wherever a seated person can reach it comfortably.
- The code can be scanned from the distance a real user will be at (rough guide: scanning distance about ten times the code's width).
- The code is at least 2 × 2 cm for close-range use, larger for distance scanning.
- There is a clear quiet zone around the code and no overlapping graphics or patterns.
- Dark modules on a plain light background; strong contrast; matte, non-glare surface.
- Tested in the location's actual lighting, from a seated and standing position.
- A plain-text label next to the code says what it opens.
- A short, typable URL is printed alongside the code.
- A phone number or staffed alternative is available where the information is essential.
- Essential content (menus, timetables, safety information) also exists in a non-digital form.
- Tactile or braille labelling considered for fixed signage.
- The landing page is mobile-friendly and works with a screen reader, zoom, and large text.
- The code opens the content directly — no PDF-only menus, forced app installs, or account walls for basic information.
- Tested with at least one person who has not seen the sign before.
Conclusion
The key takeaway: a QR code is an accessible tool only as part of a system. Place it where everyone can reach it, print it large and high-contrast on a non-glare surface, label it clearly, and — most importantly — never let it be the only way to get information people need. Pair every code with a short printed link, a phone number, or a paper alternative, and make sure the page it opens works for screen-reader and low-vision users. Do that, and the code becomes a genuine convenience rather than a new barrier.