Hotels and restaurants get sued over their websites because they combine three things plaintiffs' firms look for: transactions that happen online (menus, ordering, reservations, room bookings), an undisputed link to a physical place the ADA clearly covers, and site features that routinely fail accessibility testing. A restaurant website ADA lawsuit typically begins when a screen-reader user can't read a menu or place an order; hotel suits usually target reservation systems that fail to describe accessible rooms. The pattern is common enough that food service alone accounted for roughly 18% of web-accessibility lawsuits filed in 2025 — second only to e-commerce.
More than 5,000 digital-accessibility lawsuits were filed in 2025, up roughly 20% over 2024. Here is why hospitality sits near the front of that line, what a suit actually costs, and which fixes genuinely reduce risk.
Why are restaurants such frequent lawsuit targets?
Three reasons — and none of them are bad luck.
The menu is the product. If a blind visitor using a screen reader can't read your menu, they can't decide to eat with you. Most restaurants publish menus as PDFs or flat images — formats assistive technology often can't read unless they were deliberately built for it.
Ordering and reservations are transactions. Courts care most about whether a barrier blocks someone from actually doing business with you. The defining case is Robles v. Domino's Pizza: in 2019 the Ninth Circuit held that the ADA applies to a website and app connected to physical locations, and the Supreme Court declined to review it. The test case for the whole question was a pizza-ordering flow.
The physical nexus is undeniable. Some courts still debate whether a purely online business is a "place of public accommodation." Nobody debates it about a restaurant with a dining room or a hotel with a front desk. That certainty removes a defense argument before the case even starts — one reason serial filers favor hospitality, a pattern we break down in how serial plaintiffs pick their targets.
Why do hotels face their own dedicated wave of suits?
Hotels carry every restaurant risk factor plus a regulation written specifically for them. The Department of Justice's reservation rule (28 CFR 36.302(e)) requires hotels to identify accessible rooms and describe their accessibility features in online reservation systems — in enough detail that a traveler with a disability can judge whether a room meets their needs before booking.
That creates two separate ways to get sued. The first is the general claim: the site doesn't work with a screen reader or keyboard. The second is the reservation-rule claim: the booking flow doesn't say what the regulation requires about accessible rooms. A dedicated wave of hotel-website lawsuits targets exactly that second gap.
If your booking engine lists an "ADA King" with no description of the roll-in shower, grab bars, door clearances, or path to the elevator, you have precisely the omission those suits are built on. The rule itself is published on ADA.gov.
What does a restaurant website ADA lawsuit actually cost?
Most of these cases settle, and quickly. Typical settlements run between $10,000 and $75,000 plus a binding commitment to remediate the site — with average settlement costs above $30,000 before your own attorney's fees. Remediation isn't optional after settling; it's a term of the agreement, so waiting to be sued means paying twice.
Geography changes the math. New York leads the nation in state-court web-accessibility filings, Florida is the most active state for federal ones, and California adds the Unruh Act — minimum statutory damages of $4,000 per violation plus attorney's fees, with any ADA violation automatically counting as an Unruh violation. Multi-location restaurant groups and hotel brands can face parallel actions in several of these jurisdictions over the same website.
Which accessibility failures show up most on hospitality sites?
Sitewide failures are the norm, not the exception: WebAIM's 2025 analysis of the top one million homepages found detectable WCAG failures on 94.8% of them. Hotel and restaurant sites tend to concentrate the classics:
- PDF-only or image-only menus that screen readers can't parse.
- Low-contrast text — thin, pale type over food and property photography. WCAG requires a 4.5:1 contrast ratio for normal text.
- Missing alt text on dish and room photos, so the images convey nothing to blind visitors.
- Unlabeled form fields in reservation widgets — date pickers and party-size selectors that a screen reader announces only as "edit text."
- Booking and ordering flows that break for keyboard users, trapping focus inside calendars or requiring a mouse to finish.
None of this is exotic. Much of it shows up in an automated scan — and a free accessibility audit from ADA Fail will surface those issues quickly. But automated tools can detect only about a third of WCAG success criteria; booking-flow and menu problems in particular usually need a human tester to catch.
Will an accessibility overlay protect you?
No. UsableNet's litigation reports repeatedly find hundreds of companies each year were sued while already running an accessibility widget or overlay. In January 2025 the FTC ordered overlay vendor accessiBe to pay $1 million over allegations that it deceptively claimed its widget could make any website WCAG-compliant. The National Federation of the Blind describes overlay products as "not only ineffective but harmful."
One distinction matters here. A preference widget — a user-facing control for contrast or text size, added to a site that is already accessible at the code level and making no compliance claims — is a legitimate convenience; ADA Fail's own site runs one. A "compliance" overlay — a third-party script sold as making a broken site compliant — is a different product entirely, because it never changes the underlying code that screen readers and lawsuits are aimed at. The problem is the compliance claim, never the preference button. We cover the mechanics in why overlay widgets fail.
What should hotel and restaurant owners do now?
- Get menus out of PDF-only formats. Publish the menu as real HTML text on the page; keep the PDF as a secondary download if you like the print layout.
- Run the keyboard test on your money path. Unplug the mouse and try to book a table or a room using only Tab, Enter, and the arrow keys. If you get stuck, so does a meaningful share of the more than 1 in 4 U.S. adults living with a disability.
- Hotels: check booking content against the reservation rule. Every accessible room type should describe its specific features, not just carry an "accessible" label.
- Get a code-level audit before a plaintiff's firm does one for you. Fixes ordered by a settlement always cost more than fixes you scheduled yourself.
ADA Fail audits hotel and restaurant sites against WCAG 2.2 AA — the benchmark courts, the DOJ, and settlement agreements keep pointing to — using expert human testing, not just a scanner. Request your free accessibility audit and find out what a plaintiff's firm would find, before they go looking.
Frequently asked questions
Does the ADA apply to a restaurant website that doesn't sell anything online?
In most courts, yes. Websites connected to a physical business are widely treated as covered by ADA Title III, and the information itself — menu, hours, location — is part of what you offer the public. There is no formal federal regulation setting a specific web standard for private businesses, but courts and settlements consistently reference WCAG as the benchmark, and an information-only site with an unreadable menu can still draw a complaint.
Am I liable for a third-party reservation or ordering platform embedded in my site?
Practically speaking, treat it as your problem. Plaintiffs sue the business whose name is on the website, not the software vendor behind the booking widget. Your contract may let you recover from the vendor later, but that doesn't stop the demand letter. Ask vendors for their accessibility documentation before signing, and test the embedded flow on your own pages — with a keyboard and a screen reader — rather than taking the sales pitch on faith.
We just received a demand letter. Should we install a widget and settle?
Don't reach for an overlay: companies get sued every year with one already installed, and it won't change the code-level barriers the complaint describes. The stronger position is a documented remediation plan built on a real audit, which shows opposing counsel you are fixing the actual problem. Our guide to responding to an ADA website demand letter walks through what to do first.