ADA Website Compliance for Restaurants: Menu, Ordering & Reservation Accessibility

# ADA Website Compliance for Restaurants: Menu, Ordering & Reservation Accessibility

Restaurants are one of the most frequently sued industries under the ADA — and it's not just about wheelchair ramps and parking spaces anymore. If your restaurant has a website (and nearly every one does), you have digital accessibility obligations too.

The good news: most restaurant websites have the same core problems, and they're fixable without a full website rebuild.

This guide covers what restaurant website ADA compliance actually means in practice — with specific attention to the features your customers use most: online menus, reservation systems, and ordering platforms.

---

Why Restaurants Are a Top ADA Lawsuit Target

According to EcomBack's 2025 mid-year report, the food service industry consistently ranks in the top five sectors for federal ADA website lawsuits. Across all industries, 5,114 federal accessibility lawsuits were filed in the first half of 2025 — a 37% year-over-year increase.

Why are restaurants disproportionately targeted?

1. High website traffic from new customers — People with disabilities are often researching a restaurant for the first time before visiting in person. If they can't access your menu or make a reservation online, they can't visit at all.

2. Heavy reliance on PDFs — Restaurant menus are frequently uploaded as scanned PDFs, which are almost universally inaccessible to screen readers.

3. Third-party integrations — Online ordering, reservations, and delivery platforms are often embedded from external providers. If those providers aren't accessible, you may still be liable.

4. Small businesses, smaller legal budgets — 77% of ADA website lawsuits target companies with under $25 million in revenue. Demand letters targeting restaurants are common precisely because smaller operators are less likely to fight back.

---

What "ADA Compliance" Means for Your Restaurant Website

There is no ADA-specific list of website requirements. Instead, the Department of Justice's 2024 rule under Title II points to WCAG 2.1 Level AA as the operative standard. Title III (which covers restaurants) doesn't have the same formal rule yet, but federal courts in multiple circuits have applied the same standard.

In plain terms: your restaurant website must be usable by people who:

• Are blind or have low vision and use screen readers
• Are deaf or hard of hearing
• Have motor disabilities and can't use a mouse
• Have cognitive disabilities and need clear, simple navigation

That translates into specific technical requirements — but for restaurants, a handful of features cause the vast majority of violations.

---

The 4 Biggest Accessibility Problems on Restaurant Websites

1. Inaccessible PDF Menus

This is the single most common restaurant ADA lawsuit trigger.

A scanned PDF of your printed menu is essentially an image — a screen reader can't extract text from it. Even a "native" PDF created from a Word document is often poorly tagged and difficult to navigate with assistive technology.

What to do:

• Convert your menu to an HTML page on your website (styled with your branding — it doesn't have to look plain)
• If you must use a PDF, make it a tagged, accessible PDF with proper reading order and alt text for images
• Never upload a photographed or scanned menu and call it done

Quick test: Open your menu PDF in Adobe Acrobat and run the built-in accessibility checker. If it finds errors — or if you're using a scanned image — start here.

2. Online Reservation Systems That Fail Keyboard Navigation

Reservation widgets from platforms like OpenTable, Resy, or Yelp are embedded iframes. Some of these platforms have decent accessibility; others do not.

Common problems:

• Date pickers that only work with a mouse
• Form fields with no visible labels (screen readers can't identify what to type)
• Error messages that aren't announced to screen readers when a booking fails

What to do:

• Test your reservation widget using only your keyboard (Tab to navigate, Enter/Space to activate). If you get stuck, your users will too.
• Contact your reservation platform and ask for their VPAT (Voluntary Product Accessibility Template) — a document disclosing their accessibility status
• If your current platform is inaccessible and won't provide a fix timeline, that's a business reason to evaluate alternatives

Note: Embedding a third-party widget doesn't remove your liability. Courts have generally held that the website operator bears responsibility for the user experience, even when accessibility barriers originate in a vendor's code.

3. Online Ordering Platforms With Accessibility Gaps

If you offer direct online ordering through your website — via Toast, Square, ChowNow, Slice, or a custom build — the same rules apply.

Critical accessibility failure points in restaurant ordering:

• Product images with no alt text — A screen reader user hears "image" instead of "Margherita Pizza, fresh mozzarella, basil, $14"
• Customization dropdowns that can't be operated by keyboard
• Cart and checkout flows where focus management breaks down (user loses their place after updating a quantity)
• Allergen and dietary information buried in tooltip-only content that's inaccessible to assistive technology

What to do:

• Run your ordering flow through an automated checker like CheckMyADA's free scan — it will catch missing alt text, form labeling issues, and contrast problems
• Walk through the ordering flow yourself using only a keyboard
• Check that all allergen information is available as readable text, not just icons or tooltips

4. Contact Pages and Google Maps Embeds

Your contact page is often the first thing a new customer sees. Common issues:

• Phone numbers presented as images instead of clickable text
• Google Maps embeds with no text alternative for users who can't interact with the map
• Contact forms with unlabeled fields

For Google Maps: the embed itself has some built-in accessibility, but you should always supplement it with a plain-text address that users can copy and paste or use with their navigation app of choice.

---

Restaurant-Specific Accessibility Checklist

Use this to audit the most critical pages on your restaurant site:

Homepage

• [ ] Navigation works with keyboard only (Tab, Enter, Escape)
• [ ] Images have descriptive alt text (food photos should describe the dish, not just say "food")
• [ ] Color contrast meets 4.5:1 ratio for normal text, 3:1 for large text

Menu Page

• [ ] Menu is in HTML format, not a scanned PDF
• [ ] If PDF is used, it is tagged and accessible (run Acrobat's checker)
• [ ] Section headings (Appetizers, Mains, Desserts) use proper H2/H3 tags
• [ ] Prices and dish descriptions are readable text, not images

Reservation Page

• [ ] Reservation widget can be completed using only keyboard
• [ ] Form fields have visible, programmatic labels
• [ ] Date/time picker works with keyboard or has a text alternative
• [ ] Success/error messages are announced to screen readers

Ordering Page (if applicable)

• [ ] All food item images have descriptive alt text
• [ ] Add-to-cart and customization controls work with keyboard
• [ ] Checkout flow maintains focus management throughout
• [ ] Allergen info is available as readable text

Contact Page

• [ ] Address appears as readable text (not just embedded in map)
• [ ] Phone number is a clickable tel: link
• [ ] Contact form fields are labeled
• [ ] reCAPTCHA has an audio alternative

---

What About Third-Party Delivery Apps (DoorDash, Uber Eats, Grubhub)?

If a customer orders from you through DoorDash or Uber Eats, you generally don't control that platform's accessibility — and courts have not held restaurants liable for third-party marketplaces' inaccessibility (yet).

However, your own website's ordering flow — if you have one — is your responsibility. And your website should never redirect users only to a third-party app. Offering an accessible path through your own site is the safest approach.

---

How Much Does It Cost to Fix a Restaurant Website?

Here's a realistic picture:

The math is straightforward. Proactive remediation costs a fraction of reactive legal defense.

---

Frequently Asked Questions

I'm a small restaurant — do the ADA rules really apply to me?

Yes. Title III of the ADA covers "places of public accommodation," which includes restaurants of all sizes. There's no revenue threshold exemption. Demand letters increasingly target small businesses precisely because they're less likely to have legal resources.

My website was built on Squarespace/Wix/WordPress — isn't it their responsibility?

No. You are the website operator. The platform provides the tools, but you're responsible for how your site is configured and what content you upload (including menus). Most major platforms have some accessibility features — but default templates often fall short of WCAG 2.1 AA without customization.

Do I need to fix my Instagram or Yelp page too?

Those platforms are responsible for their own accessibility. Your obligation is your own website. That said, any content you create and post (like a scanned menu image) could still be considered inaccessible if it's also linked from your website.

What if a customer contacts me about an accessibility issue?

Respond promptly and professionally. Offer an alternative way to access the information (e.g., read the menu over the phone, take a reservation by email). Document the interaction. This kind of good-faith response is noted favorably in legal proceedings.

Is there a deadline by which I need to be compliant?

There's no single national deadline for private businesses. But the longer known barriers remain unfixed after you're aware of them, the harder it is to claim good faith if you're sued. The time to act is before you receive a demand letter.

---

Start With a Free Scan

The fastest way to understand your current exposure is to run an automated accessibility scan. It won't catch everything — manual testing is needed for keyboard navigation and screen reader behavior — but it gives you a concrete list of fixable issues in minutes.

Scan your restaurant website at CheckMyADA — no account required.

Then explore /how-it-works to understand what the report covers, and /pricing if you want ongoing monitoring.

For more guides on ADA compliance topics, visit the CheckMyADA blog.