All industries » Restaurant website accessibility

Restaurant website accessibility: menus, online ordering, allergens, and Robles v. Domino's

Restaurant websites are the most-cited category in the original 9th Circuit Robles v. Domino's ruling that established ADA Title III applies to commercial websites with a nexus to a physical place of business. Every restaurant with a brick-and-mortar location is a defendant under that ruling. The online menu, the online ordering flow, the allergen and dietary information, the reservation system, and the location pages are the surfaces plaintiffs target. The CMS landscape (Toast, BentoBox, ChowNow, OpenTable, Resy, Squarespace, custom WordPress) ships predictable WCAG failures that an automated scanner catches in under a minute. Site Brace audits any restaurant website for $149 flat.

Why restaurants are routine ADA defendants

Three structural factors put restaurants in the lawsuit funnel:

• Robles applies cleanly. The Domino's case is the textbook example of ADA Title III applied to a website. Any restaurant with a physical location that takes online orders, displays a menu, or accepts reservations meets the nexus test. The 9th Circuit holding has been adopted in multiple circuits.
• Volume. There are roughly 750,000 restaurants in the United States. Plaintiff-side firms run automated sweeps against restaurant directories (Yelp, Google Maps, OpenTable) and pull thousands of testable sites in a single pass. Independent restaurants and small chains are the typical hits because they lack the in-house engineering of national chains.
• The injury is concrete and easy to document. A blind plaintiff who cannot use the online menu to determine what is available, or cannot complete an online order, has a barrier the court understands without expert testimony. Complaint-drafting costs stay low.

Settlement values for restaurant ADA cases run roughly $5k to $40k for pre-complaint resolution; higher in litigated cases. Multi-location chains have additional exposure because the plaintiff can plead violations across multiple location-specific URLs.

The menu is the central artifact

The online menu is the most-litigated surface on a restaurant website. Two formats dominate, with different accessibility profiles:

HTML menus (the better format)

An HTML menu lives on the site as actual text. Screen readers can read prices, descriptions, and ingredients. Items can be marked up with dietary tags (vegetarian, gluten-free, etc.) that screen readers can navigate. Even an HTML menu can fail on color contrast (dietary badges in faint icons), missing labels (icon-only buttons for "modify ingredients"), or hidden allergen detail (info that only appears on hover with no keyboard equivalent).

PDF menus (the worse format)

A PDF menu uploaded as an image (scanned, or exported from a graphic-design tool without tagging) is invisible to screen readers. The user cannot determine what is available. The fix is either to publish the menu as HTML or to produce a properly-tagged PDF in Acrobat Pro. Most independent restaurants do neither. Replacing the PDF with HTML is the more durable path because HTML menus also rank in Google search; PDF menus do not.

Online ordering as a litigation surface

The online ordering flow (add items, customize, cart, checkout) typically runs through a third-party platform: Toast Online Ordering, ChowNow, BentoBox, Square Online, or Olo. The restaurant is responsible for the accessibility of the rendered experience even when the underlying platform is third-party. If your platform's checkout has unlabeled buttons, your customers' inaccessible experience is your liability.

The most common ordering-flow failures are unlabeled "+" and "-" quantity buttons, color-only "selected" state on size or modifier choices, modal dialogs without proper focus management, and cart drawers that screen readers cannot announce.

What we typically find on a restaurant website

Across restaurant sites Site Brace has scanned, these failures recur.

Multi-location dynamics

Chain and multi-location restaurant sites have additional complexity because each location may have its own URL, its own menu (slight variations), and its own hours and ordering flow. The audit needs to sample location-specific pages, not just the main site, because a plaintiff can plead violations location by location. For chains, the standard page mix shifts to include a sample of 3-5 location pages from different geographies to confirm consistency.

Why overlays are a poor fit for restaurants

Accessibility overlays are heavily marketed to restaurants via small-business marketing publications. We have written about why accessibility overlays do not actually make sites WCAG-compliant in detail. For restaurants specifically: the overlay cannot fix a PDF menu (overlays only touch the rendered DOM, not downloads), cannot fix iframe-embedded third-party widgets (Toast, OpenTable, Olo run inside iframes the overlay does not reach), and provides no defense for the order-flow accessibility that is the most-litigated surface.

The FTC's $1 million settlement with accessiBe in April 2025 makes overlay compliance claims a documented liability rather than a defense.

How Site Brace audits a restaurant website

The standard page mix for a restaurant audit covers the high-risk surfaces:

• Homepage
• Menu page or page-per-menu (lunch, dinner, drinks, kids if separate)
• Online ordering flow (entry page, sample item modifier, cart, checkout entry)
• Reservations widget page (if applicable)
• Locations page (plus 2-4 individual location pages for chains)
• About / our story
• Catering or private events (if applicable)
• Contact, hours, careers
• Accessibility statement (if one exists)

That mix covers up to 25 pages depending on whether the restaurant is single-location or multi-location. The audit runs axe-core 4.10, captures element-level screenshots of every contrast failure, and packages findings into a written report with copy-paste fix code and 12 re-scans included over 12 months.

Pricing is $149 flat, one-time. To see what the report looks like, view a sample report we built for a fictional retail brand (structure and depth are representative).

Start a restaurant website audit, $149

Related:

• E-commerce accessibility audit - the broader category restaurants share litigation patterns with
• Free single-page WCAG check
• Why accessibility overlays do not make sites WCAG-compliant
• axe-core vs WAVE vs Lighthouse
• aria-label on a div: why screen readers ignore it