ADA compliance for restaurants, focused where the risk is
Your website is where most diners decide where to eat — they read the menu, place an order, or book a table. For people who use a screen reader or navigate by keyboard, those same three actions are where restaurant sites break most often. ADA compliance for restaurants means making your menu, ordering, and reservations genuinely usable for everyone — and Curbcut does it by remediating the actual code, not by bolting on an overlay.
Food-service websites are among the most-sued categories online, and it’s not by accident. The features that drive your revenue are the exact ones plaintiffs and their testers check first.
Why restaurants get targeted
Under ADA Title III, courts have widely treated business websites as “places of public accommodation,” and the DOJ has affirmed that the ADA applies to the web even without a single dedicated technical regulation for it. Thousands of ADA web lawsuits are filed each year, and many begin with a demand letter rather than a complaint. Restaurants stand out because:
- Menus are often posted as image files or untagged PDFs a screen reader simply cannot read.
- Online ordering flows rely on custom forms, modals, and “add to cart” buttons that fail keyboard and screen-reader testing.
- Reservation widgets use date pickers and time selectors that trap focus or lack labels.
- Promotional banners, food photography, and hero images frequently ship without alt text.
This is not legal advice — if you’ve received a letter, talk to an attorney. But the technical pattern is consistent and fixable. See how to lower your lawsuit exposure.
The menu problem: your single biggest liability
The menu is the heart of a restaurant site and the most common point of failure. A photo of a menu, a scanned PDF, or a Flash-style embedded viewer all present the same wall to a blind customer: no readable text, no prices, no dietary information.
| Common menu setup | Accessibility problem | The fix |
|---|---|---|
| Image (JPG/PNG) of the menu | No machine-readable text at all | Rebuild the menu as real HTML text |
| Scanned or untagged PDF | Screen reader reads nothing or gibberish | Provide an HTML menu, or a properly tagged accessible PDF |
| Low-contrast menu styling | Text fails color contrast minimums | Adjust colors to meet WCAG 2.1 AA (4.5:1) |
| Menu in a JS widget | Not reachable by keyboard navigation | Use semantic markup and proper focus order |
The most durable solution is an HTML menu structured with real headings and lists, so it works with NVDA, JAWS, and VoiceOver and is easy to keep current. If you must keep a downloadable file, make it a genuinely accessible PDF rather than a flat scan.
Online ordering: where keyboard users get stuck
Ordering flows are interactive, which makes them the second-most-cited barrier. We test the full path — browse, customize, add to cart, check out — for:
- Keyboard operability: every control reachable and usable without a mouse, with a visible focus indicator.
- Labels and ARIA: quantity steppers, modifiers, and modals announced correctly to assistive technology, using ARIA roles and states only where native HTML can’t do the job.
- Error handling: clear, programmatically associated error messages on checkout forms.
- Third-party tools: many restaurants embed an outside ordering or reservation provider. You’re still generally responsible for it under Title III, so we document what those flows do and don’t pass.
The same risks apply to any cart, which is why our ecommerce accessibility approach and our hotel and hospitality work share the same testing discipline.
What WCAG 2.1 AA actually requires
Accessibility standards are organized around four POUR principles — content must be Perceivable, Operable, Understandable, and Robust. The practical target for ADA-related compliance is WCAG 2.1 Level AA (the A / AA / AAA scale describes conformance levels; AA is the accepted bar). For government-adjacent work, the closely related Section 508 standard incorporates the same WCAG criteria. You can read the standards straight from the source at the W3C Web Accessibility Initiative, and the federal perspective at ADA.gov and Section508.gov.
For a restaurant, AA conformance comes down to a handful of high-impact essentials:
- Text alt text on food photos and logos; empty alt on decorative images.
- Color contrast that survives your brand palette and overlaid text on hero images.
- Full keyboard navigation through menu, ordering, and reservations.
- Correct heading structure so screen-reader users can jump to “Menu” or “Hours.”
- Accessible forms for catering inquiries, waitlists, and checkout.
How Curbcut fixes it — manual remediation, never overlays
Overlay widgets promise instant compliance, but they don’t repair the underlying barriers — and courts have ruled against businesses that relied on them. They can even interfere with the assistive technology your customers already use. Curbcut does the durable work instead.
Our process for restaurant sites:
- Audit — a combined manual and automated accessibility audit of your menu, ordering, and reservation flows against WCAG 2.1 AA, validated with real screen-reader and keyboard testing.
- Remediate — hands-on accessibility remediation in your actual codebase: rebuilt menus, labeled forms, fixed contrast, alt text, and ARIA.
- Document — a VPAT / Accessibility Conformance Report and an accessibility statement so you can show your conformance status.
- Monitor — optional ongoing checks, because menus and specials change weekly and new content can reintroduce issues.
The result holds up for your customers and stands on the durable, code-level work that overlays skip. Compare overlay claims to real remediation.
Start with a free scan
You don’t have to guess where your site stands. A free accessibility scan flags the most common menu, ordering, and reservation barriers in minutes — and we’ll show you exactly what a full manual audit would cover next.