AccessivePath
Run a free audit

guide

WCAG 2.2 for e-commerce: requirements, priorities, and audit checklist

WCAG 2.2 compliance for e-commerce sites requires applying Web Content Accessibility Guidelines 2.2 to the specific failure points typical of the e-commerce industry — including product image carousels without keyboard control or proper labels, dynamic filter facets that do not announce updates to screen readers, cart drawer modals that trap focus or fail to restore it on close.

Sora Ito · IAAP WAS · Screen reader specialist3 min readPublished · Updated

Does WCAG 2.2 apply to e-commerce sites?

WCAG 2.2 (pronounced 'wuh-cag 2.2') is the World Wide Web Consortium's globally adopted standard for web accessibility, published October 2023, defining 87 testable success criteria organised under four principles: Perceivable, Operable, Understandable, Robust.

E-commerce accessibility — the lay of the land

E-commerce is the single highest-litigation accessibility vertical in the United States: industry analysts attribute the majority of ADA Title III web filings to online retail. The standard breaks happen at search filters, product gallery zoom, cart drawers, modal checkouts, and CAPTCHA — flows that combine custom widgets, dynamic state, and time-pressed transactions.

Where WCAG 2.2 bites hardest in e-commerce sites

• Product image carousels without keyboard control or proper labels

• Dynamic filter facets that do not announce updates to screen readers

• Cart drawer modals that trap focus or fail to restore it on close

• Checkout time-out warnings without WCAG 2.2.1 extend/dismiss

• CAPTCHA without accessible alternative (violates WCAG 1.1.1 + 2.5.6)

• Inaccessible PDF receipts, invoices and order confirmations

Remediation priorities

• Search and browse — must be fully keyboard- and SR-navigable

• Product detail pages — image alt text, structured data, accessible zoom

• Cart and checkout — focus management, time-out controls, accessible error recovery

• Account and order history — semantic tables, accessible filtering

• Marketing pop-ups — dismissible from keyboard, no auto-focus traps

How to comply with WCAG 2.2 on a E-commerce site

1. Establish scope and baseline: Inventory every public-facing digital property. Run an automated baseline scan to detect the ~25–30% of WCAG criteria that machines can reliably check.

2. Manual + assistive-technology audit: Engage IAAP-credentialed auditors to test the remaining ~70% of criteria — keyboard, screen reader (NVDA, JAWS, VoiceOver), zoom and cognitive criteria.

3. Remediate at source: Fix issues in source code, not via overlay widgets. Train developers; integrate axe-core into CI; track open issues in JIRA or Linear.

4. Publish an accessibility statement: Disclose conformance level, known limitations, contact for accessibility feedback, and remediation timelines. Required under EAA and best-practice under ADA.

5. Monitor and re-test: Re-audit quarterly. Re-test before every major release. Keep an internal VPAT/ACR current and post it publicly.

Sources

FAQ

Frequently asked questions

Cited answers. Sourced. Updated as standards and case law change.

  • Does WCAG 2.2 apply to e-commerce websites?

    WCAG 2.2 (pronounced 'wuh-cag 2.2') is the World Wide Web Consortium's globally adopted standard for web accessibility, published October 2023, defining 87 testable success criteria organised under four principles: Perceivable, Operable, Understandable, Robust.

  • What are the most common WCAG 2.2 failures in e-commerce sites?

    Product image carousels without keyboard control or proper labels Dynamic filter facets that do not announce updates to screen readers Cart drawer modals that trap focus or fail to restore it on close

  • What conformance level should a e-commerce site target?

    WCAG 2.2 Level AA is the consensus target for legal compliance and the level referenced by virtually every national accessibility law.

  • Why are e-commerce sites sued most often under the ADA?

    Online retail combines high traffic, transactional flows, common custom widgets (carousels, filter facets, modals), and visible failures — making it the easiest target for plaintiff firms running automated demand-letter operations. The Seyfarth Shaw tracker and UsableNet annual reports consistently place retail at the top of filings.

  • Does WCAG 2.2 apply to Shopify and other hosted platforms?

    Yes — and platform-level accessibility does not insulate you. Shopify, BigCommerce, and Magento provide partially accessible base themes, but each merchant is responsible for the final rendered site. Custom themes, custom apps, and merchant-added content typically introduce failures the base platform did not.

  • Are accessibility widgets enough for an e-commerce site?

    No. US courts have specifically ruled (Murphy v. Eyebobs, Suarez v. Camping World) that overlay widgets do not preclude ADA liability. Compliance must be achieved at the source-code level.

Stop guessing. Get the audit a Fortune 500 a11y team would have written.

Free audit on your live URL. No sign-up. IAAP-format report. Ready in hours.

Run a free auditBook a demo

founders@accessivepath.com · +977 9851094056