Since June 2025, the European Accessibility Act (EAA) has been in force across EU member states, and it applies to far more than websites and mobile apps in the abstract sense. If your business uses QR codes to point customers to a digital menu, a product information page, a booking form, or a payment portal, the page that opens after the scan falls squarely within scope. Many organizations spent months preparing their main website for accessibility while forgetting that the QR code on a table tent or product label leads to a destination that must meet the same standard.
This gap matters because QR codes are often used precisely in contexts where accessibility is most critical: a restaurant menu that a visually impaired customer needs read aloud by a screen reader, a transit schedule that must be usable by someone with motor impairments, or a public service form that older adults rely on. If the landing page fails basic accessibility checks, the business is not just risking a poor user experience. It is risking non-compliance with a binding EU law that carries real enforcement consequences.
What the EAA actually requires for QR-linked pages
The EAA does not mention QR codes by name. Instead, it sets accessibility requirements for products and services, and a QR code is simply a delivery mechanism, a shortcut, to a digital service. The obligation falls on the landing page, menu, or form itself, not the code that generates the link. In practice, this means:
Any web page reached via a QR code and used to deliver a service (ordering, booking, paying, requesting information) must meet the accessibility requirements referenced by the EAA, which align closely with WCAG 2.1 Level AA.
Static content, like a PDF menu with no interactive elements, is not automatically exempt. If it is the primary way customers access information, it still needs to be perceivable and operable by assistive technology.
Micro-enterprises providing services (fewer than 10 employees and under 2 million euros annual turnover) have a limited exemption in some member states, but this exemption is narrower than many assume and does not cover all sectors equally. It is worth checking national transposition rules rather than assuming a blanket pass.
The obligation applies regardless of whether the QR code itself is static or dynamic, or whether it was generated by a free tool or a paid platform. Compliance responsibility sits with the business publishing the destination content.
Why QR-linked destinations are an easy compliance blind spot
Three patterns keep showing up in audits and complaints since the June 2025 deadline passed.
First, many QR-linked pages are built quickly, sometimes by a marketing agency or a print shop, and never go through the same review process as the main corporate website. A page thrown together for a seasonal menu or event registration is treated as disposable, even though it may serve thousands of scans.
Second, PDFs are still the most common failure point. A scanned or image-based PDF menu, with no text layer, is invisible to screen readers. Even a text-based PDF often lacks proper heading structure, reading order, or alt text for images, which makes navigation by assistive technology painful or impossible.
Third, many businesses do not control or even know where their QR code actually points once it has been printed on thousands of table tents, packaging labels, or posters. If the destination URL changes without an accessibility review, an initially compliant page can silently become non-compliant.
A practical accessibility checklist for QR destinations
Use this list before publishing any page, menu, or form that will be reached primarily through a QR code.
Structure with real HTML, not just images or PDFs. Use semantic headings, lists, and tables so screen readers can navigate the content logically.
Provide sufficient color contrast. Text and background combinations should meet at least a 4.5:1 contrast ratio for normal text, per WCAG AA.
Make text resizable without breaking layout. Users should be able to zoom to 200 percent without losing content or functionality.
Add alt text to every meaningful image. This includes product photos, icons, and any infographic-style menu design.
Ensure full keyboard and switch-device operability. Every interactive element, buttons, forms, filters, must be reachable and usable without a mouse or touchscreen.
Avoid PDF-only menus. If a PDF is unavoidable, publish an accessible HTML version alongside it, and tag the PDF properly if it must remain the primary format.
Label form fields clearly. Booking, ordering, or feedback forms need explicit labels, not placeholder text alone, and clear error messages.
Test with a screen reader. A five-minute pass with VoiceOver or NVDA will surface most structural problems before real customers do.
Check load performance on mobile networks. Accessibility includes usability under real-world conditions, and a page that times out on a weak signal fails users regardless of markup quality.
Review the destination URL periodically. If the linked page is redesigned or replaced, re-run the checklist rather than assuming the original review still applies.
Where dynamic QR codes help with ongoing compliance
One underappreciated advantage of dynamic QR codes is that they decouple the printed code from the destination content. This matters for accessibility maintenance in two concrete ways.
First, if an accessibility issue is found in a landing page after codes have already been printed and distributed, a dynamic QR code lets you fix the destination, or swap it entirely for a compliant version, without reprinting a single label, poster, or menu. A static QR code, by contrast, locks you into whatever URL was encoded at creation time.
Second, dynamic codes make it easier to run a single accessible landing page across multiple physical touchpoints, rather than maintaining dozens of near-duplicate pages of varying quality. Fewer unique destinations means fewer places where accessibility can quietly regress.
On EUQR, dynamic codes are generated and hosted on EU infrastructure, with scan analytics limited to operational data rather than personal profiling. That EU-hosted, privacy-first setup matters here too: accessibility and data protection obligations both point toward the same discipline, knowing exactly where your data lives and who can access it, and keeping destination content under your direct control rather than a third-party black box.
Building an internal review habit
Compliance is not a one-time audit. It is a habit that needs to survive staff turnover and content updates. A few practical steps help:
Assign one person or team as the owner of every QR-linked destination, with a standing task to review it whenever content changes.
Keep a simple log of every active QR code, its destination URL, and its last accessibility check date.
Add an accessibility check to the same workflow used for legal or brand review before any new landing page goes live.
Retest after any redesign, even a small one, since layout changes often introduce new contrast or structure issues.
Conclusion
The EAA has quietly expanded what "accessible" means for any business that uses QR codes to connect physical spaces to digital services. The rule is simple even if compliance takes discipline: the page a customer lands on after scanning must be usable by everyone, including people relying on screen readers, keyboard navigation, or magnification. Treating that landing page with the same seriousness as your main website, and choosing QR tooling that lets you fix problems without reprinting materials, is the most practical path to staying compliant as content and regulations continue to evolve.