Is your restaurant menu accessible? PDF vs web page and an ADA checklist

A restaurant's website is often a PDF of the menu, a photo of a chalkboard and a link to an ordering page. For a guest who uses a screen reader, a PDF that is a picture of text is a blank page. Lawsuits and demand letters over inaccessible restaurant websites have continued to rise, and the menu is the most common problem. Here is how to make your menu usable for everyone, with a checklist you can work through in an afternoon. It complements the general guide on website accessibility for restaurants in this series.

Why does the menu matter so much?

The menu is the part of your website most guests actually use. Guests who are blind, have low vision, are deaf, have motor disabilities or have dyslexia all rely on being able to read and navigate it. Accessibility lawsuits against restaurants generally rest on Title III of the Americans with Disabilities Act and many suits have been filed in recent years. Many came from demand letters tied to blind plaintiffs who said sites did not work with screen reading software. Courts have not agreed on whether a website must be tied to a physical place, which is why the risk is uncertain but real.

What is the legal standard?

There is no federal rule written for private restaurant websites. The Department of Justice adopted a 2024 rule for state and local government websites and apps that sets the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as the standard, and while that rule does not apply to private businesses, it serves as a roadmap. In practice, WCAG 2.1 AA is the benchmark that plaintiffs, courts and settlements most often use for private businesses. Aim for it.

What goes wrong with PDF menus?

A common example: a PDF menu that is not properly tagged, so a screen reader announces menu items incorrectly, for example as headings, and reads them in an order that differs from the visual layout. Those are failures of WCAG criteria on structure and reading order. A scanned or photographed menu is worse, because it has no text at all. PDFs are also hard to read on a phone, they cannot be resized without scrolling sideways and they are easy to forget to update.

What is the best alternative?

Publish the menu as a regular web page with real text: headings for sections such as starters and mains, each dish as text with its description and price, and notes for allergens and dietary labels. Screen readers, search engines and phones all handle this better. If you want a downloadable version for printing, offer a properly tagged PDF as an extra, not the only option. Make sure the web page is the one you update first.

What does an accessible menu page include?

• Real text, not images of text. If you use an image, add a text alternative that gives the same information.
• Headings in order. Use a main heading for the page and subheadings for sections.
• Clear prices and descriptions next to each dish, in reading order.
• Dietary and allergen labels in words, not only by color or icon.
• Enough contrast between text and background, and text that can be enlarged.
• Descriptive links and buttons, such as "Order online" rather than "Click here."
• Alternative text for photos that explains what they show.

How do you check your ordering page?

Try to complete an order using only the keyboard: tab through the fields, choose items, add a note and pay. Every control should be reachable and visible when focused. Form fields need labels, errors need clear messages, and any timers or pop-ups must not trap the user. Test on a phone with the built-in screen reader, which takes ten minutes. If your ordering page is provided by a vendor, ask whether it meets WCAG 2.1 AA and request a written statement.

A one-afternoon plan for a small restaurant

Start by listing every page where guests read your menu: the website, the online ordering page, social media and any third-party listing. Replace each PDF or photo with a text version on a web page, and keep the old file only as a printable extra. Next, add headings, check the contrast of your text, write short descriptions for photos and label your dietary notes in words. Then try the ordering flow with a keyboard and with your phone's screen reader. Finally, publish a short accessibility statement with a contact number, and put a reminder in your calendar to repeat the check each time the menu changes. This is a modest amount of work, and it makes your site better for every guest, including those on small screens in a noisy room.

What should you publish and do next?

Add a short accessibility statement to your website with a phone number and email for guests who have trouble, and answer those messages quickly. Keep a record of what you fixed and when. If you receive a demand letter, do not ignore it; talk to a lawyer who handles accessibility claims, and fix the issues listed. Spend an afternoon on a simple checklist first, since a good faith effort and a quick fix put you in a stronger position than silence.

What about in-restaurant menus?

The same spirit applies in the dining room: offer a large-print or screen-friendly version of the menu, and train staff to read it aloud on request. A welcoming answer at the table is the most direct way to serve guests with disabilities.

More guides for your business:

• Can a restaurant charge a no-show fee in Oregon, New Hampshire or Arizona?
• Can a restaurant ask for reviews? The FTC fake review rule explained
• Online ordering for restaurants in Oregon, New Hampshire and Arizona

More in the US guides for food businesses.