Standalone artifact

Restaurant QR Menu Mobile Audit. 10 pass / fail rows you can run today.

Same artifact as on the home page, given its own URL so you can bookmark it, share it with a chef or a designer, or print it out in the kitchen.

Useful artifact · no signup

Restaurant QR Menu Mobile Audit.

Ten pass/fail rows to run against your own QR menu.

Example score

Workflow test against a typical PDF QR menu. Yours may score higher.

Score

0 / 10

  1. 01

    Does the menu open without forcing a PDF download?

    Fail

    Pass criterion

    Opens as an HTML page in the browser

    Common failure

    Forces a 4 to 8 MB PDF download before anything is readable

    Workflow test on 5 independent restaurant QR codes scanned 2026-05 — 4 of 5 routed to a PDF.

  2. 02

    Is body text 16px or larger after the phone's default zoom?

    Fail

    Pass criterion

    All items and prices render at 16px+ without pinching

    Common failure

    Rendered text is 8 to 10px because the PDF is sized for 8.5x11 paper

    WCAG 2.2 SC 1.4.4 recommends 200% resize without loss; PDF menus break this.

  3. 03

    LCP under 2.5s on a throttled 4G connection?

    Fail

    Pass criterion

    First contentful menu paint under 2.5s on slow-4G profile

    Common failure

    LCP is the PDF itself — 6 to 9s on slow-4G

    Lighthouse 'Slow 4G' simulation against the source PDF, not an HTML page.

  4. 04

    Can a guest read prices without pinch-zooming?

    Fail

    Pass criterion

    Prices live in a left-or-right column at body size

    Common failure

    Prices are in a 7pt right column requiring 3x pinch zoom

  5. 05

    Allergen tags machine-readable (icons + alt text)?

    Fail

    Pass criterion

    Icons have alt text like 'Contains peanuts'

    Common failure

    Allergens are image-only with no alt; screen readers see nothing

  6. 06

    Can a single menu item be linked individually?

    Fail

    Pass criterion

    Items have anchor links like /menu#flatbread

    Common failure

    It is a flat PDF — no URL fragments, no deep links

  7. 07

    Can an owner update a single price in under 5 minutes?

    Fail

    Pass criterion

    Inline edit, autosaves, QR stays the same

    Common failure

    Owner re-exports the PDF in Word, re-uploads, sometimes prints a new QR

  8. 08

    Does the menu degrade gracefully on spotty Wi-Fi?

    Fail

    Pass criterion

    HTML page caches; text shows before images

    Common failure

    PDF either fully loads or shows a blank PDF.js panel

  9. 09

    Is the restaurant phone number tap-to-call visible?

    Fail

    Pass criterion

    tel: link in header or footer, 44x44 px tap target

    Common failure

    Phone number is baked into the PDF image, not tappable

  10. 10

    Is there a print stylesheet for the kitchen?

    Fail

    Pass criterion

    /menu?print=1 prints clean A4 with prices on the right

    Common failure

    Owner maintains a separate Word doc for kitchen printouts

Open your QR menu on a phone (or Chrome DevTools iPhone SE preset) and check each row.

Methodology: how this audit was built.

Found a row your menu fails? Email hello@tealstag.com with a screenshot — we read every one.

Read how the audit was built in our launch post.

Found a row your menu fails? Email hello@tealstag.com with the screenshot — we read every one.