Short answer: Offer NFC or QR as a convenient route, not the only route. Label the destination, provide a readable URL or equivalent link, place the sign where people can reach it, and make the page and its controls usable with assistive technology.
Make the physical touchpoint understandable
A code should say what it opens: “View the menu” or “Open our contact page” is more useful than “Scan here.” Add the short URL or another direct link beside it for someone who cannot scan, does not know how, has no compatible device, or prefers not to use the camera. Section508.gov recommends descriptive QR labels and an accessible alternative.
Place signs where people can see and reach them, avoid glare, and test the actual print and lighting. U.S. Department of Energy guidance recommends an adjacent destination URL, usable placement and testing; its page does not set a universal physical QR size or mounting height. NFC is also not automatically accessible: some visitors may not know where to tap or may be unable to perform the gesture. Provide a visible QR or text option.
Make the destination accessible too
The web page after the scan still needs to work. Test headings, form labels, keyboard navigation, screen readers, text resizing and language choice. WCAG 2.2 includes a minimum pointer target criterion of 24 by 24 CSS pixels, subject to exceptions such as spacing. Its text-contrast criterion requires at least 4.5:1 for ordinary text and 3:1 for large text, with defined exceptions. These thresholds apply to digital content, not the physical QR pattern itself.
A simple test is to complete the journey without using the camera or touch gesture: follow the printed URL, navigate by keyboard and submit a form using a screen reader. Ensure errors explain how to recover. Tapytap describes public profiles shared by NFC or QR, but that alone does not certify any profile or form as WCAG-conformant.
A five-point launch check
1. State the action and destination in the sign’s label.
2. Provide a no-scan equivalent, such as a short printed URL.
3. Check physical reach, readability, contrast and glare at the final location.
4. Test the destination on mobile with keyboard and assistive technology.
5. Recheck the code after any link or profile change.
FAQs
Related guide: NFC and QR for Hotels: A Guest-Touchpoint Playbook.
Next step: Explore Tapytap NFC and profile options.