Key takeaways
- The Justice Department says ADA Title III covers the goods and services public accommodations offer on the web[1], and restaurants are public accommodations[2].
- In a 2026 scan of the top million home pages, 95.9% had detectable WCAG failures, averaging 56.1 errors per page[3].
- Low contrast text, missing image alt text and unlabeled form fields are the most common failures[3], and all three are common on menus and ordering pages.
- Fix the guest journey first: menu, hours, ordering, reservations and contact, tested with a keyboard and a screen reader.
Why restaurant sites get demand letters
Restaurant websites are among the most frequent targets of accessibility demand letters, for simple reasons. Nearly every restaurant has a site, most are built from templates with known problems, and the core content, the menu, is often posted as an image or a scanned PDF that a screen reader cannot read. When ordering and reservations move online, the site stops being a brochure and becomes the way guests buy.
The Department of Justice's web guidance says the ADA's requirements apply to all the goods, services, privileges or activities offered by public accommodations, including those offered on the web, and lists food and drink establishments among Title III businesses[1]. Restaurants and bars are among the 12 categories of public accommodations under Title III[2].
Guests increasingly depend on these pages. Some 57% of adults have recently used mobile ordering[4], and 16% of US adults rely on a smartphone for internet access with no home broadband[5]. An ordering flow that fails with a screen reader or on a small screen with magnification shuts those guests out.
The failures that show up most
WebAIM's 2026 analysis of the top one million home pages found WCAG 2 failures on 95.9% of them, with an average of 56.1 errors per page[3]. The same handful of problems account for most of them, and each has a restaurant version.
| Failure | Restaurant example | Fix |
|---|---|---|
| Low contrast text | Light gray prices on a cream background; text over food photos | Use a contrast checker and darken text or add a solid background |
| Missing alt text | Menu posted as a photo; dish images with no description | Publish the menu as real text; describe meaningful images, mark decorative ones as such |
| Missing form labels | Reservation date and party size boxes with placeholder text only | Give every field a visible label tied to the input |
| Empty links and buttons | Social icons, cart and close buttons with no text name | Add accessible names such as 'Instagram' or 'Close menu' |
| Keyboard traps | Pop-up promo or cookie banner that cannot be closed without a mouse | Make every control reachable and operable with Tab, Enter and Escape |
| Inaccessible PDFs | Scanned catering menu with no text layer | Replace with an HTML page or a tagged, text-based PDF |
The DOJ guidance names the same barriers in plain language: poor color contrast, lack of text alternatives on images, no captions on videos, inaccessible online forms and mouse-only navigation[1].
Menus: the single most important page
If you fix one thing, make the menu readable as text. A guest using a screen reader should be able to hear section names, dish names, descriptions, prices and allergen notes in a sensible order.
- Publish each menu as an HTML page with headings for sections and a consistent pattern for each dish.
- Keep a downloadable PDF only as an extra, and make it a tagged text PDF, not a scan.
- Write prices as text next to each dish, not in a separate column image.
- Use words for dietary symbols, or add a text equivalent such as 'vegan' next to each icon.
- Update the text menu whenever prices or dishes change, so it never lags the printed one.
- Avoid putting the only copy of daily specials in an image post on social media.
Example: a fictional pizzeria's site showed its menu as four photographed pages. A blind guest could not read it, and the site drew a demand letter. The owner rebuilt the menu as a text page using the website builder's menu block, added alt text to the hero image and kept the PDF as a secondary download. The work took one afternoon.
Ordering, reservations and third-party widgets
Many restaurants embed an ordering or reservation tool from a vendor. You choose and publish it, so its accessibility is your concern too. Ask vendors for an accessibility conformance report and test the flow yourself.
- Can a keyboard-only user choose a date, time and party size, then confirm a booking?
- Do item options, such as size and toppings, have labels a screen reader announces?
- Are error messages, such as an invalid phone number, announced and explained in text?
- Can the guest double the text size without losing content or controls?
- Does a time limit on checkout give enough warning and a way to extend?
- Is there a phone number and email in text on the same page for anyone who cannot complete the flow?
An alternative channel helps guests but does not replace an accessible website. A phone line answered reliably, whether by staff or by an SI Employee such as Ava that takes reservation requests and answers menu questions, gives guests another route while you fix the site.
Run an accessibility check in a day
Scan automatically
Run a free automated checker on your home, menu, ordering, reservation, catering and contact pages. It will find contrast, alt text and label problems quickly.
Test with a keyboard
Unplug the mouse and use Tab, Shift+Tab, Enter and Escape to move through each page and complete an order and a booking.
Test with a screen reader
Use the screen reader built into your phone or computer to listen to the menu page and the ordering flow.
Zoom and resize
Zoom the browser to double size and check on a narrow phone screen that nothing is cut off or overlapping.
Fix the journey first
Prioritize menu, hours, location, ordering, reservations and contact, then the rest of the site.
Publish a statement
Add an accessibility page with a contact for problems, and respond quickly to anyone who uses it.
Automated tools catch only part of the problem. A short manual test is what reveals a booking calendar that a keyboard cannot operate or a cart button with no name.
Keep it accessible after launch
Most restaurant sites become inaccessible again within months, not because of the template but because of everyday updates. A manager uploads a photo of the new brunch menu, a promo banner goes up with white text on a bright photo, or a new catering form is added with no labels. Write a one-page content guide for anyone who edits the site.
- Menus and specials go in as text, never as a photo of a printed page.
- Every image gets a short description of what matters, such as the dish name, or is marked decorative.
- Text on top of photos needs a solid or darkened background behind it.
- Links say where they go, such as 'View the catering menu', not 'Click here'.
- New forms use the website builder's labeled fields, never placeholder text alone.
- Videos get captions before they are published.
Add a quick accessibility check to the same routine you use to update prices and hours. Ten minutes with a keyboard and an automated checker each month catches most problems before a guest does.
Beyond your own site
Guests meet your restaurant on many screens you do not control directly: map listings, review sites, delivery apps and social profiles. You cannot fix those platforms, but you can make your own content on them usable. Type your hours, address, phone number and menu highlights as text in each profile. Add descriptions to the photos you post where the platform allows it. Keep the menu on your own site complete and current, so that it is the reliable source when a third-party listing is out of date.
When you choose a new website builder, ordering platform or reservation tool, put accessibility in the requirements alongside price and features. Ask for the vendor's conformance report, test a sample site with a keyboard and a screen reader, and include a clause in the contract that the vendor will fix accessibility defects in its product within a reasonable time.
Avoid quick fixes that do not fix
Overlay widgets that promise instant compliance with a single line of code are popular with restaurant owners because they are cheap and fast. They do not repair the underlying page and are not a substitute for fixing contrast, labels, alt text and keyboard access in the site itself. Spend the effort on the template and the menu instead.
For the physical side of accessibility, read ADA compliance for restaurants. For employment rules, see avoiding discrimination claims in restaurants.
Frequently asked questions
Does the ADA apply to restaurant websites?
The Justice Department says Title III covers goods and services that public accommodations offer on the web. Restaurants are public accommodations, so their sites should be accessible.
Is a PDF menu accessible?
Usually not if it is a scan or image. Publish the menu as text on a web page and keep any PDF as a tagged, text-based extra.
Will an accessibility overlay protect my restaurant website?
No overlay fixes the underlying code. Fix contrast, alt text, form labels and keyboard access in the site itself.
What standard should a restaurant website meet?
Most businesses aim for WCAG 2.1 or 2.2 level AA. Focus first on the menu, ordering, reservations and contact pages.
References
US Department of Justice (ADA.gov) (2022). Guidance on Web Accessibility and the ADA (opens in a new tab) ↑
US Department of Justice (ADA.gov) (2026). ADA Title III Regulations primer (opens in a new tab) ↑
WebAIM, Utah State University (2026). The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
Pew Research Center (2026). Americans' Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑