Ecommerce accessibility — built for stores under ADA + EAA.

In the United States, ADA Title III web-accessibility complaints have run at roughly 4,300 federal filings per year through 2024, and ecommerce dominates the docket alongside restaurant booking and hospitality. Online-only retailers no longer reliably win the "no physical nexus" defence — most circuits have either rejected it or sidestepped it, and state-court filings under California's Unruh Act and New York's State Human Rights Law have grown in parallel.

In the European Union, the European Accessibility Act names "e-commerce services" explicitly in its scope list — Article 2(2)(d) — and the microenterprise carve-out (under 10 staff or under €2M turnover) catches few real retailers. Any store with a warehouse, a multi-person team, or meaningful product catalogue is in-scope and must meet EN 301 549, which references WCAG 2.2 success criteria.

The cost of inaction is concrete. US ADA settlements typically land in the $20,000–$50,000 range for first-time defendants, with repeat-target retailers running materially higher; plaintiff-side firms now operate at scale, and a single accessibility-statement scrape feeds dozens of demand letters. In the EU, EAA enforcement is moving from the warning-letter phase that dominated 2025 to the fine-issuing phase that many member states adopted in 2026 — Germany, France, Italy, Spain, and the Netherlands have all stood up enforcement teams.

The good news: ecommerce accessibility is a known shape. The same dozen failure modes recur across nearly every audit, and most are fixable in design tokens, theme components, or a focused engineering sprint. The checklist below is what we hand ecommerce teams when they ask "where do we start?"

Ecommerce code changes daily. Marketing ships a hero variant on Tuesday, the merchandising team flips a section on Thursday, an app updates over the weekend. A one-time accessibility fix lasts about as long as your next deploy — which is why the model that actually holds is three layers, not one.

First, run a free WCAG 2.2 scanner against your live store today to establish a baseline. Second, plug in continuous automated monitoring against every preview build and every production deploy — this is the layer that catches regressions before the customer does. Third, commission a manual audit by testers with disabilities at least annually, and after any major redesign or replatform — automated tooling will never catch screen-reader legibility, focus-order intent, or whether a flow is actually usable end-to-end.

For the monitoring + manual-audit handoff specifically, our monitoring buyer's guide covers the platforms that handle the scan-to-audit workflow end-to-end — Qualibooth, axe Monitor, Siteimprove, and Level Access. Pick on integration fit with your CI and on whether the platform's manual-audit network actually includes testers with the disabilities your customers have — not all of them do.