Over 3,100 ADA web accessibility lawsuits were filed in federal court in 2025 — a 27% jump from 2024. A menu that only exists as a scanned PDF, unreadable by a screen reader, is one of the most common and easily fixed triggers.
Title III Applies to Your Website, Not Just Your Dining Room
Title III of the Americans with Disabilities Act (ADA) prohibits discrimination on the basis of disability in "places of public accommodation" — a category that explicitly includes restaurants. Courts have consistently interpreted this to extend beyond the physical dining room to a business's website and mobile app, treating them as an extension of the public accommodation itself. This interpretation isn't new, but enforcement volume has grown sharply: 3,117 website accessibility lawsuits were filed in federal court in 2025, a 27% increase over 2024, and website accessibility claims now make up roughly 36% of all ADA Title III federal filings. For every lawsuit that reaches federal court, defense attorneys report handling many more demand letters that get resolved privately — so published filing counts understate real exposure.
There's No Official Technical Standard for Private Businesses — Yet Courts Still Enforce One
This is the detail that catches most restaurant owners off guard: unlike state and local governments, which now have explicit deadlines under a 2024 DOJ rule to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standard, Title III itself does not specify a technical standard for private businesses. There is no regulation a restaurant can point to and say "we comply with this exact rule." In practice, that absence of a bright-line standard is precisely what plaintiffs' attorneys exploit — and WCAG 2.1 Level AA has become the de facto benchmark courts reference anyway when evaluating whether a website provided "effective communication" and "full and equal enjoyment" as Title III requires.
Restaurants should not read "no official private-sector rule" as "no real risk." The litigation data shows the opposite: the absence of a fixed standard is a major driver of continued filings, precisely because there's no simple compliance checkbox to point to as a defense.
Why PDF-Only Menus Are the Single Most Common Trigger
A menu published only as a scanned image or a non-tagged PDF is invisible to a screen reader — the assistive technology simply cannot extract readable text from it, meaning a blind or low-vision customer cannot learn what's on the menu at all without calling the restaurant directly. This is one of the most frequently cited defects in restaurant-industry ADA web accessibility claims, precisely because it's so common and so easy to demonstrate: a plaintiff's attorney can show a court, in minutes, that the assistive technology returns nothing usable.
Practical Steps Toward WCAG 2.1 AA
- Replace image-only or scanned-PDF menus with real HTML text — a screen reader can read HTML directly; it cannot read text embedded in an image.
- Ensure sufficient color contrast between text and background throughout the site, not just on the menu page.
- Make every interactive element (reservation widget, online ordering, contact form) fully operable by keyboard alone, not just by mouse or touch.
- Add descriptive alt text to meaningful images; decorative images should be marked so screen readers skip them.
- Test with an actual screen reader (e.g. VoiceOver or NVDA) rather than relying solely on automated scanning tools, which catch only a portion of real-world barriers.
None of this requires a specific court-ordered deadline to be worth doing now — the safest position for a restaurant is to treat WCAG 2.1 AA as the practical standard today, given how consistently courts already reference it.
Related Kibbo Tools
Sources
- Level Access — ADA Title III Lawsuits: Companies Sued Over Web Accessibility, citing Seyfarth Shaw's 2026 litigation analysis. levelaccess.com
- U.S. Department of Justice — Title II Web and Mobile Application Accessibility Final Rule, 28 CFR Part 35 Subpart H. ada.gov