ADA Lawsuits Against Restaurants: Website Fixes That Matter

Restaurants are the most targeted industry for ADA website lawsuits. Sixty percent of 2025 filings hit restaurants and apparel businesses.

The pattern is predictable. PDF menus, missing alt text on food photos, inaccessible reservation forms. Serial filers know exactly what to look for.

Why Restaurants Are Among the Most Targeted Industries

Serial filers, plaintiffs and law firms that file dozens or hundreds of ADA cases per year, use automated tools to scan websites for violations. Restaurant websites fail those scans in predictable ways.

PDF menus. Missing alt text on food photography. Reservation forms built on third-party widgets that nobody tested with a screen reader. Every one of those violations is documented in seconds. That documentation becomes the core of a federal complaint.

About 26% of U.S. adults live with some type of functional disability. When you include family members and caregivers who help plan outings, more than 180 million people in the U.S. are directly affected by whether a restaurant's website is accessible. These are not fringe users. They are your customers, and they are trying to look at your menu before they decide where to eat.

The legal exposure for restaurants comes from Title III of the Americans with Disabilities Act, which prohibits discrimination in places of public accommodation. Courts have consistently held that your website is part of how your restaurant interacts with the public. If people with disabilities cannot use it, that is a barrier. And barriers are what plaintiffs look for.

The PDF Menu Problem

This is the one that surprises restaurant owners most.

A PDF menu posted as an image file is not just a design choice. It is a WCAG 2.1 violation. Screen readers, the primary tools used by people who are blind or have low vision, cannot read image-based PDFs. They scan the file and find nothing. From the perspective of someone relying on a screen reader, the menu page is blank.

Not limited. Not awkward. Completely inaccessible.

This is one of the most cited violations in lawsuits against restaurants. The fix is not complicated. An HTML menu, built with proper heading structure and readable text, works for screen readers and ranks better in search engines at the same time. If you want to offer a printable PDF version as well, that is fine. Offer both. Just do not make the PDF the only way to see what you serve.

The same problem applies to image-only specials boards, flyer images posted in place of text, and photos of handwritten menus. If the information only exists as an image, a screen reader cannot read it.

Reservation Widgets Are Not OpenTable's Problem

OpenTable. Resy. Yelp reservations. These platforms are better than most at accessibility. They have dedicated engineering teams and public accessibility statements. But "better than most" is not the legal standard. WCAG 2.1 Level AA is.

When a plaintiff files against your restaurant because the reservation flow is inaccessible, the complaint is against you. Not OpenTable. Your website. Your name on the lawsuit. You chose the tool. You embedded it. You are responsible for what it does on your pages.

The practical test is simple. Tab through your entire reservation flow without touching your mouse. Can you reach the date picker? Can you select a party size from a dropdown using only the keyboard? Can you enter your name, email, and phone number in every field? Can you submit the form? If any step breaks, that is an accessibility barrier. A developer can usually fix most keyboard navigation failures without abandoning the widget at all.

Test it yourself. Press Tab to move forward through your site. Press Shift+Tab to move backward. Press Enter or Space to activate buttons and links. If you get stuck, find an element you cannot reach, or see a focus indicator disappear entirely, you have found a problem worth fixing.

The Most Common Fixes on Restaurant Websites

Not every accessibility violation carries the same legal weight. The ones that show up most often in restaurant-related lawsuits fall into four categories.

• !
  Missing alt text on food photography. Every meaningful image needs a text description. A dish photo without alt text is a violation. Your appetizers, entrees, and atmosphere shots all need descriptions a screen reader can announce.
• !
  Low color contrast. Restaurant branding tends toward dramatic visuals. Dark backgrounds with white text. Colored text on patterned backgrounds. If the contrast ratio between your text and its background falls below 4.5:1, it fails WCAG and is unreadable for people with low vision.
• !
  Unlabeled form fields. Contact forms, reservation forms, and email signups all need real label elements connected to each input. Placeholder text that disappears when you start typing does not count.
• !
  Keyboard navigation failures. Every element a mouse can reach, a keyboard must also reach. Dropdown menus, modal windows, and carousels are the most common failure points on restaurant sites.

There is a fifth category that catches many restaurant owners off guard: video content. If your site includes video, whether a brand film, a cooking video, or footage from a private dining event, it needs captions. Auto-generated captions from a video platform are not sufficient. They are full of errors and do not meet the WCAG standard for accurate captions.

What a Lawsuit Actually Costs

Most ADA website lawsuits settle before trial. That does not mean the cost is low.

A typical settlement against a restaurant runs between $5,000 and $25,000. Add attorney fees. Under the ADA's fee-shifting provision, you may be required to pay the plaintiff's attorney fees in addition to your own. Add the cost of remediating the site after the fact. Add the time you are not spending on your restaurant while you are dealing with it.

The all-in cost of a single lawsuit, including settlement, legal fees on both sides, and site remediation, frequently lands between $20,000 and $75,000.

For serial filers, the economics are intentional. File quickly. Settle quickly. Move on. A quick $10,000 settlement feels like the easier path for most restaurant owners, which is exactly what makes it work for the filers. Your discomfort with litigation is factored into their business model.

A comprehensive accessibility audit that identifies every WCAG violation on your site costs $49. A developer can typically address the most critical issues in a few hours. The gap between the cost of prevention and the cost of defense is not a close call.

What to Do Right Now

You do not need to rebuild your site. You need to know what is actually wrong with it.

Start with a scan. A free accessibility check at ADA Audit Report will show you where your site stands in about 60 seconds. The full $49 report maps every violation to its specific WCAG criterion, identifies which issues carry the most legal risk, and gives your developer step-by-step remediation guidance with code context for each finding.

Three things to prioritize first: alt text on every image, labels on every form field, and keyboard navigation through your reservation flow. These are the violations that appear most often in restaurant lawsuits. Get those fixed, then work through the rest.

Keep a record as you go. Courts treat a business that identified its accessibility problems and worked to fix them very differently from a business that received a demand letter and had no documentation of ever trying. The audit report is the first piece of that documentation. The developer's fix notes are the second. The re-scan confirming the fixes are in place is the third.

Restaurant websites are not uniquely hard to make accessible. They are commonly neglected. The fixes are fast, the costs are modest, and the protection is real. The question is whether you want to handle it now, on your timeline, or later, on someone else's.