Web Accessibility for Restaurants: Compliance Guide
TLDR
Restaurants are a top-five ADA web accessibility lawsuit target. Online ordering, reservation flows, and menu PDFs are the three highest-risk components. Domino's spent six years litigating a case that started with a blind user who could not order pizza online. Automated scanning catches most programmatic failures; the ordering flow needs manual testing.
Restaurants and the Domino’s Precedent
Robles v. Domino’s Pizza is the case every restaurant operator should understand. Guillermo Robles, a blind user, alleged he could not use Domino’s website or mobile app to order pizza because neither was compatible with his screen reader. The Ninth Circuit ruled in 2019 that ADA Title III applies to Domino’s digital ordering channels. The Supreme Court declined to intervene. Domino’s settled in 2022 after six years of litigation.
The case established that a restaurant’s website and app, when they connect customers to a physical restaurant location, are subject to ADA requirements. Your online ordering system is not optional from an accessibility standpoint just because it is digital.
The Three Highest-Risk Areas
Online Ordering
The entire ordering flow — browsing the menu, adding items to cart, customizing orders (extra cheese, no onions, sauces), entering delivery or pickup information, and completing payment — must be operable by keyboard alone and comprehensible to screen readers.
Custom ordering components built with JavaScript and HTML divs are the typical failure point. A screen reader user navigating a menu built as a grid of images with click handlers may encounter items with no announced names, no quantity controls, and no way to add to cart via keyboard.
Menu PDFs
The menu published as a PDF is a near-universal restaurant accessibility failure. Most restaurant menus are designed in Adobe InDesign or Canva and exported as visual layouts — the PDF is effectively an image. A screen reader cannot read an image-based PDF.
The fix options: publish the menu as an HTML page (most accessible, easily updated), or produce an accessible PDF with proper tag structure (more work, but usable for download). Providing both — HTML for web viewing, accessible PDF for download — covers all use cases.
Reservation Systems
Date and time pickers in reservation forms are notoriously difficult to make accessible. Custom calendar widgets often lack keyboard navigation, have no ARIA roles declaring their structure, and announce confusing information to screen readers. The party size dropdown needs a label. The date field needs a format hint. The confirmation step needs to announce success to assistive technologies.
What Scanning Catches on Restaurant Sites
A11yProof’s automated scan runs across your website and identifies: missing alt text on menu item photos, unlabeled reservation form inputs, low-contrast decorative typography (common on menus with thematic styling), missing ARIA on custom interactive elements, and any accessibility attributes on PDF menu links that signal an inaccessible document.
The ordering flow needs manual keyboard testing after scanning to verify that the full task — finding an item, customizing it, adding to cart, and completing checkout — is completable without a mouse.
A11yProof starts at $29/month for a single restaurant site, running scheduled scans that alert on new violations from content updates, menu changes, or third-party tool updates.
Need accessibility compliance for Restaurants? There's a simpler way.
A11yProof starts at from $29/month — scan unlimited pages, up and running in 5 minutes.
Source: UsableNet 2023 Year-End Report
Source: UsableNet 2023 Year-End Report
| Metro Area | Establishments |
|---|---|
| Full-service restaurants | 350,000 |
| Limited-service and fast casual | 400,000 |
| Bars and nightclubs | 62,000 |
| Total — REST | 1,000,000+ |
| Issue | WCAG Criterion | Risk Level | Typical Fix |
|---|---|---|---|
| Online ordering flow keyboard-inaccessible | 2.1.1 | Critical | Test full ordering flow with keyboard; fix all non-keyboard-operable controls |
| Menu PDF untagged or image-only | 1.1.1 | Critical | Publish HTML menu or use properly tagged accessible PDF |
| Menu item images without alt text | 1.1.1 | High | Add descriptive alt text to all food photos |
| Reservation form fields unlabeled | 1.3.1, 3.3.2 | High | Associate <label> with each reservation form input |
| Cart/order updates not announced | 4.1.3 | High | Add ARIA live regions to cart and order confirmation areas |
| Low contrast on stylized menu typography | 1.4.3 | Medium | Adjust decorative typography colors to meet 4.5:1 ratio |
Compliance Requirements — Restaurants
Restaurant businesses are places of public accommodation under ADA Title III. Courts have consistently applied ADA requirements to restaurant websites, particularly online ordering and reservation systems. Robles v. Domino's Pizza (2019) is the landmark case establishing that ADA applies to restaurant digital ordering channels.
Q&A
Why are restaurants one of the most frequently sued categories for web accessibility?
The Domino's case (Robles v. Domino's Pizza) drew attention to restaurant online ordering accessibility. Courts applying Ninth Circuit precedent have found that restaurant websites and apps are covered by ADA Title III because they connect customers to physical restaurant locations — places of public accommodation. The key risk factors: online ordering is how many customers interact with restaurants, and a blind or low-vision user who cannot complete an order faces a concrete, demonstrable barrier. These factors make restaurant accessibility failures easy to demonstrate in litigation.
Q&A
What accessibility scanning covers for restaurant websites?
A11yProof's automated scanning identifies the programmatic failures on restaurant sites: missing alt text on menu item photos, unlabeled form fields in reservation systems, low-contrast decorative text on menus and hero sections, missing ARIA on custom ordering controls, and PDF menus that lack accessibility indicators. The full ordering flow — add to cart, customize, checkout, confirm — needs manual keyboard and screen reader testing that automated tools supplement but cannot fully replace.
Industry Regulations — Restaurants
Restaurant online ordering volume peaks during holidays and special event periods. High-traffic periods increase the number of users encountering accessibility barriers.
Ready to make your Restaurants site accessible?
Do menu PDFs need to be accessible?
Does my third-party online ordering platform need to be accessible?
What makes a reservation system accessible?
How do I handle food allergy and dietary information accessibility?
Is there an easy starting point for a restaurant with no accessibility work done?
Keep reading
The Domino's Accessibility Lawsuit: What It Means for Your Business
Robles v. Domino's Pizza reached the Supreme Court and reshaped web accessibility law. Here is what the case decided and what it means for SMBs with websites.
ADA Compliance for Websites: What Business Owners Need to Know
A plain-English explanation of ADA web accessibility requirements for business owners. Covers legal risk, what courts expect, DOJ guidance, and how to demonstrate compliance.
WCAG 2.1 AA Compliance Checklist for Website Owners
A plain-English WCAG 2.1 AA compliance checklist organized by the four POUR principles. Covers the most common success criteria and how to test them.
How to Run a Digital Accessibility Audit (Step-by-Step)
A digital accessibility audit finds WCAG violations before plaintiffs do. This step-by-step guide covers planning, automated scanning, manual testing, and reporting.
Best accessiBe Alternative for SMBs Who Need Real WCAG Compliance
Looking for an accessiBe alternative that actually fixes your code? See how A11yProof compares on scanning depth, remediation, and lawsuit protection.
Best AudioEye Alternative for SMBs Who Don't Need Enterprise Pricing
Looking for an AudioEye alternative without enterprise contracts? See how A11yProof compares on pricing, scanning, and AI remediation for small and mid-size teams.