ADA compliance for e-commerce starts from a settled position: the Justice Department has "consistently taken the position that the ADA's requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web" (ADA.gov). Your storefront is part of how the public buys from you, so Title III reaches it. What DOJ has not done is publish a rule naming a WCAG version or a date for private businesses. It says so directly: the Department "does not have a regulation setting out detailed standards," and businesses "have flexibility in how they comply" (ADA.gov).
For a shop, the working answer is to build to WCAG 2.2 Level AA, prove it on the paths people buy through, and keep dated evidence that you maintain it. That last clause is where retail differs from a brochure site. A marketing page with weak contrast irritates someone. A checkout that traps keyboard focus inside a modal ends the order. Filing data reflects the difference: e-commerce accounted for nearly 70% of ADA web accessibility lawsuits filed in 2025, out of more than 5,000 total (UsableNet).
Does the ADA apply to my online store?
For most stores, yes. Title III covers "public accommodations," and DOJ reads that to include what those businesses offer online (ADA.gov). Revenue does not buy an exemption. Of the companies named in 2025 web accessibility filings, 64% reported annual revenue below $25 million (UsableNet). A two-person Shopify store sits under the same statute as a national chain.
One honest caveat: courts have split on whether a business that exists only online, with no physical premises, meets the definition of a public accommodation. That question is unsettled, and I would not build a compliance plan around winning it. Our ADA overview goes through the statute and the case law in more detail.
If you also sell to consumers in the EU, a second and much more specific law applies to the same checkout. The European Accessibility Act names e-commerce as a covered service and points at EN 301 549 for the technical bar. That is a different obligation with its own paperwork, covered in our EAA overview and the EAA e-commerce checklist.
Which WCAG version should an online store target?
WCAG 2.2 Level AA. No version is legally mandated for private US businesses, but WCAG 2.1 AA is the standard that consent decrees and settlements have used for years, and W3C states that content conforming to WCAG 2.2 also conforms to 2.0 and 2.1 (W3C). Aiming at 2.2 covers the version litigation cites and picks up criteria written for exactly the interactions a store has. WCAG 2.2 became a W3C Recommendation on 12 December 2024 (W3C).
Three of its new criteria land directly on a purchase flow:
- 3.3.8 Accessible Authentication (Minimum), Level AA. Account login cannot depend on a cognitive function test with no alternative. Blocking paste into a one-time-code field is the classic violation.
- 3.3.7 Redundant Entry, Level A. Nobody should have to retype the shipping address they entered two steps earlier.
- 2.5.8 Target Size (Minimum), Level AA. A floor of 24 by 24 CSS pixels, which quantity steppers and color swatches routinely miss.
Two older criteria matter more in retail than anywhere else. 3.3.4 Error Prevention (Legal, Financial, Data) at Level AA requires that transactions be reversible, checked, or confirmed, and an order is a financial transaction. 1.3.5 Identify Input Purpose at Level AA is why your address and card fields need proper autocomplete values (W3C). If you want the criteria laid out by level while you triage, use the WCAG checklist, and what changed between 2.1 and 2.2 for the delta.
Why do so many accessibility lawsuits involve online stores?
Not because retailers are worse than everyone else. A store has more interactive surface than almost any other kind of site: faceted filters, variant pickers, quantity controls, a cart that updates without a page load, a multi-step checkout, and a payment step. Every one of those is a place where a custom widget replaced a native control.
The numbers follow the surface area. In 2025, 35.8% of the top 500 e-commerce retailers received at least one ADA accessibility lawsuit, and food and service businesses made up roughly 21% of filings (UsableNet). Automated data points the same way. WebAIM's February 2026 scan of a million home pages found an average of 56.1 detectable errors per page, with the Shopping category at 71.0 (WebAIM). That is home pages only, which is the least interactive page a store has.
Where do e-commerce sites actually fail?
The failures cluster, and they are boring. DOJ's own guidance lists inaccessible online forms and mouse-only navigation among its examples of barriers (ADA.gov). WebAIM's 2026 numbers say the same thing at scale: 83.9% of home pages had low-contrast text, 53.1% had images missing alternative text, 51% had form inputs with no label, 46.3% had empty links, and 30.6% had empty buttons (WebAIM).
That last one is the cart icon. A <button> containing nothing but an <svg>, no aria-label, announced by a screen reader as "button." Here is where those failures land in a store:
| Part of the store | What typically breaks | Success criterion |
|---|---|---|
| Category filters | <div> checkboxes with no role or checked state | 4.1.2 Name, Role, Value |
| Product images | Alt text is the SKU, or the file name | 1.1.1 Non-text Content |
| Variant swatches | Color is the only thing distinguishing options | 1.4.1 Use of Color |
| Quantity steppers | Unlabeled +/− buttons under 24×24 px | 2.5.8, 4.1.2 |
| Add to cart | Cart total updates with no announcement | 4.1.3 Status Messages |
| Checkout forms | Placeholder used as the label; errors marked in red only | 3.3.2, 3.3.1 |
| Account login | Paste blocked in the 2FA field | 3.3.8 Accessible Authentication |
| Order review | No confirmation or reversal step before charge | 3.3.4 Error Prevention |
The row I hit most often in real audits is the status-message one. A shopper picks a size, the price and stock label update in the corner of the screen, and nothing announces the change. Sighted users get it for free. Everyone else finds out at the payment step. Building accessible forms covers the checkout half of that table in depth, and the contrast checker handles the 83.9% case.
Do accessibility overlays make an online store ADA compliant?
No. In January 2025 the FTC ordered overlay vendor accessiBe to pay $1 million over claims that its accessWidget product could automatically make a website compliant with WCAG (FTC). UsableNet's tracking of 2025 filings found no meaningful reduction in lawsuits against sites running a widget (UsableNet).
The mechanical reason is simple. A widget runs after your markup has already loaded and can only guess at intent from the outside. It cannot know that the <div> you styled as a checkbox is meant to be a checkbox, and it cannot invent the label your quantity input never had. Overlays don't fix code. We built the opposite on purpose. If you inherited one, the accessiBe FTC settlement post explains what the order actually said.
How do I check my store?
Work the buying path, not the page count.
- Scan one page of each template. A category page, a product page, the cart, and each checkout step. Four scans tell you more about a 40,000-SKU catalogue than 40,000 product pages do, because the errors live in the template.
- Do the whole purchase with the keyboard only. Unplug the mouse and buy something. Most stores fail this in under three minutes, usually at a custom dropdown or a modal that never returns focus.
- Put a screen reader on the flow that makes money. Automated testing catches somewhere between 30 and 57% of issues depending on the study; Deque's own analysis put full automated coverage at 57% (Deque). Whether "Error: invalid" makes sense read aloud out of context is a judgement no scanner makes. Manual versus automated testing covers the split.
- Publish an accessibility statement and date it. It documents your effort and gives customers a way to report a barrier before anyone else hears about it. The accessibility statement pillar covers what belongs in one.
- Re-scan on a schedule. A theme update in March undoes the button labels you fixed in January. A dated trail of scans and fixes is the thing your counsel will ask for.
FAQ
Is an online store legally required to be ADA compliant?
If your business is open to the public, the ADA applies to your website, per DOJ's longstanding reading of Title III (ADA.gov). There is no federal regulation naming a WCAG version or a deadline for private businesses, but courts and settlements treat WCAG 2.1 Level AA as the benchmark.
Which WCAG level does an e-commerce site need?
Level AA, and WCAG 2.2 is the version to build toward. W3C states that content conforming to WCAG 2.2 also conforms to 2.1 and 2.0, so 2.2 AA covers the version litigation cites while adding criteria written for logins and purchase flows (W3C).
Do small online stores get sued over accessibility?
Yes. Of the companies named in 2025 web accessibility filings, 64% reported annual revenue under $25 million (UsableNet). Title III covers public accommodations regardless of size.
Does the ADA cover checkout and payment pages?
The ADA covers the goods and services a public accommodation offers online, which includes the steps required to complete a purchase (ADA.gov). WCAG 3.3.4 Error Prevention (Legal, Financial, Data) applies specifically to transactions, requiring them to be reversible, checked, or confirmed (W3C).
Can a scanner make my store ADA compliant automatically?
No. Automated testing finds roughly 30 to 57% of accessibility issues, and the rest needs human review (Deque). Claims of automatic compliance are what drew the FTC's $1 million order against accessiBe in 2025 (FTC).
See what your storefront looks like today
Start with the templates that carry your revenue. A scan returns a ranked list with the exact selector for each finding, so you can fix the unlabelled cart button before you touch a decorative image warning. Run a free accessibility scan on your category, product, and checkout pages.
Written by Pavel Charkasau, founder of wcagc.com. I read the source documents so the guidance here matches what DOJ and W3C actually published.
Last updated: August 19, 2026
Sources
- ADA.gov, Guidance on Web Accessibility and the ADA (accessed August 19, 2026).
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2 (W3C Recommendation, 12 December 2024; accessed August 19, 2026).
- UsableNet, ADA Web Lawsuit Trends for 2026: What 2025 Filings Reveal (published January 8, 2026; accessed August 19, 2026).
- WebAIM, The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages (published February 2026; accessed August 19, 2026).
- Deque Systems, Automated Testing Study Identifies 57 Percent of Digital Accessibility Issues (accessed August 19, 2026).
- Federal Trade Commission, FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant (published January 3, 2025; accessed August 19, 2026).