guide
EN 301 549 for e-commerce: requirements, priorities, and audit checklist
EN 301 549 compliance for e-commerce sites requires applying EN 301 549 — Accessibility requirements for ICT products and services 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.
Does EN 301 549 apply to e-commerce sites?
EN 301 549 is the harmonised European standard for digital accessibility, maintained jointly by ETSI, CEN, and CENELEC, that incorporates WCAG 2.1 AA for web and mobile content and adds requirements for hardware, software, documentation and support — and is the technical reference for both the European Accessibility Act and the Web Accessibility Directive.
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 EN 301 549 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 EN 301 549 on a E-commerce site
1. Identify in-scope chapters: Map your product across chapters 5–13. A web app covers chapters 9, 11, 12.
2. Test WCAG 2.1 AA: Chapter 9 references WCAG directly.
3. Cover hardware/software: Add chapter 5/11 requirements where applicable.
4. Document conformance: Produce VPAT 2.5 EU or equivalent ACR.
Sources
- EN 301 549 v3.2.1 — ETSI
- ADA Title III Lawsuit Tracker — Seyfarth Shaw
- Click-Away Pound Survey — CAP
FAQ
Frequently asked questions
Cited answers. Sourced. Updated as standards and case law change.
Does EN 301 549 apply to e-commerce websites?
EN 301 549 is the harmonised European standard for digital accessibility, maintained jointly by ETSI, CEN, and CENELEC, that incorporates WCAG 2.1 AA for web and mobile content and adds requirements for hardware, software, documentation and support — and is the technical reference for both the European Accessibility Act and the Web Accessibility Directive.
What are the most common EN 301 549 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.
founders@accessivepath.com · +977 9851094056