Digital Menu Accessibility: Readable for Every Guest
Roughly one in four American adults lives with some form of disability, and the share of diners over 55, the demographic most likely to struggle with small phone type, keeps growing. When your menu moved onto a 6-inch screen, it got harder to read for a lot of the people who tip well and come back weekly. Most restaurants never notice, because guests who cannot read a menu rarely complain. They just order less, or go somewhere easier.
The good news: menu accessibility is mostly a handful of concrete, checkable specs, not a redesign. This article gives you the numbers and a 10-minute audit. It assumes your QR code already opens a real menu page; if you are earlier in the process, start with the complete QR code menu guide and the case for pages over files in QR menu vs. PDF menu, because a scanned PDF fails accessibility before any of the tips below can help.
Who you are designing for
Not an edge case. On a normal Friday night, a 60-seat room plausibly includes:
- Guests over 55 with presbyopia, who read comfortably at 16px and up but squint at 12px
- One or two guests with low vision who rely on their phone’s text-size setting or screen reader
- Guests with color vision deficiency (about 8% of men) who cannot distinguish your red “spicy” text from the black around it
- Someone reading in bright patio glare, and someone reading in candlelight, both of whom are temporarily low-vision
- Someone holding a toddler, one-handed, distracted, which is its own kind of impairment
Design for these guests and the menu gets easier for everyone. That is the reliable pattern with accessibility work.
The specs that matter
| Element | Minimum | Better | Why |
|---|---|---|---|
| Item name size | 16px | 17–18px | Below 16px, older eyes squint; iOS also auto-zooms form fields under 16px |
| Description text | 14px | 15–16px | Small but legible; never gray-on-white below 14px |
| Price size | Same as item name | Same, bold | Prices are the most re-checked element on the page |
| Body contrast | 4.5:1 ratio | 7:1 | WCAG AA minimum for normal text; gray #9A9A9A on white fails, #3D3D3A passes |
| Large headings contrast | 3:1 | 4.5:1 | Applies to text 24px+ |
| Tap targets (section tabs, buttons) | 44x44px | 48x48px | Fingertip size; Apple’s long-standing guideline |
| Line length | Under 75 characters | 45–65 | Long lines are hard to track on small screens |
Contrast ratio sounds technical but takes seconds to check: paste your text and background colors into any free contrast checker (search “WCAG contrast checker”) and look for 4.5:1 or better. The classy light-gray-on-white that designers love commonly measures around 2.5:1, which fails for everyone in dim light and excludes low-vision guests entirely.
Real text, not pictures of text
This is the single highest-leverage rule. If your “digital menu” is a photo or scan of the paper menu, every accessibility feature on the guest’s phone is dead on arrival:
- Text scaling does nothing. A guest with iOS text size cranked up gets the same tiny image.
- Screen readers read silence. VoiceOver and TalkBack cannot see inside an image. A blind guest gets literally nothing.
- Search gets nothing either. The same opacity that blocks screen readers blocks Google from reading your items and prices.
Real, structured text fixes all three at once. This is a big part of why transcribing the menu matters more than it first appears: when VisibleMenus turns a menu photo into structured sections, items, and prices, the output is genuine HTML text that scales, reads aloud, and gets indexed. If images do appear on the page (a dish photo, your logo), they need alt text: a short written description (“Margherita pizza with fresh basil”) that screen readers speak in place of the image. Decoration can have empty alt text; information cannot.
Color is a highlight, never the message
If spicy items are marked only by red text, 1 in 12 of your male guests cannot see the warning. If gluten-free items are marked only by a green leaf, low-vision guests miss it. The rule: color may emphasize information, but a symbol or word must carry it. “GF” in a bordered tag beats a green dot; a small chili icon plus the word “spicy” beats red type.
This matters most where the stakes are real: allergens. A guest scanning for shellfish warnings is doing safety work on a small screen, and your labeling system needs to survive every vision condition at the table. The dietary tags and allergen labeling guide covers how to build that system properly across both print and digital menus.
The 10-minute audit
Run this on your own menu tonight, on your own phone:
- The arm test. Hold the phone at normal distance in your dining room’s evening lighting. Can you read a description without bringing the phone closer? (2 min)
- The text-size test. Set your phone’s text size to maximum (iOS: Settings, Accessibility, Display & Text Size; Android: Settings, Display, Font size). Reload the menu. Did the text grow, and does the layout still work? (2 min)
- The grayscale test. Turn on grayscale (in the same accessibility settings) and check whether your spicy/vegan/GF markers still communicate. (2 min)
- The screen reader spot-check. Turn on VoiceOver or TalkBack and swipe through five items. You should hear names and prices, not “image” or silence. (3 min)
- The glare test. Step outside or under your brightest light and read the palest text on the page. (1 min)
Fail any of these and you now know exactly what to fix, and every fix is a text size, a color value, or a tag format, not a rebuild.
Keep the paper escape hatch
Accessibility also means options. Some guests cannot use a phone menu at any font size: dead battery, no smartphone, tremor, or simple preference. Keep a few large-print paper menus (18pt type minimum, high contrast, matte paper) at the host stand and train staff to offer them without ceremony. A guest who has to ask twice for a readable menu is a guest deciding not to come back. Where the codes themselves go, and why paper stays part of the system, is covered in the QR menu placement best practices; and if your codes are hard to scan in the first place, size is usually the culprit, which the QR code size and printing guide solves with one calculator.
An accessible menu is not a compliance chore. It is the difference between a table of six ordering confidently and a table of six sharing one squinting reader. The specs above fit on an index card. Tape them next to wherever menu edits happen.
