# Provide an accessible fallback for QR services > Offer a readable URL and another way to complete the task beside every public-service QR code. Describe the destination in plain language, preserve scan contrast and test the linked page separately. A working QR image is only one access route; it does not establish that the service is accessible to everyone. Source: https://useqr.app/docs/how-to/qr-code-accessible-service-fallback · Last reviewed 2026-10-02 · UseQR is free forever, no signup. --- ## Describe the action before the mechanism Use a label such as View the menu or Find your platform, rather than Scan me alone. Visitors need to know the benefit and whether a login or payment is involved. Pair the code with a readable destination domain so people can make an informed choice before opening it. A short URL is useful only if someone can type it. Avoid dense tracking strings as the printed fallback. Where you own the site, provide a memorable path such as https://example.com/menu that opens the same content. ## Provide another route to the task A visitor may have no smartphone, no data connection, a damaged camera or difficulty aiming it. Provide the information in print, through staff assistance or by another suitable channel. For essential services, make the alternative visible where the decision occurs. A restaurant should keep a readable menu available. An appointment desk should provide a contact route. A transit sign should show the core direction without requiring a scan. The fallback must complete the task, not merely explain that a QR code exists. ## Test image and destination separately Keep a dark code on a light background, a clear quiet zone and readable label text. Use the [size calculator](/size-calculator) to plan dimensions, then test in the actual location. Viewing angle, glare and whether the sign is reachable can matter as much as its nominal size. Open the destination with keyboard navigation and the assistive technologies relevant to your audience. Check headings, meaningful links, form labels and error messages. Avoid an image-only menu where visitors need selectable text. These checks are practical acceptance steps, not a compliance certification. ## Keep the fallback current When a page or service changes, update the text route and printed information too. Record them alongside the code in the [ownership register](/docs/how-to/qr-code-register-and-ownership). Ask a person unfamiliar with the campaign to complete the task through each route. UseQR creates the code and provides verification tools. Your organisation owns the destination experience and the alternatives it offers. ## FAQ ### Is a readable short URL enough? It helps people who can type a URL, but others may still need printed information or staff assistance. ### Does a passing decode prove accessibility? No. It checks the code's payload. The physical placement, label, destination and fallback need separate acceptance. ## Try it - https://useqr.app/url - https://useqr.app/size-calculator - https://useqr.app/validate