Is Your PDF Menu an ADA Lawsuit Waiting to Happen?

Yes, in practice. Title III of the Americans with Disabilities Act covers restaurants as places of public accommodation, and US courts have repeatedly treated restaurant websites — including their menus — as part of that accommodation. The Department of Justice has stated for years that the ADA applies to the web, and its 2024 rule requiring WCAG 2.1 AA for state and local government websites signals the technical standard courts and plaintiffs reference for private businesses too. Bottom line: if a blind guest cannot read your online menu with a screen reader, your restaurant carries legal risk.

Most restaurant PDF menus are exported from design tools (or are literal scans) with no accessibility structure: no reading order, no text alternatives, tiny fixed text that cannot reflow on a phone, and images of text a screen reader cannot parse. Accessibility reports on web lawsuits consistently list inaccessible PDF menus among the most common complaints against restaurants. An HTML menu — real text, semantic headings, scalable — is fundamentally more accessible than a scanned PDF.

Industry tracking of federal and state filings found roughly 1,368 ADA digital-accessibility lawsuits against restaurants in 2025 — an increase of about 80% over 2024 — making food service the single most-sued industry (about a third of all cases). Most cases are filed by a small group of serial plaintiffs, concentrated in New York, Florida and California, and most settle out of court.

Typical settlements for small businesses run from about $5,000 to $50,000, plus your own legal fees and the cost of remediating the website afterwards — you end up paying for accessibility anyway, plus the settlement, plus the lawyers. That is why accessibility professionals recommend fixing the low-hanging fruit (like the PDF menu) before a demand letter arrives, not after.

No — it is also a market. The CDC estimates about 1 in 4 US adults lives with some disability, including millions with low vision or blindness who use screen readers and text scaling. An accessible menu is readable by those guests, works better for older diners who bump up their font size, loads faster on bad connections, and is better understood by Google and AI assistants. Accessibility and SEO reward the same thing: real, structured text.

IAMenu serves your menu as a real HTML web page — actual text with semantic structure that screen readers can parse, text that scales, and clear allergen icons with text labels — instead of a scanned PDF, which removes the most common menu-related accessibility complaint. Full ADA conformance, however, depends on your whole web presence (your main website, reservation widgets, third-party embeds), so no menu tool can honestly promise blanket "ADA compliance". What IAMenu gives you is the accessible-menu foundation: HTML instead of PDF, structure instead of images of text.

The Web Content Accessibility Guidelines (WCAG) are the international technical standard for web accessibility, published by the W3C. US courts and the DOJ most often reference WCAG 2.1 Level AA as the benchmark (the 2024 DOJ rule for government websites adopts exactly that), and WCAG 2.2 is the current version. For a restaurant, the practical priorities are: real text (not images of text), sufficient color contrast, keyboard navigation, text that scales, and descriptive labels.

Yes. A QR code is just a link; what matters is what it opens. If your QR opens an inaccessible PDF, the problem travels with it. If it opens an accessible HTML menu, the QR becomes an accessibility feature: guests can use their own phone with their own assistive settings (screen reader, magnification, high contrast) instead of struggling with fixed print. Keep a printed menu available too — best practice is offering both.