English only
E-commerce Accessibility Requirements
Focus on the path from category pages to checkout, where accessibility issues can hurt conversion, trust, and compliance.
For full shopping-flow validation, pair this guide with User Journey Scanning to test category, product, cart, and checkout as one connected path, or use the Chrome extension for fast page-level checks during implementation.
E-commerce evidence to prioritize
- EAA Article 2(2)(f) explicitly includes e-commerce services provided to consumers after 28 June 2025.
- EAA Article 3(30) defines e-commerce services as distance services delivered through websites or mobile services at the individual request of a consumer to conclude a contract.
- Baymard's 2026 compiled benchmark reports an average cart abandonment rate of 70.22% across 50 studies (last updated 22 Sep 2025).
- Baymard reports 17% abandonment due to a long or complicated checkout process and 17% due to site errors or crashes.
What is required
- The European Accessibility Act became enforceable on 28 June 2025.
- EN 301 549 is the core technical standard used in EU accessibility programs.
- For web content, WCAG 2.1 Level AA remains the practical baseline under EN 301 549.
Journeys to prioritize first
- Browse categories, search, and apply filters
- Compare products and review key details
- Add to cart, edit quantities, and review totals
- Checkout as guest or signed-in user with clear error recovery
- Complete payment and order confirmation
Where teams need a deeper accessibility review
Product discovery and faceted filtering
Category pages often depend on layered filters, infinite lists, swatches, sticky toolbars, and dynamic result counts. If these updates are not exposed correctly, users can lose context or fail to discover products entirely.
- Check that filter groups have clear labels, state, and instructions when filters expand, collapse, or stack.
- Verify that result-count and sort updates are announced when users apply filters without a full page reload.
- Test visual swatches, badges, and availability markers so they do not rely on color alone.
Product detail and decision support
PDPs usually combine galleries, variant selectors, shipping details, reviews, and promotional messaging. The problem is often not one broken control but a dense decision flow with weak semantics and poor focus handling.
- Validate variant selectors, size guides, and delivery estimators for keyboard navigation and programmatic naming.
- Ensure image galleries, zoom states, and thumbnails expose alternative text and current state clearly.
- Confirm promotional banners, urgency copy, and financing messages do not interrupt reading order or trap focus.
Checkout, payment, and recovery
Checkout is where accessibility issues directly affect revenue. Guest checkout, coupon handling, address validation, payment widgets, and 3D Secure flows need to be tested as one connected path rather than separate pages.
- Test every required field, inline validation rule, and error summary for clear recovery.
- Verify third-party payment components inherit visible focus, labels, and accessible status messaging.
- Check that cart edits, shipping changes, and price recalculations are announced without reloading the user into a new context.
Data-driven WCAG checks
| Priority area | Why it matters | What to track |
|---|
| Search, filter, and sort controls | Complex controls can make product discovery hard for keyboard and screen-reader users. | Search-to-product-list success rate |
| Checkout form clarity and errors | Weak labels and unclear errors can cause checkout drop-off. | Checkout completion rate and form error recovery rate |
| Dynamic cart and price updates | If updates are not announced, users can miss price or cart changes. | Assistive-tech announcement pass rate for cart updates |
| CTA visibility and non-text contrast | Low-contrast buttons reduce visibility and task completion. | Contrast pass rate across PDP, cart, and checkout templates |
PDF compliance
If your customer journey includes statements, contracts, invoices, or policy documents, validate PDFs as part of the same release process. WCAG and EN 301 549 expectations apply to document access, not only web pages.
Scan PDF complianceNext step
Run a scan on your highest-risk journeys, then use platform workflows to track fixes over time.
Last updated: 2 September 2026
