Back to BlogWebsite Accessibility

QR Code Accessibility: The Customer Is Ready to Pay. Is Scanning Their Only Option?

A November 20 W3C discussion highlights a common design problem: customers are asked to scan an on-screen QR code with a second device, but no equivalent route is offered. Learn how businesses can make menus, payments, check-in, and account handoffs easier to use.

9 sections · 9 min read · 1,870 words

Written by Edward Sm

Digital Accessibility Specialist, ADA Access Group LLC

9 min read

A customer holds a smartphone toward a large digital screen displaying a QR code.

A customer is ready to pay on a desktop screen. The business displays a QR code and says, “Scan this with your phone to continue.” For someone who cannot comfortably hold and aim a second device, is using a desktop in a phone-free environment, or does not have another camera available, that small square may become the only door—and the door may be closed.

QR codes are useful. They connect printed signs, menus, payment terminals, event displays, and desktop websites to digital services. The accessibility problem is not the QR code itself. It is a workflow that makes camera scanning the only way to continue, without a usable alternative on the screen.

This issue surfaced in a public discussion in the W3C WCAG repository on November 20, 2026. A contributor asked for clearer guidance on screen-based QR flows and proposed a “never QR-only” pattern: a direct link, copyable URL, or option to send the link by email or SMS. A reply said the request would not be handled in WCAG 2.x and suggested the WCAG 3 issue repository. The issue was closed that day. This was a community issue and a reply in the thread—not an adopted WCAG requirement, a formal Working Group decision, or a new ADA rule. Read the November 20 W3C discussion about accessible QR-code alternatives.

Why a QR code can become a barrier

A QR code is a visual pattern designed to be read by a camera. That can be convenient for many customers, but requiring a second device and a precise physical action can introduce extra steps that are not part of the underlying service.

  • Limited dexterity or tremors: Holding a phone steady, aiming its camera at a monitor, and waiting for focus may be difficult or tiring.
  • Alternative input methods: A person using voice control, switch access, eye tracking, or a mounted device may not be able to pick up and position a second phone.
  • One-device situations: Someone using a public computer, a work desktop where phones are restricted, or a single mobile device cannot scan a code displayed on that same device.
  • Low vision or camera challenges: A small, low-contrast, reflective, or poorly positioned code can be difficult to locate and scan.
  • Unclear destinations: A customer may not know where the code leads or whether it will open a menu, payment page, app store, account sign-in, or unrelated service.

These are different user needs, so one fallback will not solve every problem. The design goal is to let people complete the same task through another accessible route, without having to explain their disability or ask staff to improvise.

Where QR-only workflows appear in business

The issue is not limited to restaurants. QR codes appear wherever a business moves a customer from a physical sign or a large screen to a digital service.

Customer holds a smartphone above a payment terminal displaying a QR code at a counter.
Photo: iMin Technology / Pexels.
  • Restaurants: A table sign points to the menu, ordering page, or bill payment. A customer should also be able to open the menu another way.
  • Payments and parking: A kiosk or desktop page asks the customer to scan a code to pay, add a vehicle, or continue a transaction.
  • Events and venues: A large screen displays a code for registration, ticket transfer, joining a queue, or receiving event information.
  • Retail and product support: A product label or checkout screen sends customers to instructions, warranty registration, product details, or a loyalty program.
  • Account access: A desktop sign-in or device-pairing flow expects a customer to scan a QR code with a phone to approve access.

Each example has a different risk. A restaurant can offer a printed menu or a direct menu link. A payment flow needs a secure alternative that preserves the transaction. An authentication flow needs an alternative that is both accessible and appropriately secure.

What WCAG says—and what it does not say

The current W3C Recommendation is Web Content Accessibility Guidelines (WCAG) 2.2, published on December 12, 2024. It does not prescribe one universal QR-code interface pattern.

Depending on how a QR code is implemented, existing criteria may still matter. Success Criterion 1.1.1, Non-text Content, requires a text alternative that serves the equivalent purpose of non-text content. Success Criterion 2.1.1, Keyboard, requires functionality to be operable through a keyboard interface. If a QR code forms part of an authentication process, the relevant authentication criteria should also be reviewed; see Success Criterion 3.3.8, Accessible Authentication (Minimum).

These criteria should be applied to the actual page and interaction. They do not mean that every QR code automatically fails WCAG, or that WCAG 2.2 already contains a specific rule requiring an email or SMS alternative for every code. A meaningful text label is useful, but merely announcing “QR code” does not necessarily give a customer a practical way to complete the task.

For U.S. businesses open to the public, the Department of Justice explains that Title III requires full and equal enjoyment of goods and services and that inaccessible web features can limit access to those services. The DOJ’s Guidance on Web Accessibility and the ADA also explains that it has not issued a detailed technical regulation for all private business websites; WCAG is one helpful technical resource, not a universal legal certificate. The legal analysis depends on the business and the facts. For a broader overview, see our guide to ADA Title III and website accessibility.

Give customers another way to continue

A robust QR workflow offers an alternative beside the code, not hidden in a help page that the customer cannot reach until after scanning. Choose the fallback that matches the task.

  1. Offer a direct, keyboard-operable link. Place a clearly named link such as “Open the menu” or “Continue to payment” beside the QR code. It should open the same destination and work with Tab, Shift+Tab, and Enter.
  2. Make the URL available to read and copy. A short, human-readable URL or copy-link button can help customers who cannot use a camera. Give the button an accessible name and announce when the link has been copied.
  3. Provide an optional cross-device handoff. For a desktop-to-mobile journey, consider “Send this link to my phone” or “Email me the link.” Explain why contact information is needed, collect only what is necessary, and give the customer control over whether to use this option.
  4. Use a short code when it fits the service. A customer may be able to type a code into the destination website or app. Make the code easy to select and copy where possible, provide clear instructions, and avoid unnecessary time pressure.
  5. Keep a non-digital route for essential services. A printed menu, staffed payment option, accessible kiosk, or other service channel may be appropriate. Do not make customers disclose a diagnosis just to request an alternative.

Do not treat NFC, a second QR code, or “ask an employee” as a universal fix. NFC still requires compatible hardware and the customer may not be in a staffed location. Staff help can be valuable, but it should not be the only route when a customer could complete the task independently.

Restaurants can keep the convenience without making it mandatory

Customer browses food choices on a smartphone while seated at a table.
Photo: Polina Zimmerman / Pexels.

A QR menu can be one convenient option, but customers should not have to scan a code just to find out what is available. Restaurants can show a direct menu link on their website and provide a printed menu or staff-supported option at the table. The digital menu itself should use real text, meaningful headings, readable prices, descriptive links, and controls that work with screen readers and keyboards. Avoid making an image-only menu or a PDF the only way to browse dishes.

For the ordering steps after the menu opens, see our guide to restaurant online ordering accessibility, from menu to confirmation. That article covers item customization, cart feedback, pickup and delivery, checkout errors, and order confirmation. The QR-code question is the step before all of that: can the customer reach the ordering journey in the first place?

Test the whole journey—not just the QR image

A QR code can be visually clear and still lead to an inaccessible destination. Test both the handoff and the service that follows it.

  • Can a keyboard user find and activate the direct alternative without scanning?
  • Does a screen reader announce a useful purpose, such as “Open payment page,” instead of only “image” or “QR code”?
  • Can customers use the same page on one device without needing a second camera?
  • Does the direct link open the same service and preserve the intended task?
  • If a link is sent by email or SMS, are labels, instructions, errors, privacy information, and confirmation messages accessible?
  • Does the destination work at high zoom and with the mobile screen readers used by the intended audience?
  • Can a customer recover if the QR code is damaged, the camera does not recognize it, the network is unavailable, or the app is not installed?
  • Does the alternative remain available after a redesign or vendor update?

Test with representative combinations of keyboard, screen reader, browser, and mobile device. Our screen reader testing guide explains how to evaluate NVDA, JAWS, and VoiceOver. For a broader review of scope, evidence, and retesting, read what a website accessibility audit should include.

If QR codes are used to sign in or pair a device, test the whole authentication flow, not just the code. A customer should have another suitable method to access the account if scanning is not possible. Our guide to accessible authentication and login covers password managers, paste, verification codes, and recovery paths.

The business case for a second way in

Every extra device, camera action, app installation, or unclear handoff adds friction to a customer journey. A usable alternative can help people continue independently, reduce avoidable interruptions for staff, and make a service more resilient when a camera or phone is unavailable. It may also help protect completed transactions—but businesses should measure this rather than assume a particular conversion uplift.

Track how often customers use each route, where they abandon the flow, how frequently staff need to intervene, and whether support requests fall after the alternative is introduced. Do not collect sensitive disability information just to measure whether a fallback is being used.

How ADA Access Group can help

If your website, payment process, reservation system, or event check-in relies on QR codes, assess the entire path from the code to the completed task. ADA Access Group can review the page, its keyboard and screen-reader alternatives, the mobile destination, and the third-party components involved. Learn more about our website accessibility audit service.

Does your customer have another way in? Contact ADA Access Group to discuss an accessibility assessment of QR-based customer journeys and the services behind them.

Sources

This article provides general technical and business information, not legal advice. A QR code is not inherently unlawful or inaccessible; legal obligations depend on the business, service, implementation, and applicable law.

Featured photo: Walls.io / Pexels.

Article Tags

QR code accessibilityWCAG 2.2keyboard accessibilityscreen reader testingaccessible paymentsdigital menusADA website accessibility

Need a website accessibility audit?

This article explains the topic. The audit is a manual WCAG 2.2 AA review by default (WCAG 2.1 AA when a contract or regulation requires it) with a prioritized report — not another automated scan.