If your restaurant uses QR code menus, a website menu, or any digital ordering interface, that content is increasingly treated as a "place of public accommodation" under the Americans with Disabilities Act (ADA). Courts and plaintiffs' firms have targeted restaurants with inaccessible digital experiences—and settlements often run from $75,000 to $400,000.

At TableSide, we build websites and QR menu systems for independent restaurants. We design every digital menu to meet WCAG 2.1 Level AA so you can focus on hospitality instead of legal exposure. In this post, we'll cover what the law expects, what "accessible" means for menus, and practical steps you can take.

Why Digital Menus Are Under the Microscope

The ADA requires businesses that serve the public to make their goods and services accessible to people with disabilities. For years, that meant physical access—ramps, door width, restrooms. Today, courts and the Department of Justice increasingly apply the same standard to digital access: websites, apps, and QR-code experiences that customers use to view menus, order, or pay.

If a guest who is blind or low-vision cannot use your QR menu because it's a PDF with no structure, or a guest who needs large text cannot resize it, your digital menu may be considered discriminatory. Lawsuits and demand letters have surged—especially against restaurants and hospitality brands.

What "Accessible" Means: WCAG 2.1 Level AA in Plain English

The widely accepted standard for digital accessibility is the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. For a restaurant digital menu, that typically means:

  • Text resizing: Users must be able to enlarge text up to 200% without losing content or function. No tiny 8pt PDFs.
  • Color contrast: Text and interactive elements must have sufficient contrast against the background (at least 4.5:1 for normal text).
  • Screen reader support: The menu must be structured so assistive technology can read headings, links, and buttons in a logical order.
  • Keyboard navigation: All actions (category tabs, item selection, search) must be doable with a keyboard, not just a touchscreen.
  • Touch targets: Buttons and tappable areas should be at least 44×44 pixels so people with motor limitations can use them reliably.

At TableSide, our QR menus are built as mobile-optimized web experiences—not PDFs—with semantic HTML, ARIA where needed, and high-contrast, resizable text. We treat accessibility as a requirement from day one, not an afterthought.

Common Mistakes That Increase Your Risk

  • PDF-only menus: PDFs are often not structured for screen readers and don't reflow well when users zoom. Prefer real web pages.
  • Low contrast or tiny font: Decorative choices that look "cool" can make the menu unusable for low-vision guests.
  • No alternative to QR: Some guests cannot or prefer not to use a smartphone. Offering a small number of physical menus or staff-assisted options (hybrid approach) reduces friction and risk.

What You Can Do Right Now

  1. Choose a menu platform that explicitly targets WCAG 2.1 AA (like TableSide) and ask for documentation or a brief accessibility statement.
  2. Keep a modest stock of physical menus for guests who want or need them.
  3. Train staff to offer help: "Would you like me to walk you through scanning, or would you prefer a printed menu?"

Reducing legal risk isn't just about checking a box—it's about making your dining experience inclusive. Accessible design benefits older guests, anyone in bright sunlight or low light, and anyone who prefers large text. That's more people in seats and fewer headaches down the road.