Ecommerce Accessibility and the European Accessibility Act: What Stores Must Do

Ecommerce accessibility means people with disabilities can find products, understand them, and complete checkout using a keyboard, a screen reader, zoom or voice control. Since 28 June 2025, the European Accessibility Act (EAA) has required most businesses that sell to consumers in the EU online to meet accessibility requirements, through each Member State's national law. In practice, the technical benchmark is WCAG Level AA, so the work is about fixing your templates, components and content against that standard.

This guide explains what the EAA covers, then gives a WCAG checklist organized by page type, so your team can see what to test on a home page, category page, product page, cart and checkout. This is general information, not legal advice.

What the European Accessibility Act means for online stores

The EAA is Directive (EU) 2019/882. The European Commission lists e-commerce among the services it covers, alongside banking, e-books, transport ticketing and others. A few points matter most for merchants:

• It applies from 28 June 2025. Member States had to turn the directive into national law, and national authorities handle enforcement and penalties. Rules and fines therefore vary by country.
• It covers sales to EU consumers, including from businesses based outside the EU.
• Microenterprises providing services are exempt. Article 4(5) exempts them from the accessibility requirements. A microenterprise employs fewer than 10 persons and has an annual turnover or annual balance sheet total of no more than EUR 2 million, as Ireland's regulator (the CCPC) explains in its microenterprise guidance.
• The technical bar is WCAG-based. Services that comply with harmonized standards are presumed to conform. For ICT that standard is EN 301 549. As of November 2026, the version in force is V3.2.1 (2021), built on WCAG 2.1 Level AA. V4.1.1, published on 2 September 2026, moves to WCAG 2.2 Level AA; according to Ireland's National Disability Authority, its citation in the Official Journal is expected on 16 December 2026. Meeting WCAG 2.2 AA now covers both.
• Information duties apply too. Under Article 13 and Annex V, service providers must prepare information explaining how their service meets the accessibility requirements and make it available to the public in accessible form for as long as the service operates. Many stores do this with an accessibility statement linked from the site.
• Transitional provisions are narrow. Article 32 lets service contracts agreed before 28 June 2025 continue until they expire, for no more than five years, and lets providers keep using products they lawfully used before that date until 28 June 2030. Do not assume they give a live website extra time; check with your counsel.

Selling to several EU countries? Each one has its own enforcement authority. Our guide to cross-border ecommerce with Magento covers the store setup side of selling in multiple markets.

What changed in WCAG 2.2

WCAG 2.2 became a W3C Recommendation on 5 October 2023. It keeps the WCAG 2.1 criteria (except 4.1.1 Parsing, which was removed as obsolete) and adds nine new ones. The Level A and AA additions are the ones most stores need to act on:

WCAG checklist by page type

Most accessibility problems in a store come from a few shared templates and components. Fix the component once and every page that uses it improves. Test each page type with a keyboard only, a screen reader (NVDA, JAWS or VoiceOver), 200% and 400% zoom, and an automated checker.

All pages (header, footer, global components)

• A "skip to content" link that becomes visible on focus.
• Main navigation and mega menus that open and close with the keyboard and announce their state.
• Visible focus styles on every link, button and field.
• Text contrast of at least 4.5:1 (3:1 for large text), and 3:1 for icons and field borders.
• Cookie banners, popups and chat widgets that can be reached, used and dismissed by keyboard, and do not hide focused content.
• A correct page language attribute on each store view.
• A consistent location for help and contact links.

Home and landing pages

• Carousels with pause controls, and no auto-advance that cannot be stopped.
• Meaningful alt text for promotional images, and real text instead of text baked into images.
• One H1 and a logical heading structure.
• Videos with captions; no autoplaying audio.

Category and search results pages

• Filters (layered navigation) usable by keyboard, with the number of results announced after filtering.
• Price sliders with text inputs or buttons as an alternative.
• Product cards with one clear link name, not "View" repeated many times.
• Sort and pagination controls with accessible names and large enough targets.
• Search autocomplete that works with arrow keys and announces suggestions.

Product pages

• Swatches for color and size with text labels, selected state announced, and not color alone.
• Image galleries and zoom controls operable by keyboard, with alt text per image.
• Stock and price changes announced when a variant is selected.
• Add-to-cart confirmation announced to screen readers, and focus managed if a mini cart opens.
• Tabs or accordions for details that follow standard keyboard patterns.

Cart and mini cart

• Quantity controls with labels such as "Quantity for [product]".
• Remove buttons that name the product.
• Totals updates announced, and no time-outs that empty the cart without warning.

Checkout

• Every field has a visible label and the correct autocomplete attribute (name, email, address, postal code).
• Errors are described in text, linked to the field, and announced; no reliance on red borders alone.
• Steps and progress are clear, and focus moves to the new step.
• Payment iframes from your provider are tested too. If they fail, raise it with the provider.
• No inaccessible CAPTCHA blocking order placement.
• Order confirmation is readable and includes order details in text.

Account, login and forms

• Login supports password managers and paste.
• Show-password toggles, clear password rules up front.
• Contact, returns and newsletter forms follow the same label and error rules as checkout.

How to approach this on Adobe Commerce or Magento

1. Audit a sample: pick one URL per page type per theme, plus checkout. Combine automated scans with manual keyboard and screen reader testing; automated tools catch only part of the issues.
2. Fix components, not pages: most fixes land in theme templates, UI components, and third-party extensions. Extensions that inject popups or widgets are frequent offenders.
3. Fix content: train merchandisers on alt text, headings and link text in Page Builder or CMS blocks.
4. Publish an accessibility statement that says what standard you target, known gaps, and how customers can report problems.
5. Add accessibility to QA: check new features and theme changes before release.

Accessibility and speed overlap. Lighter pages with stable layouts are easier for assistive technologies and for everyone on slow phones; see Mistri's Magento performance optimization service for that side. Accessibility fixes also tend to remove friction for all shoppers, which is why they sit naturally inside ecommerce conversion rate optimization work.

FAQ

Does the EAA apply if my business is outside the EU?

If you sell to consumers in the EU, the requirements generally apply to that service. Check the law of the Member States you sell into.

Is an accessibility overlay enough?

An overlay script does not fix inaccessible templates, missing labels or broken keyboard flows. Fix the underlying code and content.

Which WCAG version should we target?

WCAG 2.2 Level AA. It covers the WCAG 2.1 criteria in EN 301 549 V3.2.1, matches the newer V4.1.1, and adds checks that affect checkout and login.

Next steps

Start with checkout and product pages, because that is where barriers cost both customers and sales. If your theme or extensions need accessibility fixes, Mistri's Adobe Commerce development service can audit and fix templates and components.

This article is general information, not legal advice. Check your obligations with qualified counsel in the countries you sell to.

Sources: EUR-Lex: Directive (EU) 2019/882; European Commission: European Accessibility Act; W3C: What's new in WCAG 2.2; Directive (EU) 2019/882, Articles 4, 13 and 32 (legislation.gov.uk copy of the EU text); CCPC: European Accessibility Act guidelines for microenterprises; National Disability Authority (Ireland): EN 301 549 V4.1.1 published.