Robles v. Domino's Pizza

Guillermo Robles is blind. He uses JAWS on his laptop and VoiceOver on his iPhone. He was unable to order through the website in July 2015, July and September 2016, and February 2017, and through the app in July 2016 and June 2019. In September 2016 he sued under Title III of the Americans with Disabilities Act and California's Unruh Civil Rights Act.

His requested relief included an injunction requiring Domino's to conform its website and app to the Web Content Accessibility Guidelines 2.0, statutory damages under Californian law, and fees, expenses, interest and costs. Domino's did not resolve the case early. It litigated the question of whether the ADA applied to its website at all, lost in the Ninth Circuit, asked the Supreme Court to take the case, was refused, lost again on the website claims in the district court, and settled on confidential terms in June 2022.

The published Ninth Circuit opinion is an important federal appellate authority for the proposition that a website and app can fall within Title III when they connect customers to the goods and services of a physical public accommodation. The public record does not disclose Domino's litigation spend, remediation cost, legal-fee resolution or settlement amount.

The complaint first recited a sixteen-item list of barriers commonly encountered on inaccessible sites and apps. It then identified the defects Robles allegedly encountered more specifically: on the website, graphics without text alternatives, empty links, redundant adjacent links and linked images without text alternatives; in the iOS app, buttons that were not clearly labelled as Apple's accessibility guidance required, along with missing text alternatives, inaccessible forms and image maps, and inadequate prompting and labelling. Robles alleged that the barriers prevented him from completing the ordering flow with his screen readers.

Several expressly alleged defects map to Level A success criteria in WCAG 2.2. That mapping is an editorial comparison, not a criterion-by-criterion finding made by the court. Missing attributes and accessible names are often detectable with automated tools, but automation cannot determine every failure or whether the ordering journey works for a screen-reader user.

Marked points are the moments where the dispute could have ended and did not.

Five arguments, made across three courts. Understanding why four of them failed is the practical value of this case, because they recur in website-accessibility litigation and commentary.

Six points where a different operational or litigation choice could have shortened the dispute. The public record does not disclose what any alternative would have cost.

The court record is only part of the story. A Hacker News discussion posted after the Supreme Court denial attracted extensive debate, and the public arguments were often different from Domino's due-process argument in court.

Developers argued about whether the duty should exist at all

Hacker News records 591 descendants for the discussion. That metadata includes deleted or unavailable items, so it should not be read as 591 surviving substantive comments. The observations below are qualitative, not a frequency analysis.

Participants repeatedly raised telephone ordering, the absence of a government technical regulation, implementation cost, litigation incentives and the practical limits of automated testing. Those comments show the range of public reaction; they do not establish how common any position was outside that discussion.

At least five surviving comments were posted by one participant who identified as blind. He described web accessibility worsening as frameworks proliferated, rejected separate accessible versions because they tend to fall out of sync, and described accessibility reports and a submitted code change being ignored. This is evidence of one participant's experience, not a representative survey of blind users.

Blind users had already documented the app breaking

A useful independent record of what Domino's was like to use was not made by either party. It sits on AppleVis, a community site run by and for blind Apple users, where the app has a page with comments running from 2012 to 2023.

In September and November 2012, and again in March 2014, blind users praised it. One described the pizza builder working properly, including putting a topping on one half of the pizza, the exact interaction the litigation was later about. Another praised its support for braille displays. In October 2014 the same community reported it breaking: payment fields could no longer be reached by swiping, the order tracker stopped working, and buttons lost their labels. By July 2023 other users reported it working again.

Robles filed in September 2016, after the reported regression. The AppleVis posts independently document that some blind users encountered app barriers before the lawsuit, but they do not test Robles's device, version or individual experience. The court later denied summary judgment on the app claims because its current accessibility remained a disputed fact.

Disability organisations answered the no-standard argument

Fourteen disability organisations had backed Robles at the Ninth Circuit. After the denial, the American Council of the Blind answered the no-standard argument on its merits rather than in general terms: accessibility guidelines have existed for decades, and the latitude they leave a business is a benefit to that business rather than a defect. That is the same answer the Ninth Circuit gave when it said flexibility in the standard was a feature rather than a bug.

Robles's own counsel called the certiorari denial the right call on every level, and framed the underlying proposition as one nobody actually disputes: that blind people need access to websites and apps to take part in ordinary life. That framing is worth noticing, because it is precisely the proposition large parts of the public discussion went on to dispute.

Blind organisations backed the case and attacked the machinery around it

This position is more nuanced than a simple choice between supporting all such litigation and opposing accessibility enforcement.

In the same month that certiorari was denied, the National Federation of the Blind published an article in its member magazine attacking high-volume accessibility litigation. Lawyers were picking a category of business and filing near-identical complaints in bulk, some of the resulting suits were close to meritless, and small businesses were settling for a few thousand dollars without fixing anything. It warned that bad cases make bad law, and told members to decline invitations to serve as named plaintiffs in such campaigns. A resolution adopted that year condemned mass filings and confidential cash settlements, and called for public settlement agreements with specific remediation commitments instead.

At that same convention, the disability rights lawyer Eve Hill, whose firm later helped take this very case to judgment, told an audience of blind people that some blind people and some lawyers treat inaccessible websites as a business opportunity rather than a civil rights problem. Her distinction is the one worth borrowing: the problem is not the number of lawsuits but their quality, and whether the lawyer bringing them can actually litigate. She defended the Domino's case in the same breath.

The documented position was therefore more specific than blanket support for or opposition to litigation: these organisations supported the Domino's case while criticising high-volume practices that could produce payments without remediation.

Practitioners were harder on both sides than the coverage was

The disability rights lawyer Lainey Feingold, who published a response to the public reaction a week after the denial, spent more of it deflating the result than celebrating it. She also addressed a recurring objection, and it is worth stating plainly because it is a matter of law rather than opinion. Title III of the ADA provides no damages to private plaintiffs at all. The remedy is an injunction, plus legal fees to a prevailing party, which is the ordinary enforcement mechanism across American civil rights statutes. The $4,000 in this case came from a Californian state statute, not the ADA.

Criticism of the plaintiffs' bar came from inside the profession too. Karl Groves, an accessibility consultant and court-qualified expert, has argued that mass demand-letter campaigns actively damage the cause: they crowd out collaboration, and they invite judges to treat genuine claims as opportunism. He has advocated collaborative approaches as an alternative. The Domino's record does not show that the parties used a structured-negotiation process before suit.

A critique of the nexus approach

Writing in 2019, developer Ben Myers mapped the disagreement between the circuits and warned that resting the duty on a physical connection could end up harming the accessible web rather than advancing it, because it leaves the business that exists only online with the weakest obligation. The pandemic sharpened the point: when venues close, the website is not an adjunct to the service, it is the service.

The later ruling received less attention

Public discussion peaked around the Supreme Court's denial of review, even though that event did not decide the merits.

The October 2019 event was a denial of certiorari. It decided nothing. It produced no opinion, set no precedent, and did not even tell you which way the court leaned. The adjudication that resolved the website merits was the June 2021 summary judgment; the remaining app claims ended through settlement and dismissal in June 2022.

The sources reviewed for this article show substantially more public discussion of the 2019 denial than of the 2021 summary-judgment order. That helps explain why some later summaries incorrectly say the Supreme Court ruled on the merits, that Domino's was fined, or that the court specifically ordered Level AA.

What the record says about the plaintiff

The sources reviewed for this article did not reveal a public interview with Robles; the public statements attributed to his side came from his lawyers. Domino's told the Supreme Court that he had filed at least fourteen similar lawsuits, a defence characterization rather than a finding made by the Court. In this case, the district court found the website was not fully accessible in 2021. Domino's 2020 expert did not concede every historical defect, while AppleVis posts separately documented an app regression before Robles filed.

This case is described inaccurately in a great deal of published commentary, including by vendors selling accessibility products. The differences matter if you are relying on it to brief a board. Eleven claims circulate widely enough to be worth answering directly, each set here against what the filings and the judgment actually say.

Domino's told the Supreme Court that leaving the decision undisturbed would turn a flood of litigation into a tsunami. The filing record does not support the case being the cause. The largest year-over-year increase in the cited federal series occurred in 2018, after the Justice Department withdrew its web accessibility rulemaking in December 2017; that timing does not establish causation.

What has changed since the case closed

Three developments since 2022 bear on the argument this case started, and two of them cut against the plaintiffs' bar rather than for it.

In February 2026 the Justice Department filed a statement of interest opposing a proposed class settlement in a website accessibility case, objecting that the injunctive relief set out no concrete steps, that monitoring was optional, and that $2.52 million in fees was disproportionate to what class members received. It recorded that the same counsel had filed substantially the same lawsuit more than 500 times between 2019 and 2023, mostly resolving in undisclosed individual settlements, and said it opposed using a civil claim principally to enrich class counsel on the backs of disabled people. That is the federal government making, in court, the criticism the National Federation of the Blind made in its member magazine in 2019.

Second, filings by people representing themselves rose sharply in 2025, which practitioners attribute to general-purpose AI tools making a complaint easy to draft. Third, Missouri has now responded: Missouri enacted a safe harbour operative from 28 August 2026. It creates a rebuttable presumption concerning allegedly abusive litigation when a defendant takes substantial good-faith steps to correct a noticed violation within ninety days; it does not replace the substantive federal accessibility duty.

None of this disturbs the holding. It does mean the honest summary of 2026 is not that enforcement is uncontested, but that Robles's nexus holding remains binding in the Ninth Circuit while the machinery around it is under pressure from the courts, the regulator and disability organisations alike.

Did any of it make websites better?

WebAIM's 2021 survey of the top million home pages found the Food and Drink category improving from an average of 66.1 automatically detected errors in 2020 to 46.8 in 2021. Its authors said increased accessibility litigation may have contributed to the change.

This is an observational category-level comparison. It does not establish that litigation caused the decline, that Domino's was among the measured sites that improved, or that a blind customer could complete an order. Automated home-page error counts and end-to-end usability are different forms of evidence.

What to take from it

• The nexus argument is settled in the Ninth Circuit. If your website connects customers to a physical location, expect it to be covered.
• The absence of a federal technical rule did not erase the duty. The Ninth Circuit held that Domino's had fair notice of its ADA obligation and declined to wait for the Justice Department to issue a technical standard.
• An alternative channel must be measured. The line failed on the facts here because Robles waited more than forty-five minutes on each of two calls. Comparable timing, privacy, independence and access to the same offers should be tested rather than assumed.
• Several allegations mapped to Level A criteria. Missing text alternatives and accessible names can sometimes be detected automatically, but their quality and the usability of a complete journey require manual review.
• Your own expert's findings may narrow a defence. Domino's expert completed ordinary website and app orders in 2020, but found the website was not fully accessible and could not schedule a future website order.
• Accessibility is a maintenance property, not a project. Blind users praised the app in 2012 and reported an October 2014 version broken; the app was part of the complaint filed in 2016.

Court holdings and procedural facts are drawn from the complaint, orders and dockets below. Later policy, filing and community claims are attributed to their own sources. Where the public record is silent, particularly on costs and the confidential settlement, this page does not estimate.

Primary

• Original complaint, Document 1 (1 September 2016)
• District court dismissal (20 March 2017)
• Ninth Circuit opinion, 913 F.3d 898 (15 January 2019)
• Domino's petition for certiorari, No. 18-1539
• Supreme Court docket, No. 18-1539
• District court order granting summary judgment (23 June 2021)
• Joint notice of settlement (5 November 2021)
• Full district court docket
• June 2022 settlement update and public joint statement
• Domino's accessibility policy text, checked 2 September 2026

Government and filing data

• Justice Department fact sheet on the Title II web and app rule
• Justice Department statement on the Fashion Nova class settlement (2 February 2026)
• Missouri SB 907 enacted text, including the 90-day safe-harbour provision
• Seyfarth Shaw federal website-accessibility filing series, 2017–2025
• EcomBack first-half 2025 filing and law-firm dataset
• Seyfarth Shaw on the 2025 rise in pro se filings and its AI attribution

Commentary and community

• Seyfarth Shaw on the 2021 ruling
• Lainey Feingold answering the public reaction
• AppleVis, blind users on the Domino's app, 2012 to 2023
• Braille Monitor on drive-by accessibility lawsuits (October 2019)
• Karl Groves on drive-by demand letters
• WebAIM Million 2021, on litigation and the food and drink sector
• Hacker News discussion and its 591-descendant metadata, 8 October 2019
• Surviving comments by the self-identified blind participant: 1, 2, 3, 4, and 5
• Archived August 2019 thread from which the unsupported $38,000 claim spread
• Ben Myers on the nexus test and the circuit split
• American Council of the Blind on the cert denial
• American Bar Association overview of the circuit disagreement

Nothing on this page is legal advice. Community comments are used as attributed examples of public reaction, not as representative survey evidence. The circuit graphic is an editorial summary and distinguishes square website holdings from positions commonly inferred from broader public-accommodation precedent.