What contrast ratio applies to QR codes under WCAG?

For a digital QR graphic required to understand or use a web page, WCAG 2.2 Success Criterion 1.4.11 calls for at least 3:1 contrast against adjacent colors. It is not a blanket print rule. Physical codes should use stronger contrast where practical and be tested in their final setting.

Can a QR code be the only way to access a service?

The answer depends on the service, jurisdiction, and user need. The EAA and ADA impose scoped accessibility or effective-communication duties rather than a universal QR-specific ban. A readable URL, telephone option, accessible website, or staff-assisted route may be needed to provide equivalent access in a covered context.

What height should be used for accessible QR code signs?

No single mounting height fits every jurisdiction and setting. Put the code within the reach and sight range of intended users, avoid glare and obstructions, and check applicable building or signage rules. Test the placement with wheelchair users and people using camera magnification before permanent installation.

What alt text should be used for a QR code image?

Describe the action and destination, not the square pattern itself, for example, “QR code to download the allergen menu PDF.” If the adjacent link already provides the same action, avoid redundant wording. The destination must also be available as an ordinary accessible link so scanning is not required online.

Does the European Accessibility Act cover QR codes?

It has no QR-specific rule. If scanning leads to a digital service inside the Act's scope, such as e-commerce, that service must meet its accessibility requirements. Secondary sources report an application date of 28 June 2025 and a narrow microenterprise exemption for services. Check the Directive and your national law.

How do blind users scan a QR code?

Many use the built-in phone camera with VoiceOver on iPhone or TalkBack on Android, which can speak the detected link. Finding and aiming at a flat printed square is the hard part, so provide a text label, a readable URL or a staff-assisted route. Menu steps vary by device, so verify them on current software.

Do I need a printed URL next to every QR code?

It is a cheap and widely recommended safeguard. A GSA bulletin on Section 508 recommends a nearby link or URL, and the Bureau of Internet Accessibility suggests offering a manual option. A short readable URL helps people without a working camera or compatible phone, though a long URL can be hard to type.

How should I test whether a QR sign is accessible?

Test the finished sign in place. Scan it with several phones at realistic distances and lighting, check reach from seated and standing positions, then complete the destination task using a keyboard, magnification and a screen reader. Try the fallback separately, and ask disabled users to repeat the journey before permanent installation.

QR Code Accessibility Guide: WCAG Contrast & EAA Standards

An accessible QR experience gives people a clear reason to scan, a placement they can reach and read, a destination that works with assistive technology, and another way to finish the same task. The printed square cannot make a service accessible on its own, so treat the sign, the phone interaction, the web page and the fallback as one journey.

This guide walks through that journey: where accessibility laws and standards apply, what contrast guidance covers, how to place and label a code, how to pair QR images with ordinary links in digital files, and how to test the result with real users. It offers implementation guidance, not legal advice, and the closing section lists what a checklist cannot settle.

What makes a QR code experience accessible?

Accessibility means people with disabilities can find the option, understand its purpose, operate it, perceive the result and complete the task. A code that scans perfectly still fails if it is mounted out of reach, opens an unlabeled form, or leaves a person without a compatible phone with no route at all.

Six boxes in two rows labeled discover, understand, operate, access, complete and another route, with arrows between them — Original diagram: the six stages of a QR journey. A failure in stages 1 to 5 should lead to stage 6.

Journey stage	Accessibility question	Practical control
Discover	Can a person find the code and know it exists?	Consistent placement, a text heading, staff guidance, tactile or audio wayfinding where appropriate.
Understand	Does the label explain the result?	Write “Scan for the accessible menu,” not “Scan me.”
Operate	Can the person aim a device from a stable position?	Avoid excessive height, deep obstructions, glare, curved surfaces, movement and crowded layouts.
Access	Does the destination work with assistive technology?	Semantic HTML, keyboard access, reflow, captions, labels and suitable contrast.
Complete	Can the user finish without an inaccessible step?	Test sign-in, consent, payment, upload, confirmation and error recovery.
Use another route	What happens if scanning is not possible?	A readable link, accessible kiosk, telephone route, printed information or trained staff.

Pick the weakest stage first. For most printed codes it is stage 6, because nobody planned for the person who cannot or will not use a phone camera.

Which laws and standards apply to QR codes?

No law or standard reviewed for this guide contains a rule written specifically for QR codes. Several general rules reach them through what the code opens or what the sign communicates, and each has its own scope. Treat the table as orientation and confirm the rule that governs your setting.

Source	What it covers	How it touches a QR code
WCAG 2.2 (W3C)	Web content, at Levels A, AA and AAA	Applies to the destination page and to QR images shown on a web page. It does not set a print specification.
ADA effective communication (US DOJ)	State and local governments (Title II), businesses and nonprofits open to the public (Title III)	Covered entities must communicate effectively with people who have vision, hearing or speech disabilities. The right aid depends on the length, complexity and context of the communication.
Section 508 (US federal ICT)	Electronic content and technology used by US federal agencies	A GSA bulletin says QR codes can count as electronic content and that the standards do not apply to print media. It still recommends a printed URL.
European Accessibility Act (Directive 2019/882)	Listed products and services, including e-commerce	If scanning leads to a covered digital service, that service has to meet the accessibility requirements. Reported application date: 28 June 2025, with a narrow exemption for microenterprises that provide services.

The EAA dates and the microenterprise test (fewer than 10 employees and turnover or balance sheet total of up to €2 million) come from law-firm and compliance-vendor summaries found in search, not from a regulator page that could be fetched. Check Directive (EU) 2019/882 and your member state’s implementing law before relying on either figure.

Can a QR code be the only way to reach a service?

Do not assume a QR-only route is acceptable because most phones can scan. Whether an alternative is legally required depends on the covered service and the person’s need, but an equivalent route also protects against dead batteries, no mobile signal, older phones and people who prefer not to hand over a device.

The US Department of Justice explains that the aid a covered entity offers depends on the nature, length, complexity and context of the communication and on how the person usually communicates. Title II entities must give primary consideration to the aid the person requests, and Title III entities are encouraged to consult the person. Examples on the DOJ page include qualified readers, Braille or large print and screen reader software. That is a contextual duty, so no single fallback format fits every placement.

Decision chart showing three kinds of QR code purpose and the matching fallback: printed short URL, equal non-phone route, or printed core text — Original diagram: match the fallback to what the code does. This is a qualitative guide, not a legal test.

Short public information: print the essential lines beside the code, or give a short readable URL.
Restaurant menu: keep an accessible web menu and an effective non-phone option, such as a printed or large print copy on request.
Payment or ticketing: offer another operable channel so a smartphone is not the only gate.
Emergency or safety notice: print the core instruction. A code may add detail but should not hide the warning.
Private personal service: make the alternative preserve privacy, so nobody has to announce a disability to get help.

For allergen information specifically, see QR codes for food allergens, and for restaurant signage see restaurant menu QR codes.

What contrast ratio applies to QR codes?

WCAG 2.2 Success Criterion 1.4.11 (Non-text Contrast) asks for 3:1 against adjacent colors for graphical objects required to understand the content and for visual information needed to identify user-interface components. The W3C Understanding page does not mention barcodes or QR codes, and it exempts graphics where text conveys the same information, where the graphic is decorative, or where the information is available in another form. A QR image on a web page may or may not fall in scope depending on what the page does with it.

Some guidance goes higher. A GSA bulletin on Section 508 recommends the 4.5:1 text ratio from WCAG 2.1, and several vendor guides repeat it. Treat that as a conservative recommendation rather than a standard that names QR codes.

Scanning reliability is an engineering question of its own. Two colors that pass a WCAG calculation can still fail after printing, lamination, fading, glare or image compression. Use a dark foreground on a plain light background, keep the quiet zone clear, and validate the finished asset on real phones.

Check	What it establishes	What it leaves open
WCAG contrast calculation	Contrast between two specified digital colors	Print accuracy, glare, focus, decode success
Generator preview	The intended modules and design are present before export	How a printer, substrate, crop or laminate changes them
Camera scan test	A tested device decoded that sample in those conditions	Whether every user can find, aim at and use it
User accessibility test	People using relevant access methods attempted the whole journey	Legal compliance in every jurisdiction

Check candidate digital colors with the contrast checker, then follow the QR color and design guide and run a proof through the scannability tester. Avoid labeling any color pair “ADA approved” or “WCAG certified.”

How should an accessible QR code be positioned and labeled?

Place the symbol where seated and standing users can reach a comfortable camera distance, approach without obstruction and hold a phone steadily. WCAG, the ADA Standards and the EAA give no single QR centerline height.

ADA reach ranges apply to covered operable parts. A printed symbol is not automatically an operable part just because a phone can interact with it. Those dimensions can still prompt useful questions, but they should not be described as a QR mandate. Check the rule that governs the sign, kiosk or service.

Original diagram: anatomy of a sign that works without a camera. The QR square is a schematic, not a scannable code.

Keep the code out of corners, behind counters, above stairs and inside checkout queues where a wheelchair cannot approach.
Avoid glossy covers, reflective metal, backlighting, deep shadows, curved containers and doors that move.
Leave clear floor space so a person can pause without blocking traffic or being struck by it.
Size the code for its payload density and scanning distance, and confirm with the print size guide and a physical proof.
Repeat an essential code at two heights or locations when one placement cannot serve everyone.
Put a text heading that names the result above the code, and a readable URL below it.

BOIA suggests a colored frame around the code to help people aim the camera. The QR code frame guide covers frames that still decode.

A flat, silent square is hard to locate without a cue. Start with a large text label and staff who know where the code is, then add tactile or technology-assisted wayfinding only after testing it with the people you expect to use it.

A summary of a Mississippi State University resource sheet reports that on an iPhone with VoiceOver the Code Scanner control can be added to Control Center, and that on Android with TalkBack the Camera app reads out the link it detects. Menu names change between devices and OS versions, so treat those steps as a starting point and confirm them on current software. The same summary notes that the phone does not need to touch the sign.

A tactile marker can show where the scanning area is, but it needs a documented convention. An unexplained raised border does not tell someone what the code opens or whether another route exists. Braille labels should follow applicable signage standards and be produced by someone qualified.

Specialized markers and navigation systems exist for transit hubs, museums and campuses. Apps listed for blind users in app stores, and standalone technologies designed for accessibility, are not interchangeable with an ordinary QR code and may need a dedicated app. Weigh detection distance, adoption, privacy, upkeep and the non-app fallback before buying.

How should a QR code appear in a PDF, website or email?

Give the reader an ordinary accessible link that performs the same action. Someone already on a screen gains nothing from scanning that screen with another device, so keep the QR image as an optional handoff to a phone and make the link the main control.

Side by side comparison of a repetitive QR image and link pair against a paired version where the link is primary and the image has brief alt text — Original diagram: avoid announcing the same action twice. The exact alt text depends on context.

Link text: name the destination or action, such as “Download the conference schedule.”
Alt text: describe what the code does, not the pattern. Search summaries of the WCAG 1.1.1 guidance say a functional image should name its action, and that adjacent image and text links to the same page can be announced twice. W3C technique H2 addresses that case.
PDFs: check reading order, link annotations, document language, headings and alternative text in the exported file. An image-only PDF is invisible to a screen reader.
Email: include a normal linked button or text link, since many recipients read on the phone they would otherwise need for scanning.

The QR code for PDF article covers hosting a file so its link stays stable.

What must the linked page provide?

The destination must stay accessible through the whole task, including consent banners, sign-in, forms, media, payment, errors and confirmation. A well-written label cannot compensate for an inaccessible page. BOIA lists unoptimized sites, apps and PDF menus as common post-scan barriers.

Use WCAG 2.2 as the current W3C Recommendation unless a governing policy names another version. Test keyboard operation, visible focus, headings, form labels, error identification, zoom, reflow, color contrast, captions, transcripts and screen reader output. WCAG 2.2 also added SC 2.5.8, which asks for pointer targets of at least 24 by 24 CSS pixels at Level AA, subject to exceptions. That matters for the buttons a person meets right after scanning.

Keep the page light for mobile connections, state the file type and size before a large download, and do not force an app install without warning. Avoid short-lived sign-in tokens in public codes. Link to a page with a clear call to action instead of triggering a text message or download straight from the scan, as the GSA bulletin advises.

What should you check before putting a code in public?

Define the audience, environment, task, governing requirements and available alternatives.
Write a plain label that names the result and place a readable URL under the code.
Print a proof on the real material and test several phones, camera zoom settings, orientations and lighting.
Stand where a wheelchair user stands and where a short or tall adult stands, and check approach, glare and reach.
Complete the destination task with keyboard only, screen magnification and a screen reader on iOS and Android.
Try the fallback on its own and confirm it offers comparable information, timing, privacy and effort.
Name an owner, write down the destination URL, and retest after the page, print or environment changes.

A static code never expires, which makes it a reasonable choice for a permanent sign when the destination URL is stable. Use a dynamic code if you expect to repoint the destination after printing.

What are the most common mistakes?

Picture a small café that prints a laminated table card reading “Scan me” beside a glossy, curved menu stand. The code is 3 cm (about 1.2 in) wide, sits at the back of a high counter, and opens a PDF made from a photographed menu. A customer who uses a screen reader scans it and hears nothing useful, because the PDF has no text. The café has no printed menu and the server is busy at the till.

Four things went wrong, and each maps to a stage in the first diagram: the label did not say what the code does, the position made aiming hard, the destination was an image-only file, and no other route existed. Repairing them is cheap: a matte card with a heading and a short URL, a tagged HTML menu, and a large print copy kept at the till.

What does a checklist not settle?

Whether your organization is inside the scope of the ADA, EAA or a national law, and which standard version it must meet.
How much alt text a given screen reader user prefers for a QR image. Preferences differ and the sources reviewed do not agree on one wording.
What the right mounting height is for your site. No QR-specific rule was found, so test with the people who use the space.
Whether the 4.5:1 and 3:1 figures meet a contract or procurement requirement. Ask the buyer which they mean.

This article is general information, not legal advice. Accessibility duties differ by country, sector and organization, so check your local rules and seek qualified review for a regulated deployment.