Photo: Solomon203, CC BY-SA 4.0, via Wikimedia Commons
The table tent says VIEW OUR MENU and features a small square of static. You scan it, because you are hungry and the server has already walked past twice.
What loads is not a menu. It is a redirect to a third-party ordering site, which asks you to allow location, then offers eighteen percent off if you join the rewards program, then requests your email so it can send you the receipt, then suggests the app because the app is faster. Nine minutes later you are looking at a PDF of a menu that was last updated in 2023, pinching to zoom on a photo of a laminated page, and the font is somehow blurry in a way that feels personal.
This is the modern American lunch: a privacy negotiation with a side of fries.
The pandemic was the excuse, not the reason
In 2020, contactless menus were a genuine public health measure. Laminated menus were, briefly, treated like biohazards. Restaurants printed codes, taped them to tables, and every diner learned the gesture. Fine. Nobody is mad about the emergency.
The emergency ended. The codes stayed. And somewhere between then and now, someone in a marketing department noticed something wonderful: the little square is a doorway, and whoever owns the doorway gets to ask questions.
What that square is actually doing
A printed menu cannot tell the restaurant anything. A QR code can tell it almost everything.
Most codes are not static links. They are tagged, often regenerated per surface, which means the restaurant knows which table scanned, at what time, on what kind of phone, on which visit, and whether you looked at the dessert section and then ordered the chicken. If the code routes through a third-party platform, that platform collects a parallel copy. Cookies get set. Tracking pixels fire. Some of these flows hand your email to the restaurant's marketing vendor, and some hand it to a company you have never heard of that resells audience data to people who make excuses about it in privacy policies.
None of this is secret. All of it is buried in a consent screen with a large green ACCEPT and a grey reject link at four-point type.
The accessibility problem is the whole problem
Here is the part that gets filed under inconvenience and should be filed under failure: a QR-only menu excludes people.
A PDF is not a menu, from an accessibility standpoint. It does not reflow. It does not respond to text size settings. It usually has no reading order, no alt text for the images, and no labels, so a screen reader announces something between a shrug and a stream of numbers. Color contrast fails routinely. Tap targets are the size of a sesame seed.
Then there is the harder exclusion. Not everyone carries a charged smartphone with a data plan. Older diners, people whose phones died at the museum, anyone who left the phone in the car because today was supposed to be about talking to their kid. A restaurant that will not hand over a printed page has quietly decided those customers are not worth the paper.
Federal disability law is generally understood to reach a business's website and digital services, and restaurants have been sued over inaccessible ordering pages. The settlement usually involves a fix and a training session. The menu stays behind a code.
And then there is the Wi-Fi hostage situation
Some codes lead to a menu. Some lead to a captive portal that wants the Wi-Fi password, which it will text you, if you provide a number. Some lead to a page that demands notifications before it will render a list of appetizers. Several lead to a login wall because the restaurant decided its menu should live inside a social platform that wants an account before it will show you food.
No one has ever wanted a chicken sandwich badly enough to hand over their contact list. People do it anyway, because the alternative is asking a stranger for a favor in a restaurant.
The paper menu never actually left
There is a backlash, and it is not being run by technophobes. It is being run by people with parents, people with screen readers, people who would like to read a wine list without creating a password. A handful of state legislators have floated bills requiring restaurants to provide a physical menu on request. They are unlikely to become a national standard, but the fact that they exist tells you how badly the transition went.
Meanwhile, plenty of restaurants quietly printed new menus. It turns out a piece of cardstock has excellent uptime, needs no onboarding, and works in a basement with no signal. The convenience fee is zero.
How to order lunch without joining a mailing list
- Ask for a paper menu. Ask every time. It is a reasonable request and the worst answer is no.
- If the code leads to an email gate, look for the small grey skip link. It is there, designed to be missed.
- Decline to let a restaurant menu have your location. It has no use for it except the obvious use.
- Prefer to order with a human when one is available. That is the entire channel, and it does not track you.
- If you build these pages for a living: a menu is a document, not a landing page. Ship HTML that reflows, put the prices in text, and give the kitchen a printed backup.
The QR code did not eat the menu. The menu was eaten by an analytics team that saw a table tent and recognized a conversion opportunity. The square is just what they left on the table.