ADA Title III and web accessibility — a current-data guide for 2026

Title III of the Americans with Disabilities Act says, in a sentence written for shopping malls and movie theatres in 1990, that a “place of public accommodation” must not discriminate on the basis of disability. Three and a half decades later, that sentence governs whether a screen-reader user can finish a checkout flow, book a hotel room, or read a restaurant menu PDF. The doctrinal bridge from the brick-and-mortar text to the commercial web was built case by case between 2006 and 2019, anchored by Robles v. Domino’s Pizza. The volume that flows over that bridge is now substantial: roughly 12,000 federal Title III complaints in 2024, of which approximately 4,300 were website-accessibility cases (Seyfarth Shaw ADA Title III tracker). The Department of Justice’s Title II final rule of April 2024 formalised WCAG 2.1 Level AA as the federal standard for state and local government — and quietly reset the bargaining posture for the parallel Title III docket. This dossier maps the law, the data, and the place the still-pending Title III rulemaking sits in 2026.

01 · What Title III actually says

The operative language is short. 42 U.S.C. §12182(a) provides that “no individual shall be discriminated against on the basis of disability in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation by any person who owns, leases (or leases to), or operates a place of public accommodation.” The implementing regulations at 28 CFR Part 36 list twelve categories of covered entities, from inns and restaurants to “sales or rental establishments” and “service establishments.” The list was drafted in 1990. It does not mention the internet.

The interpretive question that has driven thirty years of litigation is whether the category list is meant to be exclusive — a closed enumeration that captures only the physical places that existed when Congress passed the statute — or whether it is illustrative, meant to apply to any commercial setting that fits the underlying purpose. The Department of Justice has consistently taken the illustrative view. So has the disability-rights bar. Industry has consistently argued the narrower reading. The circuits have split, and the doctrinal split is what the 2024–25 filing data is sitting on top of.

Inside that statutory architecture, Title III matters disproportionately because the entities it regulates — retailers, restaurants, hotels, banks, healthcare providers, educational institutions, entertainment venues — operate the consumer-facing surfaces of the economy. If a Title III obligation reaches a commercial website, it reaches the great majority of the public-facing web. If it does not, the federal-statute floor on commercial web accessibility is essentially Section 504 (which only applies to federal-fund recipients) and state law. That stakes-level reality is why the small doctrinal question — is a website a “place” — has produced more than three thousand reported federal decisions since 2006.

02 · The Robles foundation

The case that anchors the modern Title III web docket is Robles v. Domino’s Pizza, LLC, 913 F.3d 898 (9th Cir. 2019). Guillermo Robles, a blind plaintiff, alleged that he could not order from Domino’s website or its mobile app using his screen reader. The district court dismissed on due-process grounds — that the absence of a DOJ technical standard meant the company could not have known what compliance required. The Ninth Circuit reversed in January 2019, holding that the ADA did apply to the website and app because they were “heavily integrated” with Domino’s physical restaurants and constituted “two of the primary (and heavily advertised) means” by which customers ordered the company’s product.

The legal architecture of the holding is worth pulling apart. The Ninth Circuit did not hold that every website is a place of public accommodation. It held that a website is covered when there is a sufficient nexus to a physical place that itself falls within the Title III category list. The pizza chain’s physical stores were the place of public accommodation; the website was the means by which goods and services from that place were obtained. The court left for another day what happens when a defendant has no physical store at all — the e-commerce-only case.

Domino’s petitioned for certiorari. The Supreme Court denied the petition on 7 October 2019. Robles’s nexus framework has been cited by district courts roughly six hundred times in the years since. The denial of certiorari has had its own effect: by leaving the circuit split unresolved, the Court effectively delegated the question to a doctrinal patchwork that the plaintiffs’ bar has learned to navigate.

The Ninth Circuit did not hold that every website is a place of public accommodation. It held that a website is covered when there is a sufficient nexus to a physical place. That distinction is the entire 2026 doctrinal map.

Two earlier cases provide the older context. Carparts Distribution Center, Inc. v. Automotive Wholesaler’s Association of New England, 37 F.3d 12 (1st Cir. 1994), held in a non-web setting that a place of public accommodation need not be a physical location at all — the First Circuit’s reasoning has since been pulled forward to argue that purely virtual entities can be covered. National Federation of the Blind v. Target Corp., 452 F. Supp. 2d 946 (N.D. Cal. 2006), was one of the earliest federal decisions to apply Title III to a commercial website, on a nexus theory that anticipated Robles’s by thirteen years. The 2008 settlement in Target — including a $6 million class fund and a WCAG-pegged remediation plan — set the template for Title III web settlements that has held, broadly, ever since.

03 · The circuit map in 2026

The current circuit map breaks into three rough postures.

Broad-read circuits. The First Circuit treats places of public accommodation as a functional rather than geographic category. The Second Circuit’s per se rule is unsettled, but its district courts — particularly the Southern and Eastern Districts of New York — have consistently allowed Title III claims against website-only defendants since Andrews v. Blick Art Materials, LLC, 268 F. Supp. 3d 381 (E.D.N.Y. 2017). The Seventh Circuit’s Doe v. Mutual of Omaha line provides similar latitude. Together these are the jurisdictions where pure e-commerce defendants face the highest Title III exposure.

Nexus circuits. The Ninth Circuit’s Robles rule and the Eleventh Circuit’s Gil v. Winn-Dixie Stores trajectory (the 2017 bench trial vacated and remanded in 2021 on mootness grounds, leaving the underlying doctrine unresolved) both require a connection between the digital surface and a physical place of public accommodation. The practical effect is that a website with a physical-store counterpart faces full Title III exposure in these circuits; a pure e-commerce site faces an uncertain doctrinal road.

Unsettled circuits. The Third, Fourth, Fifth, Sixth, Eighth, Tenth, and DC Circuits do not have controlling appellate decisions on the question. District-court practice within each of them varies, with the trend over the last five years moving toward acceptance of website coverage but with meaningful holdouts. The Sixth Circuit’s Gomez v. Trinitas Cellars LLC petition and similar 2024–25 cases will likely shape the next round of appellate doctrine.

For a defendant chosen as a target, the circuit in which the complaint is filed often determines more about the case’s trajectory than the underlying facts. For the plaintiffs’ bar, that fact has produced predictable forum selection — most concretely the concentration in the Southern District of New York and the Central District of California. For a national e-commerce defendant, the doctrinal patchwork means the practical compliance question is whether the website meets some jurisdiction’s broad-read standard, because that is the standard a plaintiff there can plead under.

04 · Filing volumes and the website wave

The federal-court filing data tells a clean story. The Seyfarth Shaw ADA Title III tracker, which has hand-coded every Title III federal-court complaint since 2013, reports the following annual totals: 8,694 (2022), 8,227 (2023), and approximately 12,000 (2024). Inside those totals, the website-accessibility share has climbed from a few hundred a year in the mid-2010s to roughly 2,895 in 2023 and approximately 4,300 in 2024.

The geographic concentration is even sharper than the numerical climb. The Southern District of New York alone is estimated to have hosted more than 3,200 Title III complaints in 2024. Adding the Eastern District of New York brings the New York federal share to roughly 4,500 — close to 38% of the national total. The Central and Northern Districts of California add another 2,800 between them. Outside those four districts, the Southern District of Florida and the District of New Jersey carry most of the remaining volume. Filings beyond those six districts are a long tail.

The website cases are not evenly distributed across industry. The Seyfarth analysis and complementary work by the ADA Title III News & Insights blog identify the most-litigated surfaces: e-commerce checkout flows, restaurant menu PDFs, hotel reservation pages (already covered by 28 CFR §36.302(e)‘s “reservations policy” rule), independent retailers’ Shopify-hosted storefronts, and small-business websites scraped en masse by automated tester tools. The plaintiff cohort in the New York website wave is small — a few dozen named plaintiffs filing through a handful of firms. The defendant cohort is enormous and varies week to week.

05 · The April 2024 Title II rule and its Title III shadow

On 8 April 2024, the Department of Justice published the final rule amending 28 CFR Part 35 to add Subpart H, titled “Web and Mobile Application Accessibility.” The rule sets WCAG 2.1 Level AA as the technical standard for the websites and mobile applications of state and local governments. Compliance dates are staged by entity size: large public entities (population 50,000 and above) had until 24 April 2026; smaller entities and special-district governments had until 26 April 2027. The rule includes a small number of narrow exceptions — archived web content, third-party content the entity does not control, password-protected documents about specific individuals — that the disability-rights bar negotiated down from earlier drafts.

The Title II rule does not, by its terms, apply to Title III defendants. A private retailer is not bound by 28 CFR Part 35. But the rule’s existence has changed the Title III bargaining table in three ways.

First, it removes the longstanding defence argument that the ADA’s web obligations are too vague to enforce. The DOJ’s 1996 letter to Senator Harkin, the 2010 ANPRM, the 2018 withdrawal of that ANPRM, and the gap that followed had all been cited for a decade as evidence that no clear federal standard existed. WCAG 2.1 AA is now in the Code of Federal Regulations. That removes the doctrinal argument that no standard exists — at least for Title II — and significantly weakens the parallel argument when raised in Title III cases.

Second, it produces a single benchmark that settlement agreements can reference. Throughout 2024 and 2025, the great majority of Title III website settlement decrees publicly available cite WCAG 2.1 Level AA as the remediation target, with phase-out periods modelled on the Title II compliance windows. Earlier settlements referenced WCAG 2.0 or 2.1 inconsistently; the post-April-2024 cohort has converged.

Third, it pressures the DOJ to finalise the parallel Title III rule. The Civil Rights Division has been on record since 2022 that a Title III website rulemaking is on the long-term agenda. The Title II rule’s existence — and the awkwardness of a federal standard that applies to a state university but not to a private one across the street — makes the regulatory gap politically conspicuous in a way it was not before.

06 · Where the Title III rulemaking sits

The history of DOJ Title III website rulemaking is short and not flattering. In July 2010 the department published an Advance Notice of Proposed Rulemaking (ANPRM) seeking comment on web-accessibility regulations under both Titles II and III. The ANPRM proposed adopting WCAG 2.0 Level AA as the technical baseline. Public comments ran for a year. The proposed rule that should have followed never came. In late 2017 the department placed the rulemaking on inactive status. In December 2017 it formally withdrew it.

The 2022 Unified Regulatory Agenda re-listed a Title III web rulemaking as a long-term action. The 2023 and 2024 agendas continued the listing. The April 2024 Title II final rule was the result of a parallel proceeding initiated in 2023; the Title III equivalent has not advanced to NPRM stage as of mid-2026. In public statements through 2025 the Civil Rights Division has indicated that the Title III rulemaking is “under active development” and that the Title II rule’s structure is likely to inform the Title III approach. No timeline has been published.

The substantive question that a Title III NPRM will have to resolve is bigger than the Title II rule’s. Title II covered a discrete universe — state and local governments — that the DOJ already had inventory data on. Title III covers, depending on how the rule is drafted, every commercial website operated by a US entity (or any non-US entity targeting US consumers). The compliance-window question, the small-business exception question, the third-party-content question, and the relationship-with-state-law question all become harder in the Title III setting. The plaintiffs’ bar wants a fast NPRM. Industry wants a slow one. The DOJ has not yet committed publicly to either.

A federal standard that applies to a state university but not to a private one across the street makes the regulatory gap politically conspicuous in a way it was not before April 2024.

07 · The defence-side critique

The defence-bar argument against the current pattern is structural and has been pressed by the US Chamber of Commerce, the Restaurant Law Center, and the Retail Litigation Center in amicus filings since at least the 2017 Winn-Dixie appeal. The argument has three components.

The first is the absence of regulatory guidance. Without a Title III final rule, defence counsel argue, defendants cannot reasonably be expected to know what compliance requires; due-process concerns therefore counsel narrow construction of the statute. The April 2024 Title II rule has weakened this argument by establishing that some federal standard now exists, but defence counsel continue to press a version of it.

The second is the standing question. Defence counsel argue that “tester” plaintiffs — those who visit a website only to file a lawsuit, without genuine intent to use the goods or services — should not satisfy Article III’s injury-in-fact requirement. The Supreme Court’s non-decision in Acheson Hotels v. Laufer left the question live; some district courts dismiss tester complaints, others do not.

The third is the fee-shifting structure. Title III’s lack of a damages remedy means the entire economic engine of private enforcement runs on §12205 attorneys’ fees. Defence counsel argue that the structure produces filings that are about fees, not access. The disability-rights bar’s response is that no Title III enforcement scale would exist at all without the fee provision, given the DOJ’s vanishingly small Title III caseload.

08 · 2026 outlook

Four developments will likely shape the rest of the year and the early 2027 docket.

The first is the Title III NPRM. If the DOJ issues a proposed Title III web rule in 2026, the public comment period will likely run six to twelve months, with a final rule unlikely before late 2027 at earliest. The plaintiffs’ bar expects the rule to formalise WCAG 2.1 Level AA and to expand, not contract, the pool of potential defendants. Industry will press hard for small-business exceptions and long compliance windows. The shape of the NPRM, when it comes, will be the largest single policy event in the area since the 1990 statute itself.

The second is appellate clarity on the standing question. A return of the tester-standing issue to the Supreme Court is widely expected after Acheson Hotels’s mootness dismissal. The 2025 term’s petition queue includes several candidate cases. A ruling that constricts tester standing would reduce the filing volume in the broad-read circuits substantially; a ruling that expands it would lock the current pattern in.

The third is the long-pending e-commerce-only question. The Ninth Circuit’s Robles nexus rule, the Eleventh Circuit’s unresolved posture, and the Second Circuit’s district-level acceptance of pure-website defendants together produce a slow-burning circuit split that is ripe for Supreme Court review. A grant of certiorari in a clean e-commerce-only case — one with no physical store at all — would settle the central doctrinal question of the last two decades.

The fourth is the migration of filings from federal to state court, and from heavily-litigated districts to neighbouring ones. The 2024 New York CPLR §3211 amendments and the 2024 California SB-585 reforms have already produced measurable shifts in where complaints are filed. If the Seyfarth federal tracker progressively understates the national volume as cases move to state court, the policy debate that uses its numbers will need a new baseline.

The through line

The Title III web-accessibility landscape in 2026 sits on a single observation: thirty years of statute, twenty years of case law, ten years of pending rulemaking, and one final rule on the sister title in April 2024 have produced a system in which private litigation is the primary federal enforcement mechanism for commercial-web access, the technical standard is WCAG 2.1 Level AA in everything but the actual Title III regulations, and the volume of filings is steadily climbing while the underlying access gap moves much more slowly. The 2026 calendar will tell whether the DOJ closes the regulatory gap, whether the Supreme Court resolves the doctrinal one, and whether either changes the shape of the docket.

For the moment, the practical baseline is straightforward to state and harder to apply. A US commercial entity whose website serves customers is exposed to Title III enforcement risk in at least three circuits regardless of physical footprint, and in the Ninth Circuit if there is any nexus to a physical place of public accommodation. WCAG 2.1 Level AA is the standard the settlement market has converged on; a free WCAG 2.2 scan is the cheapest way to spot the gaps before a demand letter lands. Title III’s lack of a damages remedy means the per-case stakes are limited but the volume is structural. Read more from Disability World on the ADA, on who actually drives Title III enforcement, and on the wider US accessibility-law landscape. To put a Title III posture into practice: the step-by-step WCAG 2.2 compliance playbook walks through audit, remediation and ongoing monitoring; the accessibility monitoring buyer’s guide compares the platforms organisations use to maintain that posture; and the accessibility compliance explainer routes between the regional regimes.