A restaurant menu page people and search can read

Why the menu belongs in text

A PDF has to be downloaded, pinched and zoomed on a phone, and a person standing in a parking lot will give up. Text on the page loads with the rest of the site and reads at any size.

It also lets search and AI tools read what you serve. A menu locked in a photo says nothing to them, and a file is harder for them to use. Our guide on accessible PDFs covers why files struggle.

A text menu is also easy to share. A friend who texts the address of your menu page is sending something that opens at once, not a file that must be saved first.

Sections that match how people choose

Group dishes the way guests think: starters, mains, sides, desserts, drinks, and perhaps a short section for the kids. Put the section names in headings so a person can jump straight to the part they want.

Give each dish a name and one honest sentence about what is in it or how it is cooked. Avoid long poetry. A guest scanning on a phone reads the name, then the sentence, then decides.

Mark the dishes the kitchen is proudest of with a plain label such as house favorite, only where it is true. Do not stuff the page with adjectives, which tire readers and tell them nothing.

Prices, changes and the date problem

If you list prices, keep them current, since a wrong price on the site causes an awkward moment at the table. If prices move often, say what the menu is and invite guests to ask.

Seasonal dishes need a plan. Decide who updates the page when the kitchen changes it, and how quickly. You can edit the text yourself or ask the in-app assistant to change a line.

Remember the drinks. A short list of what is on tap or by the glass changes often, and some guests look for it first, so give it its own heading and keep it as current as the food.

Allergen and dietary wording

Be careful. A site cannot know what happened in a busy kitchen on a Friday. Mark dishes only as your kitchen can stand behind, and add a plain line asking guests with allergies to tell their server before ordering.

Do not make health claims about dishes. Owners should check their own food rules, and this page is not legal advice.

Ordering, reservations and where the page leads

A site built here has no online store checkout, so the menu should lead to how a guest actually orders: a phone number, a link to your ordering partner, or an invitation to walk in. Make that next step visible at the top and bottom.

Add the hours and address nearby, since people open the menu to decide whether to come. Our page on business hours on a website shows how.

If you take reservations, say how and how far ahead, and what to do for a large group. Link to a booking tool only if you actually use one.

Photos, readability and the printable copy

Use photographs sparingly and give each one a short description of what it shows, so the page reads for someone using a screen reader. Photos of dishes help, but they should never carry words the page does not also say.

Keep the text large enough to read at arm's length and the contrast strong enough to read in dim light. A guest reading by a candle has the same needs as a guest with low vision.

If you keep a printable version, link it at the bottom as an extra and make sure it matches the page. Two versions that disagree cause arguments at the table.

Mistakes that make a menu page useless

These are the problems that make a hungry visitor leave the page and open a map instead.

• A scanned photo of the printed menu as the only version
• A PDF that loads slowly and cannot be zoomed comfortably
• Dish names with no description of what they are
• An old seasonal menu still live after the season
• No next step: no phone number, no ordering link
• Allergen claims the kitchen cannot actually promise