The menu that is a photograph and the price list that is a PDF
What happens when a menu is published as a flat picture
"What are the specials tonight?" a customer asks over the phone, because the website's menu is a photo of the printed one. The words in that photo don't exist as text to anyone, or anything, reading the page.
A screen reader has nothing to announce. A phone's built-in search can't find "gluten-free" on it. Even a sighted customer squinting at a blurry photo on a small screen is fighting the same underlying problem, just in a different way.
This is one of the more common accessibility failures on small business sites, and it's rarely intentional. A designer had a beautiful print menu, and the fastest way to get it online was a photo or a scan. Fast, and quietly unusable for a meaningful share of visitors.
A hungry customer with a food allergy is often the person hit hardest by this particular gap. They need to search a page for a specific ingredient, fast, and a picture gives them nothing to search. A phone call is their only fallback, and not everyone thinks to make one before ordering.
PDFs that were never structured to be read aloud
A PDF isn't automatically better than a photo. Many PDF menus are built the same way a print flyer is built. Text boxes placed wherever they look right, with no underlying structure telling a screen reader what's a heading, what's a price, and what's a description.
Read aloud, it comes out as a jumble of fragments. Prices and descriptions scrambled together, in whatever order the file happens to store them. A listener has no way to sort it back into sense.
A PDF can be built accessibly, with real tagged structure, but that takes deliberate work in the software that made it. Plenty of menu PDFs floating around online were never built that way, simply because nobody asked for it at the time.
There's a quick way to check which kind you have. Try selecting a line of text on the PDF with your cursor. If nothing highlights, or the whole page selects as one image, it's not text at all, just a picture wearing a PDF file extension.
A print-shaped document on a phone-shaped screen
Print is designed for a fixed page size that never changes. A phone screen is the opposite. Narrow. Tall. Used one-handed at arm's length, often in bad restaurant lighting.
A print-shaped PDF crammed onto that screen tends to mean pinch-zooming sideways, reading one column at a time. That's friction a hungry customer standing outside a restaurant does not have patience for.
A real web page reflows automatically. Text wraps to fit the screen it's on, front and center, without the visitor doing any of the work. That single difference is a large part of what separates a document a phone can handle from one it can't.
Rebuilding a flyer as a real page without losing its look
Rebuilding a menu as an actual page doesn't mean losing the design work that went into the print version. The categories, the ordering, the little descriptive notes under each item, all of that carries over.
It becomes headings, sections, and paragraphs on a normal web page, styled to match the rest of the site. Nothing about the look has to change.
What changes is the underlying structure. A heading for "Starters." A list for the items under it. Real text for prices instead of text baked into an image. How to check whether a rebuilt page is actually readable this way is worth running once the new version is live, not just assumed.
The cases where a downloadable document is genuinely right
A downloadable document still makes sense in specific cases. A seasonal wine list a regular wants to print out. A full spec sheet a contractor needs to hand to a client. A form somebody has to sign by hand and mail back.
The test is whether the primary use is reading it on a screen or printing it out. If it's mainly getting printed, a PDF is a reasonable choice, and nobody needs to apologize for using one there.
What it shouldn't be is the only way to reach information a visitor needs right away, like today's hours or tonight's specials. That's core page content. It doesn't belong hidden behind a download link.
A good rule of thumb: if a customer would be annoyed to discover the information only lives in a download, it belongs on the page itself. If they'd expect to print it and carry it around, a document is the right call.
Keeping a printable version alongside the page version
None of this means the PDF has to disappear entirely. Plenty of businesses keep a printable version available as a secondary option. A "download as PDF" link sitting next to the real page, for the regular who wants a physical copy on the counter.
The page stays the primary version anyone visiting the site actually reads. The PDF becomes an extra, not the only route in.
Images throughout the site still need their own descriptions handled properly, and describing individual images with real alt text is worth doing well beyond just the menu.
A menu locked inside a picture is also invisible to search, the same way it's invisible to a screen reader, part of why small businesses struggle to get found for the things they actually sell. The words simply aren't there to be found, no matter how good the search engine is.
None of this takes a rebuild of the whole site. Usually it's one page, done properly once, and it stays fixed. All of it connects to how accessibility fits together for a small business site.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go