ADA · By industry
ADA compliance for restaurant websites
ADA compliance for a restaurant website means a menu a screen reader can read, an ordering flow a keyboard can finish, and a reservation widget with labeled fields, in line with the WCAG criteria courts reference in ADA cases. Food service is a perennial leader in ADA website filings, and the barriers are almost always the same three: image or PDF menus, third-party ordering widgets, and unlabeled forms. Complidar scans your site the way a plaintiff's investigator would and shows you those barriers before a demand letter does.
Why restaurants get sued so often
Restaurants sit at the top of ADA Title III web filings (tracked annually by Seyfarth Shaw and UsableNet) for structural reasons: nearly every restaurant has a website, menus are usually PDFs or images a screen reader can't parse, ordering and reservations run through third-party widgets the owner never accessibility-tested, and the business behind the site is usually small enough to settle rather than fight.
The canonical website-accessibility case is itself a restaurant case. In Robles v. Domino's Pizza a blind customer couldn't complete an order through the site or app; the Ninth Circuit held the ADA applied, the Supreme Court let that stand, and the multi-year fight ended around $325,000 plus fees. The demand letters that followed cite the same theory and are priced below the cost of answering one.
The three barriers that draw claims
Almost every restaurant claim traces to the same surfaces, all of them detectable from the outside:
- Image-only or untagged-PDF menus, the single most-cited barrier in restaurant suits, because the screen reader simply can't read them
- Online-ordering widgets and 'order now' flows that can't be completed with a keyboard
- Reservation and contact forms with no field labels, so a screen-reader user can't tell name from party-size from date
The risk that rides along with online ordering
Once a site takes orders and signups, accessibility is no longer the only exposure. SMS-marketing programs fall under the TCPA, where statutory damages run $500 to $1,500 per text and class actions have reached nine figures. Ordering and reservation pages routinely embed session-replay and ad trackers that trigger wiretap and state-privacy theories. A scan that only checks WCAG misses most of what a restaurant site can be sued over, which is why Complidar runs all 22 checks, not just accessibility.
What the scan checks here
- Full WCAG / axe-core accessibility pass across menu, ordering, and reservation pages
- Image-only and untagged-PDF menus flagged as the screen-reader barriers plaintiffs cite
- Keyboard operability of 'order now' and reservation flows, embedded widgets included
- Form-field labeling on reservation, contact, and signup forms
- TCPA consent language on any SMS-marketing signup
- Session-replay and advertising trackers on ordering pages (wiretap / state-privacy exposure)
Honest limits: A scan flags the mechanical barriers: unreadable menus, unreachable controls, missing labels. It can't judge whether a menu's wording is clear or whether a custom ordering widget is genuinely usable end to end; those need human review, and the report marks which findings are which rather than implying a clean automated pass equals full conformance.
Common questions
Is a PDF menu really an ADA problem?
Image-based and untagged PDF menus are among the most-cited barriers in restaurant web suits, because a screen reader can't read them at all. An HTML menu, or a properly tagged PDF, removes one of the most common claims outright. The scan flags untagged menu documents it finds.
My ordering and reservations are third-party widgets. Am I still liable?
The demand letter names the restaurant, not the widget vendor, because your site is the public accommodation customers use. Complidar scans the pages and embedded widgets your customers actually touch, so you can see what a plaintiff sees and take the vendor conversation from there.
What does a restaurant website scan cost?
The preview is free: violation count, severity, and an estimated liability range across up to 120 pages, no card. The full report with evidence and fixes is a one-time unlock, and monitoring matters here because menus and platforms change constantly.
All 22 checks · up to 120 pages · no card
Last updated 2026-06-28 · Informational, not legal advice: how to read this