The Ninth Circuit tied ADA website duties to a physical restaurant

The workload

Robles v. Domino's Pizza turned on ordinary maintenance work a site or app owner either does or skips: making a website and mobile app usable with a screen reader, so a blind customer can order food the same way a sighted customer does. The Ninth Circuit's opinion sets no technical checklist; it holds Domino's had to provide auxiliary aids sufficient for effective communication, the same open-ended ADA standard applied to a physical storefront, applied here to code instead of a ramp.

What the documents show

Verified: the court held the ADA applies to Domino's website and app because they are a means of accessing the goods and services of Domino's physical restaurants, calling that connection a nexus and stating it was critical to the analysis. Verified: the panel expressly declined, in a footnote, to decide whether the ADA covers a website whose inaccessibility does not impede access to a physical location, so the ruling does not resolve online-only coverage. Verified: the court held that Domino's had received fair notice of its ADA duty despite the absence of any Department of Justice regulation naming a technical standard, and that ordering compliance with WCAG 2.0 would be a possible remedy, not a basis for liability itself. The Department of Justice's own guidance, in its current form dated 18 March 2022, states that Title III covers businesses open to the public and that an inaccessible website can limit access to their goods and services, consistent with the reasoning in Robles.

The operating cost

Neither document states a compliance cost; both describe a legal standard, not a price. The practical cost is remedial engineering plus litigation exposure if a complaint is filed, and the opinion does not quantify either. What the ruling does establish is that not knowing which standard applied is not, on its own, a defence once a court is prepared to interpret the statute's existing language.

The stop condition

Editorially: the holding rests specifically on a nexus between an online product and a physical place of public accommodation; it does not extend automatically to a SaaS product with no storefront to connect to, and the court said so itself. A founder operating only online is reading a narrower precedent than the headline claim that the ADA applies to websites suggests, and circuits have not uniformly agreed on how far Title III reaches without that nexus.

• Does the product connect to any physical location or service the way Domino's website connected to its restaurants, or is it purely online?
• Has a WCAG-level accessibility pass actually been done, given that courts have treated it as a workable remedy standard even without a DOJ regulation?
• Which circuit's case law would actually govern a dispute, given that Robles is Ninth Circuit precedent, not a nationwide rule?

Robles is often summarised as a ruling that the ADA applies to websites. The opinion itself is narrower: it applies to a website that functions as a gateway to a physical business, and it states plainly that it is not deciding the harder question of a website with no such gateway.