The Robles v. Domino’s decision changed how businesses, courts, and web teams think about accessibility by making one practical point impossible to ignore: if a website or app is tightly connected to a company’s physical locations, digital barriers can trigger the same legal risks as barriers at the front door. In plain terms, “public accommodation” refers to a business that serves the public, such as restaurants, hotels, retailers, banks, medical offices, and entertainment venues. For decades, that term was applied most visibly to physical spaces under the Americans with Disabilities Act. Robles pushed the conversation into the digital environment, where customers now browse menus, place orders, book appointments, refill prescriptions, and manage accounts.
I have worked with organizations responding to accessibility demand letters, remediation projects, and settlement timelines, and one pattern repeats across industries: leadership often assumes the website is a marketing asset, while courts increasingly examine it as an access point to goods and services. That distinction matters. When a blind user cannot complete an order with a screen reader, or a keyboard-only user cannot navigate a checkout flow, the issue is not merely technical inconvenience. It can be framed as denial of equal access.
This article explains why Robles v. Domino’s became a landmark precedent, how it influences state and local lawsuits, and why this subtopic now sits at the center of legal and technological strategy. It also serves as a hub for related articles on demand letters, state disability statutes, municipal enforcement trends, settlement structures, mobile app claims, and remediation governance. The most important takeaway is straightforward: digital accessibility is no longer an optional compliance project. It is a core operational requirement for any business that offers services to the public through connected digital channels.
What Robles v. Domino’s Actually Held
Robles v. Domino’s Pizza, LLC arose after Guillermo Robles, a blind plaintiff, alleged that Domino’s website and mobile app were not compatible with his screen reader, preventing him from ordering customized pizzas and using promotional discounts. The Ninth Circuit held in 2019 that Title III of the ADA applied because the alleged inaccessibility of the website and app impeded access to the goods and services of Domino’s physical pizza franchises, which are places of public accommodation. The U.S. Supreme Court later declined to review the case, leaving the Ninth Circuit ruling in place and giving it outsized practical influence.
The decision did not say every website in America is automatically a public accommodation under federal law. That is an important nuance. Instead, it confirmed that when digital tools act as gateways to a covered business, inaccessible design can violate the ADA. Courts and litigants often describe this as the “nexus” approach. If the website or app is integrated with in-store pickup, loyalty accounts, booking systems, coupons, prescriptions, or customer service tied to physical locations, the legal argument becomes much stronger. In practice, many plaintiffs’ firms built their case strategies around that reasoning.
For businesses, Robles matters because it moved accessibility debates away from abstract policy questions and into operational facts. Can a user complete the same task online that a sighted or mouse-using customer can complete? Can they review product information, select options, authenticate, pay, and receive confirmation without assistance? Those are the questions courts, experts, and settlement negotiators now ask first.
Why Websites Are Treated Like Access Points to Public Accommodations
A modern customer journey rarely begins at the storefront. It begins with search, maps, online menus, appointment forms, payment portals, or account dashboards. That shift makes websites and apps functionally similar to entrances, service counters, and printed materials. If a restaurant requires online ordering for delivery discounts, or a clinic pushes intake forms through a patient portal, digital access becomes part of the service itself.
That is why plaintiffs increasingly argue that inaccessible sites create the same exclusion the ADA was designed to prevent. A blind customer blocked by unlabeled buttons on a restaurant website is not meaningfully different from a wheelchair user blocked by a step at the entrance. The medium differs, but the consequence is similar: unequal access to a public-facing business transaction.
Courts have split on whether standalone websites are independently covered under federal law, but state and local lawsuits have expanded pressure well beyond that question. California’s Unruh Civil Rights Act, New York State and New York City human rights laws, Massachusetts discrimination claims, and other state-level theories often give plaintiffs additional paths. Even where federal doctrine is unsettled, state statutes can increase exposure through statutory damages, fee-shifting, and more plaintiff-friendly pleading standards.
From a compliance perspective, this is why companies with brick-and-mortar operations should assume their websites are legally significant points of access. If the site helps customers locate stores, order products, book services, join rewards programs, or communicate with staff, it is woven into the public accommodation analysis whether the business planned for that or not.
How State and Local Lawsuits Expand Risk Beyond Federal ADA Claims
State and local lawsuits are the real accelerant in digital accessibility litigation. Federal ADA claims often seek injunctive relief and attorneys’ fees, but state law can add statutory damages or broader anti-discrimination language. California is the clearest example. Plaintiffs commonly pair ADA claims with the Unruh Act, which allows minimum statutory damages per violation in many circumstances. That changes settlement economics immediately. A complaint that might have been treated as a technical dispute becomes a measurable financial risk.
New York provides another major venue. Plaintiffs have relied on the New York State Human Rights Law and the New York City Human Rights Law in cases involving websites, apps, and online reservation systems. Because New York City’s law is interpreted broadly, businesses operating there often face heightened scrutiny even when their headquarters are elsewhere. Local presence, targeted marketing, or service availability can be enough to invite claims.
Municipal and state enforcement priorities also vary. Some jurisdictions place stronger emphasis on disability access in consumer transactions, housing interfaces, education platforms, transportation systems, or government contractors. For private businesses, that means accessibility risk is not uniform across the country. A retailer with stores in Los Angeles, San Francisco, New York City, Boston, and Miami may face very different litigation patterns depending on venue, plaintiff bar activity, and judicial precedent.
| Jurisdiction | Common Legal Hook | Why It Matters |
|---|---|---|
| California | ADA plus Unruh Civil Rights Act | Statutory damages can increase settlement pressure quickly |
| New York | ADA plus state and city human rights laws | Broad anti-discrimination standards support frequent filings |
| Massachusetts | State public accommodation theories | Claims may proceed even when federal coverage arguments are disputed |
| Florida | ADA-focused filings in active federal districts | Venue trends and repeat plaintiff activity shape defense costs |
As a hub page, this section connects to deeper analysis on California website accessibility lawsuits, New York digital access claims, venue selection, serial litigation, and the difference between private suits and government enforcement. The practical lesson is simple: businesses do not face one accessibility regime. They face overlapping federal, state, and local systems that reward early remediation and punish delay.
The Technical Standard Courts and Settlements Usually Expect
Although the ADA does not codify a single technical rule for private websites, the benchmark used most often in consent decrees, settlement agreements, procurement requirements, and expert audits is the Web Content Accessibility Guidelines, usually WCAG 2.1 Level AA and increasingly WCAG 2.2 Level AA. In my experience, once outside counsel, consultants, and insurers are in the room, the conversation turns to WCAG almost immediately because it offers a recognized, testable framework.
WCAG is organized around four principles: content must be perceivable, operable, understandable, and robust. That translates into concrete requirements such as text alternatives for meaningful images, keyboard accessibility, sufficient color contrast, visible focus indicators, form labels, error identification, resizable text, semantic headings, and compatibility with assistive technologies. Mobile apps raise parallel issues, including screen reader labels in iOS VoiceOver and Android TalkBack, touch target size, orientation, and gesture alternatives.
Businesses should understand a hard truth here: installing an overlay widget rarely resolves the underlying problems that produce lawsuits. Plaintiffs’ experts test source code, component behavior, ARIA usage, focus order, modal dialogs, PDF structure, and dynamic content updates. If a checkout button is unlabeled or a date picker traps keyboard focus, an overlay does not cure the defect. Sustainable remediation requires design system fixes, content governance, QA workflows, and regression testing during releases.
This hub links outward to detailed guides on WCAG levels, accessibility audits, VPAT documentation, screen reader testing, and accessible design systems. The legal issue begins in court, but the durable solution lives in engineering, product management, procurement, and content operations.
What Triggers a Lawsuit and How Businesses Usually Respond
Most website accessibility cases begin with a failed user task. A customer cannot add an item to cart, redeem a coupon, submit an application, reserve a room, or access account information. The legal filing then converts that failure into claims of unequal treatment, deterrence, and ongoing harm. Common triggers include missing alt text on core images, inaccessible navigation menus, CAPTCHA barriers, empty links, unlabeled forms, auto-advancing carousels, inaccessible PDFs, and checkout flows that break under keyboard navigation.
Before a complaint arrives, many companies receive a demand letter. The strongest responses happen when the business can show a current audit, a remediation roadmap, named internal owners, and documented testing by qualified specialists and disabled users. The weakest responses rely on vague promises like “we are working on accessibility” without dates, standards, or evidence. Plaintiffs’ counsel sees that ambiguity as leverage.
An effective response plan typically includes a litigation hold, privilege-sensitive technical review through counsel, preservation of code and release records, triage of severe blockers, and a communications plan for executives, support teams, and developers. If the company settles, the agreement may require deadlines, recurring audits, training, third-party monitoring, policy adoption, and accessibility contact channels. Those obligations can last years, which is why prevention is cheaper than reactive compliance.
Companies often underestimate how quickly small defects compound. A mislabeled login field may block account access; inaccessible product filters may block discovery; a broken payment confirmation may undermine trust and create abandonment. Legally, each barrier supports the broader narrative that the digital service is not equally available.
Building a Defensible Accessibility Program Across Locations and Platforms
The most effective accessibility programs treat websites, mobile apps, kiosks, PDFs, email templates, and third-party integrations as one service ecosystem. That is especially important for multi-location businesses, franchises, universities, healthcare systems, and retailers with local landing pages. If one part of the journey is accessible and another is not, the user still loses access to the underlying service.
A defensible program starts with executive ownership and a written policy tied to recognized standards. Next comes an inventory of digital assets, including microsites, booking engines, embedded widgets, loyalty portals, and downloadable forms. Then the organization needs baseline audits, prioritized remediation by user impact, procurement controls for vendors, training for designers and developers, and periodic manual testing by people who use assistive technology daily.
In practice, the organizations that improve fastest integrate accessibility into sprint planning and release gates. They add automated scans with tools such as axe DevTools, WAVE, Lighthouse, or Pa11y, but they do not confuse automation with full compliance. Automated checks catch only a portion of barriers. Manual testing is indispensable for reading order, context changes, focus management, error recovery, and task completion.
For state and local lawsuit risk, documentation matters almost as much as code. If challenged, a business should be able to show when it audited, what standard it used, which issues were fixed, what remains in progress, and how users can report barriers. That record will not eliminate liability, but it often improves settlement posture and demonstrates good-faith effort.
Robles v. Domino’s remains the clearest warning that digital channels are not legally separate from the businesses they serve. When a website or app is the path to ordering, booking, applying, paying, or communicating, courts and plaintiffs will treat accessibility barriers as barriers to a public accommodation. State and local lawsuits make that reality even sharper by layering additional statutes, broader remedies, and venue-specific pressure on top of federal claims.
For businesses, the lesson is not to wait for perfect legal uniformity. The smarter move is to act on the existing pattern: courts recognize digital access as integral to customer access, plaintiffs file where state and city laws strengthen their leverage, and settlements routinely anchor obligations to WCAG-based remediation. That means accessibility belongs in governance, design, engineering, procurement, and customer experience, not just in legal review after a complaint arrives.
As the hub for state and local lawsuits within the broader Legal and Technological Frontiers topic, this page points to the next level of detail: California and New York claim trends, demand letter response strategy, mobile app litigation, vendor liability, audit protocols, and settlement mechanics. Use it as your starting point, then review your own digital customer journey with the same rigor you would apply to a physical site inspection. If the public can reach your business online, make sure they can actually use it.
Frequently Asked Questions
What did Robles v. Domino’s actually decide about websites and apps?
Robles v. Domino’s is widely viewed as a landmark accessibility case because it reinforced a practical legal principle: when a website or mobile app is closely tied to the goods and services of a brick-and-mortar business, barriers in that digital experience can create liability under the Americans with Disabilities Act. The case arose because a blind customer alleged he could not effectively use Domino’s website and app with screen-reader technology to order customized pizzas from the company’s physical restaurants. The Ninth Circuit did not say that every website in America is automatically covered in exactly the same way. What it did say, however, was critically important for businesses: the ADA applies when digital barriers impede access to the goods and services of a place of public accommodation.
That is why the decision became such a major turning point. It shifted the conversation away from the outdated idea that accessibility obligations stop at the front door. If a customer uses your website or app to find locations, book appointments, place orders, refill prescriptions, buy tickets, access loyalty benefits, or otherwise interact with your in-person business, then the digital experience is not separate from the public accommodation. It is part of how customers access it. In that sense, Robles made clear that accessibility is not just a technical best practice or a customer-service issue. It can be a legal compliance issue tied directly to how a business serves the public.
What does “public accommodation” mean, and why does that matter for my website?
Under the ADA, a public accommodation is generally a private business that offers goods or services to the public. Common examples include restaurants, hotels, retail stores, banks, healthcare providers, theaters, gyms, schools, and many other customer-facing establishments. Traditionally, people thought of public accommodation in physical terms: entrances, ramps, restrooms, counters, parking spaces, and similar features. But as commerce increasingly moved online, courts began grappling with a simple question: if the public interacts with a business through a website or app, can digital barriers deny equal access in the same way a staircase can?
Robles helped answer that question in a very practical way. If your website or app functions as a gateway to your physical business, it matters whether people with disabilities can use it. For example, if someone cannot navigate your online menu, schedule a medical visit, complete a purchase, reserve a hotel room, or access account information because your site is incompatible with assistive technology, that person may effectively be shut out of the same services offered to everyone else. That is why the concept of public accommodation now has major digital implications. Even if the statute was written before modern websites existed, courts increasingly look at whether your digital tools are part of the customer journey to your real-world goods and services. If they are, accessibility is no longer optional in any meaningful sense.
Does this precedent mean every business website must be ADA compliant?
The careful answer is that Robles does not create a one-size-fits-all rule declaring every website in every jurisdiction covered under identical standards. Website accessibility law still depends on factors such as the type of business, the court jurisdiction, whether the business has physical locations, and how closely the digital platform is connected to the company’s services. That said, the broad compliance takeaway for most businesses is straightforward: if you serve the public and your website or app is an important part of how customers access your offerings, you should assume accessibility matters legally as well as operationally.
For businesses with physical locations, the risk is especially clear. A restaurant that takes online orders, a retailer that offers in-store pickup, a hotel that processes reservations, or a medical office that uses patient portals all rely on digital channels that directly affect access to their services. Even businesses that operate primarily online are facing growing legal and regulatory pressure around accessibility, although the exact legal theories can vary. In practice, the smartest approach is not to focus on technical loopholes or narrow interpretations of case law. It is to treat accessibility as a baseline requirement. Following recognized standards such as WCAG, testing with assistive technologies, fixing barriers proactively, and building accessibility into design and development workflows are far more effective than waiting to see whether your particular business model becomes the subject of a complaint.
What kinds of website barriers can create the same legal risk as physical barriers?
Digital barriers can be just as exclusionary as physical ones when they block access to core business functions. Common examples include images without meaningful alternative text, navigation that cannot be used with a keyboard, buttons or forms that screen readers cannot identify properly, videos without captions, low-contrast text, error messages that are unclear or not announced to assistive technology, and checkout flows that become unusable for people with visual, motor, cognitive, or hearing disabilities. If a customer cannot complete an essential task because of one of these issues, the legal and practical effect may be the same as arriving at a store with no accessible entrance.
What makes these barriers particularly risky is that they often appear in the exact places where businesses interact most directly with the public. Think about online ordering, appointment scheduling, account creation, payment, location finders, digital coupons, loyalty programs, application forms, and customer-support tools. If those experiences are inaccessible, the business may be denying equal access to the goods and services it offers. Courts and plaintiffs do not usually focus on whether a website looks modern or whether a company had good intentions. They focus on whether people with disabilities could actually use the service. That is why accessibility audits must go beyond surface-level scans. Businesses need manual testing, real-user perspective, and remediation focused on the journeys that matter most to customers.
What should businesses do now to reduce ADA website risk after Robles v. Domino’s?
The most important step is to stop treating accessibility as a one-time legal checkbox and start treating it as an ongoing business discipline. Begin with a comprehensive accessibility audit of your website and mobile app, ideally using both automated tools and manual review by experienced testers. Automated scans can catch some issues quickly, but they do not provide a complete picture. Manual testing is essential for identifying real usability barriers involving keyboard navigation, screen readers, focus order, form behavior, modal windows, multimedia, and transaction flows. Once you know where the problems are, prioritize fixes on the pages and functions most closely tied to customer access, such as ordering, booking, payment, login, and contact features.
Beyond remediation, businesses should build accessibility into every stage of their digital process. That means adopting a recognized standard such as WCAG 2.1 or 2.2 AA as an internal benchmark, training designers and developers, involving accessibility in procurement decisions, reviewing third-party integrations, and creating a sustainable governance process so new barriers are not introduced with every update. It also helps to publish an accessibility statement, provide a clear method for users to report problems, and respond quickly when issues are raised. Legally, no strategy can guarantee you will never face a claim. But from both a risk-management and customer-experience standpoint, a documented, proactive accessibility program puts your organization in a much stronger position. Robles showed businesses that digital access is part of public access. The companies that act on that lesson are far better prepared than those that continue to treat accessibility as someone else’s problem.
