Robles v. Domino's Pizza

One further fact, which comes from outside the litigation, changes how the failure should be read. Blind users had rated the Domino's iOS app highly in 2012 and 2013, praising the pizza builder and its braille support, and then documented it breaking in October 2014. The company had built something that worked and then shipped releases that broke it. That is covered below, and it is the difference between a company that never thought about blind customers and one that stopped checking.

The last row is the one most commentary gets wrong. In its Supreme Court petition Domino's argued at length that accessibility is costly, citing a grocery chain's $250,000 estimate, bank estimates reaching $3 million per website and a publishers' floor of $100,000. But those were other companies' numbers, offered as a reason for the Court to take the case. At the Ninth Circuit stage, on its own website, Domino's did not argue that fixing it would be an undue burden or would fundamentally alter its business, which are the actual statutory defences. The court noted that absence expressly.

At the Supreme Court the argument shifted again. Rather than defend the website in isolation, Domino's proposed that Title III should be satisfied by the combined means of access a business offers, so that no single channel need be accessible on its own provided the whole adds up to equal enjoyment. Had it been accepted, a working phone line would have excused an unusable website. The Court did not take the case, so the theory was never tested.

Publicly, the company held one line throughout. Its statement on the day certiorari was denied said it had already developed an accessible website and app, and pressed for national rulemaking to eliminate what it called a tsunami of website accessibility litigation. That word was Domino's own, taken from its petition rather than from the business groups supporting it.

Two things stand out. The argument the company actually made, that it lacked fair notice of a specific technical standard, was of almost no interest to working developers. They argued instead about whether the obligation should exist, which was never the legal question.

The second is who was speaking. In a thread of 591 comments about blind people, three comments came from someone identifying as blind. One made the point that accessibility has been getting worse as web frameworks proliferate. Elsewhere a commenter argued that if blind customers genuinely wanted to use these sites they would simply write in and ask for fixes. A disabled developer in the same thread described doing exactly that, submitting a code change to a large platform, and being ignored. The Domino's record answers it too: there was no accessibility contact route on the site until after the lawsuit was filed.

Blind users had already documented the app breaking

The most useful 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 late 2012 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, inside that window. This is independent corroboration, from people with no stake in the case, that the product genuinely regressed. It also explains why the app claims were never resolved: the court refused summary judgment on the app because whether it was accessible by then was genuinely disputed, and a moving target is hard to enjoin.

Blind organisations backed the case and attacked the machinery around it

This is the part that almost never survives into secondary coverage, and it is the most interesting position in the whole debate, because it is neither of the two on offer.

In the same month that certiorari was denied, the National Federation of the Blind, the largest blind consumer organisation in the United States, 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.

So the accurate summary is not that blind people supported the lawsuit or opposed it. Their organisations supported this case and criticised the machinery around it, on the grounds that the machinery was producing cash rather than accessible websites.

Practitioners were harder on both sides than the coverage was

Writing after the 2021 judgment, the accessibility consultant Sheri Byrne-Haber criticised Domino's for continuing to spend on litigation, but also faulted the plaintiff's team on evidence handling, including failing to preserve the original phone and running expert testing on a different platform from the one the plaintiff actually used.

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 corrected the most popular objection of all, 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. His preferred alternative is structured negotiation, which has produced dozens of accessibility agreements with major institutions without anyone filing suit. That is the option Domino's never took and the one this case never tested.

The most striking thing about the practitioner response, though, is how little of it there was. A page-by-page crawl of the personal sites of many of the field's best-known technical writers, together with the archives of a major community project and a leading accessibility research group, found no mention of this case at all.

The ruling that decided the case was never discussed

Here is the most useful observation about the public record, and it explains why so much of what people believe about this case is wrong.

The moment everybody argued about, in October 2019, 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 moment that actually resolved the dispute was the summary judgment of June 2021.

That second event produced no significant discussion anywhere. The community formed its beliefs during a procedural non-event reported under misleading headlines, and was not present for the correction. That is why, years later, people still say the Supreme Court ruled against Domino's, that the company was fined, and that Level AA was ordered, when none of those things happened.

The one voice missing throughout is the plaintiff's

Across six years of coverage, Guillermo Robles does not appear to have spoken publicly once. Every quotation attributed to his side comes from his lawyers. Court records indicate he was a party to roughly sixteen federal accessibility suits filed in the same district over about a year, which is the pattern that draws the serial-plaintiff criticism. That context belongs in any fair account. So does the fact that the criticism directed at this case was aimed almost entirely at the litigation environment rather than at him, and that the barriers he complained of were real, were conceded by Domino's own expert, and had been independently documented by other blind users two years before he filed.

Certiorari was denied in October 2019, and that year was flat against 2018. Counts that include state courts run considerably higher, so do not mix the two series. Filing is also heavily concentrated: in the first half of 2025, sixteen firms accounted for more than 90 percent of cases and the firm that represented Robles was the single largest filer. Our accessibility lawsuit tracker keeps the current numbers.

One part of Domino's complaint also turned out to be durable. There is still no federal technical regulation for private business. The rule the Justice Department published in 2024, adopting WCAG 2.1 Level AA, binds state and local government under Title II only.

Did any of it make websites better?

There is one piece of evidence, and it is worth knowing because it is measured rather than asserted. WebAIM's annual survey of the top million home pages found the food and drink sector improving markedly in the years after this litigation wave, from around 66 detected errors per page to around 47, and its authors attributed part of that improvement to the increase in accessibility litigation in the sector.

Treat that carefully. It measures automatically detectable errors on home pages, which is precisely the class of defect at issue in this case, and precisely not the same thing as a blind customer being able to order a pizza. The honest reading is that litigation demonstrably reduced the machine-detectable failures and tells us nothing directly about whether the experience became usable. That gap is the whole argument between compliance and accessibility, and it is why an audit that stops at the scanner is not an audit.