ADA Website Compliance in 2026: The Ecommerce Guide

Key takeaways

• There is no federal regulation spelling out technical requirements for private-sector websites. Courts apply ADA Title III to ecommerce sites anyway, treating them as “places of public accommodation.”
• The standard everything converges on is WCAG. Level AA is the target courts, settlements, and regulators reference, and building to WCAG 2.2 AA satisfies the US, EU, and UK regimes in one pass.
• The risk is concentrated on online stores: over 5,000 ADA digital accessibility lawsuits were filed in the US in 2025, and 70% targeted ecommerce.
• The DOJ’s 2024 web rule adopts WCAG 2.1 AA, but it applies to state and local governments (Title II), not private stores. Treating it as an ecommerce mandate is a common error.
• Accessibility overlays do not deliver compliance. The FTC fined accessiBe $1,000,000 over its compliance claims, and more than 1,400 of 2025’s lawsuits hit companies already running a widget.

ADA website compliance is the question of whether your website meets the accessibility requirements of the Americans with Disabilities Act. For an online store, the question stopped being theoretical years ago: ecommerce was the target of 70% of the ADA digital accessibility lawsuits filed in the US in 2025.¹

The confusing part is that no federal rulebook tells a private business what its website must do. The law gets enforced anyway, through thousands of lawsuits a year that nearly all point at the same technical standard.

This guide covers the legal side (what the ADA actually says, the Domino’s case, the state and EU laws), the standard itself (WCAG compliance, and what A, AA, and AAA mean), and the practical side: what making an online store compliant involves, and why the shortcut products fail.

Why you can trust us

We have been in the Shopify space for over four years and built Fudge, an AI store builder and editor with a 4.9 rating on the Shopify App Store. Accessibility remediation in native storefront code is part of what Fudge does, so we work with these standards daily rather than summarizing them from a distance.

Every legal and statistical claim in this guide is checked against primary sources: ada.gov, the Federal Register, court records, ftc.gov, official EU texts, and the published UsableNet and WebAIM datasets. Where the law is unsettled, we say so. This is general information, not legal advice.

---

Is there actually a law that says your website must be accessible?

Yes and no, and the “no” part is why this area confuses store owners.

The Americans with Disabilities Act was signed in 1990, before the commercial web existed. Title III of the ADA prohibits discrimination on the basis of disability in the full and equal enjoyment of the goods and services of any “place of public accommodation”, a term the statute illustrates with physical examples like shops, restaurants, and hotels.

What the ADA does not contain is a web chapter. The Department of Justice started writing web accessibility regulations for businesses in 2010, then formally withdrew the rulemaking in December 2017 without ever issuing a rule.²

The DOJ’s position since then, restated in its March 2022 guidance, is that the ADA’s requirements apply to the websites of businesses open to the public, but that businesses have “flexibility” in how they comply. No technical standard is named as mandatory for the private sector.³

The practical result: there is no federal checklist for private websites, but there is liability. The requirements are defined case by case, by courts and settlements.

Do courts agree that the ADA covers websites?

Mostly yes, but through two different theories, and the split matters if you sell online only.

• Some circuits, led by the First, hold that a “public accommodation” does not have to be a physical place. Under that reading, a web-only business can be covered by Title III on its own.
• Others, including the Third, Sixth, and Ninth Circuits, tie public accommodations to physical locations. In those circuits, a website is covered when it has a nexus to a physical place, such as a store, restaurant, or showroom the site connects customers to.

The Supreme Court has not resolved the split. In practice, the disagreement helps plaintiffs more than defendants: they choose where to file, and the highest-volume venues accept website cases readily. No ecommerce business should plan around being out of scope.

What the Domino’s case settled

The closest thing to a landmark is Robles v. Domino’s Pizza. A blind customer using screen-reading software could not order a customized pizza through the Domino’s website or app, and sued under Title III and California’s Unruh Act.

In January 2019, the Ninth Circuit held that the ADA applies to the Domino’s website and app, because they connect customers to the goods and services of its physical restaurants.⁴ Domino’s argued that being held liable without a DOJ regulation violated due process. The court rejected that: the ADA has required effective communication with disabled customers since 1990, so the company had fair notice, regulation or not.

The Supreme Court declined to hear the appeal in October 2019, leaving the ruling in place.⁴ The message every plaintiff firm took from it: the absence of a federal web regulation is not a defense.

What about the DOJ’s 2024 web rule?

In April 2024 the DOJ did finally publish a web accessibility regulation, and it is regularly misquoted, so precision matters here.

The 2024 rule falls under Title II of the ADA, which covers state and local governments. It requires their web content and mobile apps to meet WCAG 2.1 Level AA, with compliance dates that the DOJ extended by one year in April 2026, to April 2027 for larger governments and April 2028 for smaller ones.⁵

It does not apply to private businesses. Your store is governed by Title III, where no such rule exists. What the rule did change for everyone is the benchmark: it is the first time the DOJ wrote a specific WCAG version into an ADA regulation, and WCAG 2.1 AA is also the standard most commonly requested in private litigation.¹

How likely is an ADA website lawsuit for an online store in 2026?

More likely than most other legal risks a store carries, and the volume is aimed squarely at ecommerce.

UsableNet, which has tracked this litigation for over seven years, reviewed more than 5,000 ADA digital accessibility lawsuits filed in federal and state courts in 2025. Federal courts accounted for 3,195 cases, with another 1,919 in New York and California state courts.¹

The industry breakdown is lopsided:

Industry	Share of 2025 suits
Ecommerce	70%
Food service	21%
Healthcare	2%
Everything else	7%

A few more findings from the 2025 data are worth internalizing:¹

• You can be sued where you sell, not where you sit. New York leads the country, and its courts accept cases against businesses whose sites are merely accessible to New York residents. Florida returned as a high-volume venue in 2025, while California filings dropped.
• One lawsuit is rarely the end. 1,427 suits, 45% of the federal total, targeted companies that had already been sued before. Partial fixes invite the sequel.
• Big brands are not skipped, they are preferred. 36% of the top 500 ecommerce retailers received at least one accessibility lawsuit in 2025.
• A small plaintiff bar drives it. A concentrated group of firms files most of these cases with a deliberate, repeatable playbook.

Filed cases are only part of the picture. Many claims arrive as private demand letters and settle before anything reaches a docket, which means the public numbers understate the real volume.

The state-law layer: California’s Unruh Act

Federal ADA claims can win injunctions and attorney’s fees, but not damages. State laws add the money, and California’s Unruh Civil Rights Act is the sharpest example.

A 1992 amendment made any ADA violation automatically a violation of the Unruh Act, which carries statutory damages of at least $4,000 per violation plus attorney’s fees.⁶ Because each encounter with a barrier can count separately, the exposure stacks quickly, which is exactly what makes an accessibility demand letter worth settling and worth sending.

New York plaintiffs lean on similar state and city human rights laws. The pattern is the same everywhere: the ADA establishes the duty, and state law prices the failure.

What is WCAG compliance?

If the ADA supplies the legal duty, WCAG supplies the definition of done. The Web Content Accessibility Guidelines are published by the W3C, the standards body behind the web itself, and they are what courts, settlement agreements, and regulators reference when they need to say what “accessible” means.

WCAG is not itself a law. It becomes binding when a law, regulation, or settlement points at it, and by now nearly all of them do: the DOJ’s Title II rule uses WCAG 2.1 AA, the EU’s EN 301 549 standard incorporates WCAG 2.1 AA, and WCAG 2.1 AA is the most commonly requested standard in US litigation.¹

What A, AA, and AAA actually mean

Each WCAG success criterion is assigned one of three levels:

• Level A is the minimum. Failing A criteria means some users are locked out entirely: images with no text alternative, controls that only work with a mouse.
• Level AA is the legal target. Claiming AA conformance means meeting every Level A criterion and every Level AA criterion. This is the level referenced in settlements and regulations.
• Level AAA is the highest tier. It is aspirational, not required by any major regime, and some AAA criteria are impossible for certain content.

When someone says a site “meets WCAG”, the meaningful claim is a version plus a level: WCAG 2.1 AA or WCAG 2.2 AA.

The four POUR principles

WCAG organizes everything under four principles, known by the acronym POUR:

• Perceivable. Users can perceive the content: text alternatives for images, captions for video, text contrast of at least 4.5:1.
• Operable. Users can operate the interface: full keyboard access, visible focus, no keyboard traps.
• Understandable. Content behaves predictably: clear labels, consistent navigation, form errors explained in text.
• Robust. Assistive technology can interpret the markup: semantic HTML, correct names, roles, and states.

For an ecommerce site, the highest-stakes application of all four is the path from product page to completed checkout. A shopper who cannot finish a purchase is both lost revenue and the exact scenario plaintiffs test.

WCAG 2.1 vs 2.2: which version should you target?

WCAG 2.2 became the current W3C Recommendation in October 2023.⁷ It contains everything in 2.1 plus a handful of new criteria, so conforming to 2.2 AA automatically satisfies every rule that references 2.1 AA.

That makes the choice simple: build to WCAG 2.2 AA once and you cover the US settlement standard, the DOJ’s Title II benchmark, the EU requirement, and the UK’s Equality Act expectations in a single body of work. For the criterion-by-criterion breakdown applied to a storefront, see our WCAG 2.2 AA checklist.

Selling into the EU: the European Accessibility Act

US law is no longer the only regime an online store has to think about. The European Accessibility Act (Directive (EU) 2019/882) became applicable on 28 June 2025, and it names ecommerce explicitly as a covered service.⁸

Three things make it relevant to stores far beyond Europe:

1. It reaches non-EU sellers. The trigger is selling to consumers in the EU, not where your business is registered. A US store shipping to EU customers is in scope.
2. It points at the same standard. Conformance runs through EN 301 549, which incorporates WCAG 2.1 AA for web content, and it expects a published accessibility statement.
3. The exemption is narrow. A micro-enterprise providing services is exempt only if it has fewer than 10 employees and annual turnover or balance sheet at or below EUR 2 million. Both conditions must hold.⁸

Penalties are set country by country rather than EU-wide. Our guide to the European Accessibility Act covers scope, exemptions, and enforcement in detail.

How do you make an ecommerce website ADA compliant?

Strip away the legal framing and compliance is an engineering loop with three stages: find the issues, fix them in the code, and keep them fixed. There is no filing, certificate, or badge that makes you compliant. The state of your live site is the whole story.

The good news is that the failures are heavily concentrated. The WebAIM Million, an annual automated analysis of the top one million home pages, found detectable WCAG failures on 95.9% of pages in its February 2026 report, averaging 56.1 errors per page. About 96% of all those errors fall into just six categories:⁹

Failure	Share of home pages affected	Typical storefront cause
Low-contrast text	83.9%	Brand colors used for body or button text
Missing alt text	53.1%	Product and lifestyle images uploaded without alt
Missing form labels	51%	Search, newsletter, and checkout fields
Empty links	46.3%	Icon-only links (cart, social) with no label
Empty buttons	30.6%	Icon-only buttons (menu, close) with no label
Missing page language	13.5%	No lang attribute in the page template

Every one of these is unambiguous, machine-detectable, and fixed by editing the site’s actual markup and styles. That is where the three-stage loop comes in.

Stage 1: Audit

Start with an automated scan using a free tool like axe DevTools, WAVE, or Lighthouse. It will surface most of the six failures above in minutes.

Then do the part machines cannot: automated tools only detect roughly 30 to 40% of WCAG criteria. Navigate from a product page through checkout using only the keyboard, repeat the trip with a screen reader (VoiceOver on Mac, the free NVDA on Windows), and zoom to 200% to check nothing clips. Our store accessibility audit guide walks through the full method, and it transfers to any platform.

Stage 2: Fix it in the code

Durable fixes are changes to the site’s HTML, CSS, and JavaScript: real alt text on images, a programmatic label on every input, accessible names on icon buttons, contrast raised to 4.5:1, visible focus states, a correct lang attribute, and keyboard-operable menus and modals.

This is the step no product can paper over. If the underlying markup is broken, the site is broken for assistive technology, whatever sits on top of it.

Stage 3: Monitor

Accessibility decays. A theme update, a new banner, a seasonal campaign page, or a single image uploaded without alt text can reintroduce failures months after an audit. Re-scan on a schedule and re-test the checkout path after significant changes, so a regression is a ticket rather than a demand letter.

Do accessibility overlays make a website ADA compliant?

No, and 2025 removed any remaining ambiguity about it.

An overlay is a third-party script (accessiBe, UserWay, AudioEye, and similar) that loads on top of your pages and claims to detect and repair accessibility problems automatically. The pitch is one line of code in exchange for compliance. The structural problem is that a script running on top of broken HTML cannot rewrite the source, and automated logic covers only a minority of WCAG criteria.

The record now speaks for itself:

• The FTC fined accessiBe $1,000,000. The order, proposed in January 2025 and finalized that April, bars the company from claiming its widget can make any website WCAG compliant, findings the FTC paired with allegations of deceptively formatted reviews.¹⁰
• Widgets did not slow the lawsuits. More than 1,400 of 2025’s ADA suits were filed against companies that already had an accessibility widget running, over a quarter of the year’s total.¹
• The field rejects them. More than 1,000 accessibility professionals, including WCAG contributors and screen-reader engineers, have signed the Overlay Fact Sheet stating that overlays cannot deliver compliance.¹¹

An overlay is a recurring cost that hides the problem from you while leaving it visible to your customers and to plaintiff firms. We break down how the products work and fail in why accessibility overlays fail.

If your store runs on Shopify

Everything above applies to any ecommerce site. The implementation layer is platform-specific: on Shopify, the fixes live in your theme’s Liquid, CSS, and JavaScript, and the platform’s defaults get you an accessible starting point that your theme, apps, and content then make or break.

Our Shopify ADA compliance guide is the platform-specific version of this article, covering where each fix lives in a theme and which parts Shopify handles for you.

It is also the layer where we can do more than explain. Fudge reads your live theme, surfaces the accessibility failures in your code, and fixes them directly in native Liquid, CSS, and JavaScript. Because the output is real theme code rather than an injected script, it holds up the way a developer’s fix would, with no widget weighing down the page.

Beyond the legal exposure, the fixes are simply good retail. More than 1 in 4 US adults reports a disability.¹² A store that a screen-reader or keyboard user can actually check out of is serving customers your inaccessible competitors turn away.

---

FAQ

Footnotes

1. UsableNet, 2025 Year-End Digital Accessibility Lawsuit Report: more than 5,000 ADA digital accessibility suits reviewed for 2025 (3,195 federal, 1,919 in NY and CA state courts); ecommerce 70% of filings, food service 21%, healthcare 2%; 1,427 suits (45% of federal cases) against previously sued companies; 36% of the top 500 ecommerce retailers sued; monthly counts of suits against widget-equipped sites totaling over 1,400; WCAG 2.1 AA the most commonly requested standard in litigation. usablenet.com. ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶

2. US Department of Justice, Notice of Withdrawal of Four Previously Announced Rulemaking Actions, Federal Register, December 26, 2017, withdrawing the Title III web accessibility rulemaking (RIN 1190-AA61) opened by the July 2010 ANPRM. federalregister.gov. ↩

3. US Department of Justice, Guidance on Web Accessibility and the ADA, March 18, 2022: the ADA applies to web content of businesses open to the public; businesses have flexibility in how they comply; no mandatory technical standard is named for Title III entities. ada.gov/resources/web-guidance. ↩

4. Robles v. Domino’s Pizza, LLC, No. 17-55504 (9th Cir., January 15, 2019): Title III applies to the website and app because they connect customers to physical restaurants; due process challenge rejected. Supreme Court denied certiorari on October 7, 2019 (No. 18-1539). ca9.uscourts.gov, supremecourt.gov. ↩ ↩²

5. US Department of Justice, Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (ADA Title II final rule, published April 2024), adopting WCAG 2.1 AA; compliance dates extended by the interim final rule of April 20, 2026 to April 26, 2027 (population 50,000+) and April 26, 2028 (smaller entities and special districts). ada.gov/resources/2024-03-08-web-rule, federalregister.gov. ↩

6. California Unruh Civil Rights Act, Cal. Civ. Code sections 51(f) and 52(a): a 1992 amendment incorporates ADA violations, with statutory damages of no less than $4,000 per violation plus attorney’s fees. leginfo.legislature.ca.gov. ↩

7. Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, October 2023. w3.org/TR/WCAG22. ↩

8. European Accessibility Act, Directive (EU) 2019/882, applicable from 28 June 2025; e-commerce services in scope; conformance via EN 301 549, which incorporates WCAG 2.1 AA; micro-enterprise services exemption for fewer than 10 employees and turnover or balance sheet at or below EUR 2 million. eur-lex.europa.eu/eli/dir/2019/882/oj. ↩ ↩²

9. WebAIM Million, February 2026 report: 95.9% of the top 1,000,000 home pages had detectable WCAG 2 failures, averaging 56.1 errors per page; six error categories (low-contrast text 83.9%, missing alt text 53.1%, missing form labels 51%, empty links 46.3%, empty buttons 30.6%, missing document language 13.5%) account for 96% of all detected errors. webaim.org/projects/million. ↩

10. FTC order requiring accessiBe to pay $1,000,000 for deceptive claims that its accessWidget could make any website WCAG compliant, proposed January 2025 and approved as final in April 2025; the order bars unsubstantiated compliance claims. ftc.gov. ↩

11. Overlay Fact Sheet, signed by more than 1,000 accessibility professionals. overlayfactsheet.com. ↩

12. CDC, July 2024: more than 1 in 4 US adults (28.7%, about 70 million people) reported having a disability, based on 2022 BRFSS data. cdc.gov. ↩