Robles v. Domino's Pizza: The ADA Website Accessibility Case That Changed Everything
Case at a Glance
Robles v. Domino's Pizza is the most cited ADA website accessibility case in American legal history. The Ninth Circuit's 2019 ruling that the Americans with Disabilities Act applies to commercial websites helped trigger a wave of ADA litigation that has reached tens of thousands of businesses. Understanding this case — what happened, what the courts decided, and what it means today — is essential context for any business with a web presence.
Background: Who Is Guillermo Robles?
Guillermo Robles is a blind California resident who uses a screen reader — software that converts text to speech — to navigate the internet. In 2016, Robles attempted to order food through Domino's Pizza's website and mobile app using his screen reader. He was unable to complete his order because the digital interfaces were not compatible with his assistive technology.
Robles had encountered this kind of barrier before. He filed a complaint in the Central District of California alleging that Domino's failure to make its website and app accessible to blind customers violated Title III of the Americans with Disabilities Act, which prohibits discrimination against people with disabilities in "places of public accommodation."
The key legal question: Is a commercial website a "place of public accommodation" under the ADA?
Round 1: The District Court Dismisses the Case (2017)
Judge S. James Otero of the Central District of California dismissed Robles's complaint in 2017. His reasoning: enforcing the ADA against Domino's website would violate due process because the Department of Justice had not issued specific technical standards for website accessibility. Without regulatory guidance on exactly what "accessible" means, Domino's couldn't know what it was required to do.
The DOJ had, in fact, been in the process of issuing website accessibility regulations for years — but kept delaying. The Obama administration advanced proposed rulemaking that the Trump administration then abandoned in 2017. This regulatory void was the hook Domino's used in its defense.
Domino's core argument
The DOJ has not issued specific technical regulations for website accessibility. Without clear regulatory standards, enforcing the ADA against a website's technical implementation violates due process. We cannot be held liable for failing to meet standards that don't officially exist.
Round 2: The Ninth Circuit Reverses (January 2019)
On January 15, 2019, a three-judge Ninth Circuit panel reversed the district court's dismissal. The ruling, written by Judge John Owens, addressed both of Domino's arguments directly.
On whether the ADA applies to websites
The court held that ADA Title III applies to websites and apps that have a "nexus" — a close connection — to a physical place of public accommodation. Domino's operates physical restaurants (places of public accommodation). Its website and app are integrally connected to those restaurants: customers use them to place pickup and delivery orders from Domino's physical locations. Therefore, the ADA applies.
Key Quote from the Ninth Circuit Opinion
"The ADA applies to the services of a place of public accommodation, not services in a place of public accommodation... The website and app are... avenues that Domino's customers use to order pizzas for pick-up at a Domino's physical location or for delivery from a Domino's physical location."
On the due process argument
The court rejected Domino's due process argument. The fact that the DOJ hadn't issued specific technical regulations for websites doesn't mean Domino's was unaware that inaccessible websites could violate the ADA. WCAG guidelines — developed by the W3C and widely adopted as the industry standard — gave Domino's sufficient notice of what accessibility requires. The ADA's general nondiscrimination mandate applied regardless of specific regulatory implementation details.
Round 3: The Supreme Court Declines to Intervene (October 2019)
Domino's petitioned the United States Supreme Court for a writ of certiorari — asking the Supreme Court to take the case and potentially resolve the circuit split over whether the ADA applies to websites. The Supreme Court denied the petition on October 7, 2019, without comment.
The denial meant the Ninth Circuit ruling stood as binding precedent in the Ninth Circuit (covering California, Oregon, Washington, Nevada, Arizona, and other western states). The broader question of whether non-physical-nexus websites must comply with the ADA remained unsettled in other circuits.
The Supreme Court's refusal to hear the case was widely interpreted as a signal that the Court was not inclined to narrow ADA website obligations — and the explosion in ADA website lawsuits in the years following confirmed that signal.
Full Case Timeline
Guillermo Robles files a complaint in the Central District of California, alleging Domino's website and app are inaccessible to blind users in violation of ADA Title III.
Judge S. James Otero dismisses the case, ruling that applying the ADA to Domino's website would violate due process because the DOJ hadn't issued specific technical regulations for websites.
A three-judge Ninth Circuit panel reverses the dismissal. The court rules the ADA applies to Domino's website and app because they have a nexus to a physical place of public accommodation, and that the DOJ's failure to issue technical standards doesn't excuse non-compliance.
Domino's petitions the Supreme Court for certiorari. The Supreme Court denies the petition without comment, allowing the Ninth Circuit ruling to stand. The case becomes binding precedent in the Ninth Circuit.
The case is remanded to the district court for trial on the merits. COVID-19-related delays push proceedings. Depositions and discovery proceed.
Robles and Domino's reach a settlement on undisclosed terms. By this point, Domino's had already spent years and millions in legal fees litigating a case that a proactive accessibility investment could have prevented.
The Case's Impact on ADA Website Litigation
Robles v. Domino's is the case that plaintiff attorneys and accessibility advocates cite most often in ADA website lawsuits. Its impact has been substantial:
ADA website lawsuits surged
Federal ADA Title III website lawsuits climbed from roughly 2,258 in 2018 to more than 4,600 in 2023. While many factors drove this increase, the Ninth Circuit ruling and the Supreme Court's refusal to hear Domino's appeal removed a key legal defense that businesses had relied on.
WCAG became the de facto standard
The Ninth Circuit noted that WCAG guidelines gave businesses sufficient notice of accessibility requirements. This reasoning accelerated courts' adoption of WCAG 2.1 AA as the benchmark for ADA website compliance — even without formal DOJ regulation under Title III.
The 'nexus' theory spread beyond the Ninth Circuit
Other circuits had already applied various versions of the nexus theory before Robles. The high-profile nature of the Domino's case — and the Supreme Court's refusal to limit it — made courts in other circuits more confident in applying the ADA to websites connected to physical businesses.
Overlays won't save you
Domino's eventually installed an accessibility overlay widget. It didn't. Accessibility overlays have been the subject of their own ADA lawsuits and FTC action, and courts have consistently rejected overlay widgets as evidence of genuine ADA compliance.
What Made Domino's Website Inaccessible?
The complaint alleged that Domino's website and app contained numerous barriers for users relying on screen readers. Common issues in cases like this include:
- Interactive elements (buttons, form fields) without accessible names — screen readers couldn't identify what they did
- Custom UI components (dropdown menus, interactive pizza builder) that didn't expose keyboard navigation or ARIA attributes
- Images without meaningful alt text
- Error messages that weren't programmatically associated with form fields (screen readers couldn't connect the error to the problem field)
- Focus management issues that left keyboard users lost after completing an action
All of these are detectable — and fixable — with standard WCAG 2.1 AA testing. A professional accessibility audit in 2016 would have identified and provided remediation guidance for each of these issues. The cost of that audit and remediation would have been a small fraction of the multi-year litigation costs.
Lesson for businesses
The Domino's case illustrates that accessibility lawsuits are preventable. An automated accessibility scan — costing as little as $29/month — would have identified Domino's most egregious barriers years before Robles filed suit. Fix the issues before they become a lawsuit.
The Current Legal Landscape (2026)
ADA website accessibility law has evolved significantly since the Ninth Circuit's 2019 Domino's ruling:
DOJ Title II Rule (2024)
The DOJ issued a final rule in April 2024 explicitly requiring state and local government websites and mobile apps to conform to WCAG 2.1 AA. Large entities had until April 2026; small entities have until April 2027. This is the most significant federal rulemaking on web accessibility since the ADA was enacted.
Private business Title III
Despite years of rulemaking activity, the DOJ has not issued specific technical regulations for private business websites under Title III. Courts continue to apply the WCAG 2.1 AA standard as the practical benchmark, consistent with the Domino's ruling.
Circuit split remains
Courts are still divided on whether websites without physical-location nexus must comply with the ADA. The Eleventh Circuit (Florida) has taken a narrower view, requiring nexus to a physical location. Other circuits are broader. If your business operates across multiple states, consult an ADA attorney about your specific circuit's precedent.
Serial plaintiffs and demand letters
The plaintiff ecosystem has matured. Plaintiff attorneys use automated scanning tools to identify non-compliant websites at scale and send demand letters. Most result in settlements of $5,000–$25,000 for small businesses. A documented accessibility program is the most effective defense.
What Businesses Should Do Now
Step 1.Run an accessibility audit on your website now
Start with automated scanning to understand your current WCAG 2.1 AA compliance baseline. Tools like RatedWithAI, WAVE, or axe DevTools can identify issues immediately. Fix what you find — especially the high-severity issues affecting screen reader users (missing alt text, unlabeled form fields, keyboard traps).
Step 2.Keep remediation records
Document your accessibility program: when you scanned, what issues were found, when they were fixed. Courts look favorably on defendants who show good-faith remediation effort. A documented compliance history is your strongest defense if you receive a demand letter.
Step 3.Don't use accessibility overlays as your only strategy
Domino's eventually installed an overlay. It didn't protect them. Overlays modify the DOM on the client side but don't fix underlying source code issues. Courts and regulators have rejected overlays as sufficient ADA compliance.
Step 4.Post an Accessibility Statement
An accessibility statement on your site (explaining your commitment to WCAG 2.1 AA, listing known limitations, and providing contact info for accessibility support) demonstrates good faith and often satisfies plaintiff attorneys looking for easy targets.
Step 5.Consult an ADA attorney if your legal risk is high
If you operate in a high-risk industry (healthcare, financial services, e-commerce, hospitality) or your site has significant user-facing functionality, a consultation with an ADA Title III specialist can help you prioritize and document your compliance program.
Check your site now
Don't wait for a demand letter. RatedWithAI scans your entire site for WCAG 2.1 AA violations using the same axe-core engine professional accessibility auditors rely on — starting at $29/month.
Start free accessibility scan →Frequently Asked Questions
What was the Robles v. Domino's Pizza case about?
Guillermo Robles, a blind man, sued Domino's Pizza in 2016 after he was unable to order pizza through the Domino's website and mobile app using his screen reader. He alleged that Domino's failure to make its digital properties accessible violated the Americans with Disabilities Act (ADA). The case became a landmark in ADA law because Domino's argued — unsuccessfully — that the ADA's Title III public accommodation requirements don't apply to websites.
What did the Ninth Circuit decide in Robles v. Domino's?
In January 2019, the Ninth Circuit Court of Appeals ruled that the ADA does apply to Domino's website and app. The court held that ADA Title III covers websites and mobile apps that have a 'nexus' to a physical place of public accommodation — like Domino's restaurants. The court rejected Domino's argument that enforcing the ADA against its website violated due process because the DOJ hadn't issued specific technical standards.
How did Robles v. Domino's Pizza end?
After the Ninth Circuit ruling in 2019, Domino's petitioned the Supreme Court to hear the case. In October 2019, the Supreme Court declined to take the case (denied certiorari), allowing the Ninth Circuit ruling to stand. The case was then remanded back to the district court for trial. Domino's and Robles ultimately settled the case in 2022 on undisclosed terms. By that point, the case had already established precedent that fundamentally changed how businesses view ADA website compliance.
Does the ADA apply to all websites?
Courts are split on this question. The Ninth Circuit's ruling in Robles v. Domino's applies to websites of businesses with a 'nexus' to a physical location (restaurants, retailers, hotels). Other circuits have applied broader interpretations. The First, Second, and Seventh Circuits have ruled that even 'pure-play' online businesses (no physical locations) must comply with the ADA. A handful of courts have taken a narrower view. In practice, most businesses treat their websites as covered by the ADA, and the DOJ's 2024 Title II rule for government websites has reinforced WCAG 2.1 AA as the de facto standard.
What is WCAG and why is it relevant to ADA compliance?
WCAG (Web Content Accessibility Guidelines) is a set of technical standards developed by the W3C that defines what makes a website accessible to users with disabilities. Courts have not mandated a specific technical standard for ADA compliance, but WCAG 2.1 Level AA has become the practical benchmark used by courts, the DOJ, and consent decrees. The DOJ's 2024 Title II rule for state/local governments explicitly requires WCAG 2.1 AA. For private businesses under Title III, demonstrating WCAG 2.1 AA conformance is the strongest evidence of good-faith ADA compliance.
Could Domino's have avoided the lawsuit?
Yes. A basic WCAG 2.1 audit would have identified that the Domino's website and app were not usable with screen readers — a failure to meet basic WCAG Success Criteria 4.1.2 (Name, Role, Value) and others. Accessibility remediation at the time would have cost far less than years of federal litigation, the Supreme Court petition, and eventual settlement. The case is a textbook example of the cost-benefit argument for proactive accessibility: remediation before a lawsuit is almost always cheaper than defense after one.