Skip to main content
आपका ब्राउज़र पुराना है, इसलिए यह साइट ठीक से नहीं दिखेगी। कृपया Chrome, Edge, Firefox या Safari का नया संस्करण इंस्टॉल करें।
E-Commerce · ADA Title III & EAA

E-Commerce
Accessibility Compliance

Online stores, subscription services, and any site facilitating commercial transactions are routinely targeted in ADA Title III litigation. Retail and e-commerce sites are consistently among the businesses most frequently named in these lawsuits. Here's where checkout flows tend to fail, and how to fix it.

3,117
Federal ADA website lawsuits (2025)

Seyfarth Shaw count; online retailers are among the businesses most often named

June 28, 2025
The EAA has applied since

E-commerce is one of the services the EAA names, for stores selling to EU consumers (microenterprises are exempt)

WCAG 2.1 AA
The technical bar

The level US settlements most often reference, and the web level of EN 301 549 (the EAA's reference standard)

Who Must Comply?

ADA Title III (US)

Online Stores & Retailers

Online stores, subscription services, and any site facilitating commercial transactions are routinely targeted in ADA litigation. The same standard is documented in AccessiSight's ADA guide.

EAA / EN 301 549 (EU)

Any Merchant Selling to EU Consumers

"E-commerce & Online Retail" is one of the European Accessibility Act's explicitly regulated categories: webshops and marketplace platforms must meet EN 301 549 / WCAG 2.1 AA across the entire purchase flow.

Common WCAG Failure Patterns in E-Commerce

These four patterns concentrate at the exact moments that determine whether a sale completes.

Checkout flow keyboard traps

WCAG 2.1.1 · Level A

Custom date pickers, address autocomplete, and multi-step checkout wizards frequently trap keyboard focus so a customer who can't use a mouse simply cannot complete a purchase. This is the #4 most common ADA violation type overall.

Product-image alt text at scale

WCAG 1.1.1 · Level A

A catalog with thousands of SKUs makes missing alternative text (the #1 most common ADA violation type) especially costly: a screen reader user can't tell what a product looks like, or in some templates, what it even is.

Cart & inventory updates without ARIA live regions

"Added to cart", "only 2 left in stock", and price changes that update the DOM silently leave screen reader users with no indication anything happened, unless the update is announced through an ARIA live region.

Payment & address form labeling

WCAG 1.3.1 / 4.1.2 · Level A

Card number, expiry, CVC, and billing-address fields are exactly the kind of form inputs that fail the #3 most common ADA violation type (missing or programmatically unassociated labels) at the single most consequential step of the funnel.

E-Commerce Compliance Checklist

Tab and test the entire checkout flow with a keyboard only, start to finish
Audit alt text coverage across the full product catalog, not a sample page
Add ARIA live regions for cart totals, stock warnings, and applied discounts
Label every payment and address field programmatically, including autofill fields
Verify color contrast on sale badges, price strikethroughs, and stock warnings
Test filters, sort controls, and infinite-scroll product grids for keyboard access
If selling to EU consumers, map the purchase flow against EN 301 549 Chapter 9
Never rely on an overlay widget as your only remediation

Frequently Asked Questions

Is my online store required to be ADA compliant?

Many courts have treated e-commerce websites as covered by ADA Title III, though some require a connection to a physical store, and there is no employee threshold. Online stores, subscription services, and any site facilitating commercial transactions are routinely targeted in ADA litigation, and DOJ guidance points to WCAG 2.1 AA as the standard courts use.

What if I sell to customers in the EU?

The European Accessibility Act (EU Directive 2019/882) has applied since June 28, 2025. E-commerce and online retail is one of its explicitly regulated categories, and it must meet the EAA's accessibility requirements across the entire purchase flow, for which EN 301 549 (WCAG 2.1 AA for web content) is the reference standard; microenterprises providing services are exempt, regardless of where the business itself is headquartered.

Do accessibility overlays protect an online store from lawsuits?

No tool can promise that. Businesses using overlay widgets are still sued, and in April 2025 the FTC finalised an order requiring overlay vendor accessiBe to pay $1 million over claims that its tool could make websites WCAG-compliant. Overlays do not remediate underlying code. Real accessibility requires fixing the source HTML, CSS, and ARIA in the checkout flow itself.

What are the most common e-commerce accessibility failures?

Keyboard traps in multi-step checkout flows, missing alt text on product images at catalog scale, cart and inventory updates with no ARIA live region to announce them, and unlabeled payment and address form fields are the failures found most often on retail sites.

Not legal advice. This guide is educational and does not constitute legal advice. Consult a qualified attorney for compliance guidance specific to your organization and the jurisdictions you sell into.

Find Checkout Accessibility Gaps Now

AccessiSight scans your full purchase flow against WCAG 2.1 AA, flags keyboard traps and missing alt text at catalog scale, and generates EN 301 549 VPATs for EU-facing stores.