Are QR codes accessible? Designing QR campaigns that work for everyone

Picture the poster you just designed for a client. There is a confident headline, a strong image, and a QR code in the corner that opens the booking page. It tests perfectly on your phone. Now picture the person standing in front of it who is blind, or who has a five-year-old phone that will not scan, or who uses a wheelchair and cannot reach the code mounted at shoulder height. For them, the campaign simply does not exist. The code is a locked door with the key painted on the other side.

QR codes have a quiet accessibility problem, and it is one agencies are well placed to fix because the fixes are cheap, mostly free, and almost entirely about design decisions you already control. This guide explains who a QR-only campaign excludes, what the law does and (importantly) does not require, and the specific, mostly no-cost changes that make a QR campaign work for far more people. We will be careful to separate hard legal requirements from sensible best practice, because the gap between the two is where a lot of confident-sounding but wrong advice lives.

What "accessible" actually means for a QR code

A QR code is, at heart, an image: a grid of squares that means nothing until a camera decodes it. That single fact creates two separate accessibility questions, and they have different answers.

The first is whether someone can reach and use the code at all. Scanning assumes a working camera, a modern phone, the dexterity to hold it steady and aim, the eyesight to find the code, and the knowledge that the little square is even scannable. Take any one of those away and the code becomes a dead end.

The second is what happens after the scan. The destination page is where the real content lives, and a page that fails on contrast, tiny tap targets, unlabelled forms, or screen-reader support excludes people just as effectively as an unscannable code. The scan is only half the journey, and as we will see, the destination is also where the legal responsibility genuinely sits.

Get both halves right and the code works for almost everyone. Ignore either and you have built a campaign with a barrier in the middle of it.

The people a QR-only campaign leaves out

It helps to be concrete about who is affected, because "accessibility" can sound abstract until you count the people.

The World Health Organization estimates that 1.3 billion people, around 16% of the world or one in six, live with a significant disability (this is the WHO's current figure, updated in 2023, and it supersedes the older "one billion / 15%" number you may still see quoted). Separately, the WHO puts the number of people with a near or distance vision impairment at at least 2.2 billion. These are the people for whom a small, unexplained square in a corner is most likely to be a problem.

Then there is the device gap. Scanning assumes a smartphone, and not everyone has one. In the United States, Pew Research finds that while smartphone ownership is near-universal among younger adults, it drops to around 78% of those aged 65 and over, and to about 82% among the lowest-income households. So roughly one in five older Americans cannot scan your code at all, regardless of how well it is designed. A 2021 YouGov poll (dated, but directionally useful) found a meaningful share of older adults found QR codes difficult or had never heard of them.

Beyond vision and devices, there are motor and dexterity barriers (aiming a camera steadily is hard with a tremor or limited hand control), and cognitive ones (an unlabelled code gives no clue what it is or what it will do). None of these groups is niche. Together they are a large slice of the audience your client is paying you to reach.

What the law actually says, and what it does not

This is where agencies most need a clear head, because the topic attracts a lot of overstatement. Let us separate what is genuinely required from what is good practice.

In the European Union, the European Accessibility Act (Directive (EU) 2019/882) applies from 28 June 2025. It sets accessibility requirements for a defined list of products and services, including e-commerce, consumer banking, electronic communications, e-books, and elements of transport services. It binds economic operators (manufacturers, importers, distributors, and service providers), with a narrow exemption for microenterprises that provide services. The technical yardstick behind it is the harmonised standard EN 301 549, which in turn incorporates the Web Content Accessibility Guidelines (WCAG).

Here is the crucial nuance that most QR accessibility advice gets wrong. Neither the European Accessibility Act nor EN 301 549 mentions QR codes at all. No EU law bans QR codes, and none requires you to print a URL next to one. What the EAA regulates is the accessibility of the digital service at the end of the journey. So if a QR code is the only way to reach an in-scope service (say, a banking or e-commerce flow), and that service is not accessible, the problem is the service, and a sole QR entry point makes the barrier worse. The sensible reading is not "the law mandates a printed URL" but "if the destination must be accessible, do not gate it behind a single method that excludes people."

WCAG itself reinforces the split. WCAG governs digital content only; it never mentions print. So a QR code rendered on a screen (in an email, a PDF, a web page) is squarely in scope, and so is the landing page, but a code printed on a poster is not directly governed by WCAG at all. The most relevant success criterion for an on-screen code is 1.1.1 Non-text Content (Level A), which requires a text alternative for non-text content. In practice that means an on-screen QR needs real alt text and, more importantly, a real clickable link beside it, because a screen-reader user cannot scan a code displayed on the very screen they are reading.

In the United States, the picture is similar in spirit. The Department of Justice holds that the Americans with Disabilities Act covers web content, and its April 2024 Title II rule adopts WCAG 2.1 Level AA for the websites and apps of state and local governments. (Those compliance deadlines were pushed back a year by a 2026 interim rule, to April 2027 for larger entities and April 2028 for smaller ones, so ignore any guide still quoting 2026 or 2027 as the original dates.) For private businesses there is no single codified numeric standard, but heavy litigation under Title III means WCAG 2.1 / 2.2 AA is the de facto benchmark for any public-facing site. Again, the law bites on the digital destination, not on the printed square.

The honest summary: treat a printed text alternative as strong best practice rather than a legal mandate, and treat the destination page as the place where real legal exposure lives. That framing keeps you both compliant and credible with clients.

Make the code itself more inclusive

Most of what makes a QR code inclusive costs nothing and is decided at design time. The single most important principle, repeated by every serious accessibility source from the US Section 508 programme to specialist consultancies, is this: never make the QR code the only route.

The numbered callouts in the diagram map to the points below:

1. The code itself, kept dark on a light background with a full quiet zone, so it scans on the widest range of devices. (For the detail on sizing and contrast, see our guide on how big a QR code should be; for getting it right on press, preparing a QR code for print.)
2. A short, human-readable URL printed beside the code. This is the parallel route: anyone who cannot or will not scan can still type the link. Keep it short and memorable, which is another argument for a tidy dynamic short link over a sprawling tracked URL.
3. A plain-language call to action that says what the code is and what it does, for example "Scan to read the menu, or visit example.com/menu". This single line helps sighted users, screen-reader users (when the code is digital), and anyone unsure whether the square is even meant to be scanned.
4. Placement within comfortable reach. There is no print-specific law here, but the ADA's reach ranges for operable controls (a low of 15 inches and a high of 48 inches, roughly 380 to 1220 mm) are a sensible analogy: a code a wheelchair user or a shorter person cannot get a phone in front of is a code they cannot use. Avoid glare-heavy surfaces and unreachable heights.
5. An accessible destination, which the next section covers.

A few more specifics worth stating plainly. Avoid inverted (light-on-dark) codes: many scanners struggle with them, so they hurt everyone, not only users with impairments. If you have ever debugged this, our piece on why a QR code will not scan walks through the common causes. Print the code large enough to be found and aimed at easily; a bigger code helps low-vision users and anyone with shaky hands, not just the scanner. For codes shown on screens (web, email, PDF), give the image real alt text that identifies it as a QR code and, crucially, pair it with a genuine clickable link, since a screen-reader user has no way to scan their own display. And where it fits the campaign, an NFC tap can be a useful complementary modality because it removes the aim-the-camera step that is hardest for some motor and vision impairments; our QR versus NFC comparison covers the trade-offs. NFC is a complement, not a replacement, since not every phone has it.

Do not forget the destination page

You can do everything above perfectly and still exclude people if the page behind the code fails. The destination is squarely in WCAG and EAA scope, and it is where the legal responsibility actually concentrates, so it deserves the same care as the code.

At a minimum, the landing page should meet WCAG 2.1 / 2.2 Level AA. In practical terms: text contrast of at least 4.5:1 for normal text and 3:1 for large text; interactive tap targets of at least 24 by 24 CSS pixels (the new WCAG 2.2 minimum, with 44 by 44 the enhanced target, echoed by Apple's 44pt and Google's 48dp platform guidance); properly labelled form fields for any lead capture; and full mobile and screen-reader support. Our guide to QR code landing pages goes deeper on the post-scan experience. Accessibility and GDPR also overlap here, since both govern what happens on that page; if that is on your radar, see are QR codes GDPR compliant.

When you find a problem after the run is printed

Accessibility audits often happen after a campaign is live, which is exactly when a static QR code becomes a trap: if the page it points to fails an audit, the only fix is a reprint. A dynamic code avoids that. Because its destination is an editable redirect rather than a fixed URL baked into the pattern, you can repair the landing page or repoint the code to an accessible version without touching the printed artwork. The printed glyph stays valid while you fix what is behind it. That is not a marketing flourish; it is an inherent property of redirect-based codes, and it is the difference between an accessibility finding being a quick dashboard edit and being a five-figure reprint. Our walkthrough on changing a QR code's destination without reprinting covers the mechanics.

A pre-launch accessibility checklist

Before a QR campaign goes to print or live, run it past these eight points:

1. The code is never the only route: a short typed URL is printed or shown beside it.
2. A plain-language call to action explains what the code is and what it does.
3. The code is dark on light, high contrast, with a full quiet zone, and not inverted.
4. The code is printed large enough to find and aim at easily.
5. It is placed within comfortable reach and away from glare and unreachable heights.
6. On any screen, email, or PDF, the code image has real alt text and a genuine clickable link.
7. The destination page meets WCAG 2.1 / 2.2 AA: contrast, tap targets, labelled forms, mobile, screen reader.
8. The code is dynamic, so an accessibility fix to the destination never needs a reprint.

Frequently asked questions

Are QR codes accessible to blind people?

Not on their own. A printed code is invisible to a screen reader, and a code shown on a screen cannot be scanned by someone using that same screen. The fix is to always provide the destination as a real, typed link (with proper alt text when the code is digital), so a blind or low-vision user can reach the same place without scanning. This maps to WCAG success criterion 1.1.1, Non-text Content.

Are QR codes ADA compliant?

The code itself is not really the unit of compliance; the digital destination is. Under the US Department of Justice's 2024 Title II rule, state and local government websites and apps must meet WCAG 2.1 Level AA, and for private businesses WCAG 2.1 / 2.2 AA is the de facto benchmark through ADA litigation. So "ADA compliant" applies to the page the code opens, not to the square of pixels. Make that page accessible and pair the code with a typed alternative.

Does the European Accessibility Act apply to QR codes?

The European Accessibility Act applies from 28 June 2025, but it does not mention QR codes and does not ban them. It regulates the accessibility of certain digital products and services (e-commerce, banking, e-books, and more). If a QR code is the only way to reach an in-scope service, that service still has to be accessible, so offering a parallel route and an accessible destination is the prudent way to stay on the right side of it.

What contrast ratio does a QR code need?

For the code itself there is no strict WCAG figure, because a QR is not text and not cleanly a UI component; the practical rule is dark modules on a light background, the higher the contrast the better the scan. WCAG's contrast ratios (4.5:1 for normal text, 3:1 for large text and non-text elements) apply to the labels around the code and to the landing page, not to the QR graphic itself.

How do you add alt text to a QR code?

Only when the code is digital. For a QR code shown on a web page, in an email, or in a PDF, add alt text to the image that says it is a QR code and where it leads, and provide a real clickable link as well. A printed QR code has no alt text (alt text is a digital concept); its equivalent is a visible printed URL and a short caption explaining the code.

How high should a QR code be placed for wheelchair users?

There is no print-specific legal rule, but the ADA's reach ranges for operable controls are a good guide: a usable height sits roughly between 15 inches (380 mm) low and 48 inches (1220 mm) high. The point is simply that a code mounted too high or too low, or behind glare, is one that some people cannot physically get a phone in front of.

How do dynamic QR codes help with accessibility?

A dynamic code points to an editable redirect rather than a fixed URL, so if an accessibility audit finds the destination page wanting, you can fix or replace that page without reprinting the code. It turns an accessibility problem from a reprint into a dashboard edit, which makes it far more likely the fix actually gets made.

The short version

A QR code is an image, and an image alone excludes anyone who cannot scan it: blind and low-vision users, the roughly one in five older adults without a smartphone, and people for whom aiming a camera is hard. The single most important fix is to never make the code the only route, so always pair it with a short typed URL and a plain-language call to action. Keep the code dark on light with a full quiet zone, print it large, and place it within reach. On screens, give it real alt text and a genuine link. Then make the destination page meet WCAG 2.1 / 2.2 AA, because that is where both the real exclusion and the real legal responsibility sit, while remembering that the law governs the digital destination, not the printed square. Use a dynamic code so any accessibility fix is an edit, not a reprint. Do that, and the campaign you hand your client works for the whole audience, not just the part of it holding a new phone.