Skip to content
wcagc
←Back to blog
ADArestaurantsWCAGPDF

ADA compliance for restaurant websites and ordering

What the ADA asks of a restaurant site: menus, online ordering, reservations, and who answers when a third party runs the checkout.

P

Pavel Charkasau

ADA compliance for a restaurant website means a customer who cannot see the screen, or cannot use a mouse, can still read the menu and place an order. The statute lists "a restaurant, bar, or other establishment serving food or drink" among covered public accommodations (42 U.S.C. § 12181(7)(B)), and in Robles v. Domino's Pizza the Ninth Circuit held that the alleged inaccessibility of the website and app "impedes access to the goods and services of its physical pizza franchises" (Ninth Circuit, 15 January 2019). The Supreme Court declined to review that ruling in October 2019 (SCOTUSblog, No. 18-1539).

What none of that gives you is a checklist. The Justice Department says its reading of the ADA covers services offered on the web, then says in the same guidance that it "does not have a regulation setting out detailed standards" for private businesses (ADA.gov). So the working target is WCAG 2.2 Level AA, applied to the parts customers actually touch: the menu, the ordering flow, the reservation form, and the hours and location page.

Does the ADA really apply to a restaurant's website?

In the Ninth Circuit, yes, and the reasoning is worth reading because it is narrower than the headlines suggest. The Domino's panel leaned on the connection between the digital ordering path and the physical stores. Customers used the website and app "to locate a nearby Domino's restaurant and order pizzas for at-home delivery or in-store pickup," and the court called that nexus "critical to our analysis." It also said the ADA applies to the services of a public accommodation, not only services in one, which is why a site accessed from a customer's sofa still counts.

Two points from the same opinion get misquoted a lot. Domino's argued that being sued without a published federal web standard violated due process; the court held the statute was not impermissibly vague and the company had fair notice. And the plaintiff was not asking the court to impose WCAG 2.0 as a legal rule. The panel called compliance with WCAG 2.0 "a possible equitable remedy," which is a different thing from a regulation. Our ADA overview covers the case law in more detail.

A restaurant with no dining room is the genuinely unsettled case. Delivery-only kitchens and app-first brands have no premises for a nexus test to attach to, and the federal circuits split on whether a purely online business is a place of public accommodation at all. I would not build a plan on winning that argument.

Which parts of a restaurant site get complained about?

The menu first, then the ordering flow. Reservation widgets come third. Those are also the pages that take money, which is not a coincidence.

WebAIM's February 2026 report scanned 21,921 home pages in its Food & Drink category and found an average of 57.4 detected errors per page, 2.3% above the million-page average (WebAIM Million). Across the whole million, low contrast text appeared on 83.9% of home pages, missing image alt text on 53.1%, and missing form input labels on 51%. Read that list against a restaurant page and it maps almost item for item: pale gray prices on a cream background, a hero shot of the dining room with no alt text, and a "Table for how many?" field whose label is a placeholder that vanishes when you type.

The ordering flow adds failures a home-page scan never sees. A few that show up repeatedly:

  • Modifier dialogs that trap keyboard focus, so a screen-reader user picks the bun and cannot get back out to the cart.
  • Quantity steppers built from bare <div> elements with a click handler, which never reach the tab order.
  • An "Add to order" button labeled only with a plus icon, announced as "button" and nothing else.
  • Time-slot pickers that fail 2.5.8 Target Size (Minimum), the WCAG 2.2 criterion requiring pointer targets of at least 24 by 24 CSS pixels (W3C).

Are PDF menus an accessibility problem?

Usually, yes. A menu exported from a design tool is a picture of text: no reading order, no tagged headings, nothing for a screen reader to announce except the filename. The Title III regulations require a public accommodation to furnish appropriate auxiliary aids and services for effective communication, and the examples for people who are blind or have low vision explicitly include "accessible electronic and information technology" (28 CFR § 36.303).

If I could change one thing about restaurant websites, it would be this. Delete the PDF and put the menu in HTML. It costs about a morning, and it fixes the phone-screen problem in the same move. Google can finally read your dish names too. Where a PDF has to exist because the print shop needs one, keep it as the download and make the HTML version canonical. You can check an existing file with our PDF accessibility checker, and we have a walkthrough of how to make a PDF accessible.

Who is responsible when ordering runs on a third-party platform?

You are, alongside the vendor. This is the part restaurant operators are most often surprised by, and the statute is unusually direct about it. Discrimination under Title III includes denying someone the opportunity to benefit from your goods and services "directly, or through contractual, licensing, or other arrangements" (42 U.S.C. § 12182(b)(1)(A)(i)).

Handing checkout to a delivery marketplace or a reservation widget does not move the obligation off your site. In practice that means three things worth doing before the contract renews:

  1. Ask the vendor for a current accessibility conformance report and read the "Supports" rows skeptically. Nobody audits that document before it reaches you.
  2. Test the embedded flow on your own domain rather than the vendor's demo. Embeds behave differently inside your CSS.
  3. Put a phone alternative on the page and staff it. That does not replace fixing the flow, and it helps the customer who is stuck tonight.

For a chain taking online orders from EU customers, a second set of rules reaches the same checkout, since e-commerce services fall inside the European Accessibility Act. Our EAA overview covers that scope question.

Which WCAG version should a restaurant target?

WCAG 2.2 Level AA. W3C states that content conforming to WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0 (W3C Recommendation, 12 December 2024), so one target satisfies the versions named in older settlements and in federal procurement rules. If you want the longer answer on why no US regulation names a version for private businesses, we wrote it up in does the ADA require WCAG.

Three criteria added in WCAG 2.2 land directly on ordering:

  • 3.3.7 Redundant Entry (Level A). Information the customer already entered is pre-populated or made available. Asking for the delivery address again at the payment step fails it.
  • 3.3.8 Accessible Authentication (Minimum), Level AA. No step of signing in may require a cognitive function test. Blocking paste in the one-time-code field is the usual way to fail.
  • 2.4.11 Focus Not Obscured (Minimum), Level AA. A focused component must not be entirely hidden by author content. The sticky "Your order: $42.50" bar is the repeat offender.

What should a restaurant actually do first?

Scan the ordering path, not the home page. Start at the menu, add an item with modifiers, reach the payment screen, and record what breaks. A home-page-only scan will hand you a tidy report about your hero image while the checkout stays broken, which is the failure mode we wrote about in why homepage scans miss risk.

Then fix in this order: contrast on menu prices, labels on every form field, keyboard operability through the cart, and alt text on anything carrying information rather than decoration. Contrast you can settle in an afternoon with our contrast checker.

Be honest about what tooling covers. Deque's study of more than 2,000 audits put automated detection at about 57% of issues by volume (Deque); counted by success criteria instead, the figure lands closer to 30%. Either way, full conformance needs human review. Our scanner will find the unlabeled "Add to order" button. It will not tell you whether a list of 14 sandwich modifiers makes any sense when it is read aloud one option at a time. Somebody has to order lunch with a screen reader to learn that, and it is the single most useful hour a restaurant team can spend.

FAQ

Does a small independent restaurant have to comply with the ADA?

Yes. Title III applies to places of public accommodation regardless of size, and the statute names restaurants directly (42 U.S.C. § 12181(7)(B)). There is no small-business exemption for websites, though what counts as a reasonable fix scales with the business.

Is a PDF menu enough to meet the ADA?

Not on its own. Most restaurant PDFs are untagged images of text that a screen reader cannot read, and Title III regulations call for auxiliary aids that achieve effective communication (28 CFR § 36.303). An HTML menu is the reliable fix; a tagged, tested PDF alongside it is fine.

Am I liable if my ordering system belongs to a third party?

Your obligation stays with you. Title III covers discrimination "directly, or through contractual, licensing, or other arrangements" (42 U.S.C. § 12182(b)(1)(A)(i)), so a vendor-run checkout on your site is still your customer's experience of your restaurant.

Which WCAG level do restaurant websites need?

Level AA, at WCAG 2.2. No US regulation names a version for private businesses (ADA.gov), but AA is the level used in settlements and in the Justice Department's public-sector rule, and 2.2 conformance also covers 2.1 and 2.0 (W3C).

How many accessibility issues can a scanner find by itself?

Roughly 30% to 57%, depending on whether you count individual defects or success criteria (Deque). The remainder needs manual testing with a keyboard and a screen reader, which is why an accessibility statement documents effort rather than certifying an outcome.

Run a free scan of your menu and ordering pages to see the exact selectors that fail, then decide what to fix first: scan your site.

Written by Pavel Charkasau, founder of wcagc.com. I read the Ninth Circuit opinion and the Title III regulations so the guidance here matches what the courts and DOJ actually published.

Last updated: September 10, 2026

Sources