Why Magento and EAA
Magento (now Adobe Commerce) runs a large share of Europe's mid-size and enterprise webshops — exactly the e-commerce category the European Accessibility Act regulates without a micro-enterprise exemption. Since June 2025 an inaccessible Magento store is a legal exposure in every EU market, and B2B buyers increasingly cascade EN 301 549 requirements into supplier contracts. The scale differs from WordPress or Wix: Magento stores have more custom theming, more extensions, and more complex transactional flows — which means more surface area for failures, but also more budget to fix them properly.
No Size Exemption
Unlike service providers, e-commerce falls under the EAA regardless of company size. Even a two-person Magento shop must comply.
Theme Inheritance Risk
Most stores run heavily customised descendants of Luma — accessibility bugs baked into the parent theme replicate on every page.
Extension Wild West
Checkout upgrades, search, reviews and wishlists often come from third-party vendors with unknown accessibility quality. Each one needs an audit.
Common Magento Failures
Across Magento storefronts, these defects dominate:
Layered Navigation
Filter facets rendered as div-based toggles without aria-expanded or keyboard support. Screen-reader users cannot narrow a product grid at all.
Quantity & Variant Inputs
Custom steppers replacing native number inputs, swatches without labels or selected-state announcements — the classic cart-breaking bugs.
One-Page Checkout
Ajax-swapping checkout sections that neither move focus nor announce errors. Payment fields without programmatically associated labels.
Product Media
Image zoom galleries without keyboard operation or alt text; colour variants conveyed only by swatch visuals.
Toasts & Mini-Cart
"Added to cart" confirmations shown visually only — no ARIA live region, so non-sighted shoppers re-add items repeatedly.
Search Autocomplete
Type-ahead suggestions in inaccessible popups that ignore arrow keys and escape.
Theme and Template Fixes
Remediation happens mostly in your custom theme:
Start from semantics: restore real landmarks (header, nav, main, footer), one h1 per page, and product titles as real headings in list/grid templates.
Native inputs first: replace custom quantity steppers and selects with native elements styled to match — they inherit keyboard and screen-reader behaviour for free.
ARIA states: faceted navigation needs aria-expanded on toggles, aria-pressed on filter chips, and result-count updates announced via aria-live.
Focus management: every Ajax section swap (cart updates, checkout steps) moves focus to its new content; error summaries receive focus and link to individual field errors.
Form labels: audit every template that renders form fields for explicit label associations — Magento's knockout templates frequently omit them.
Contrast tokens: fix grey-on-grey price/meta text once in theme variables, then re-verify across sale badges and buttons.
Extensions and Upgrades
Treat every third-party extension as an accessibility unknown until proven otherwise. The practical method: on staging, walk the extension's complete flow with keyboard only, then with a screen reader — install, configure, use, undo. Vendors vary wildly; some major checkout and search modules have known public accessibility issues. When an extension fails and no vendor fix exists, decide deliberately: replace it, wrap it with a corrective layer, or document it as a limitation in your accessibility statement with a workaround path. Also note that upgrading between Magento versions silently reintroduces old bugs wherever you patched vendor files — re-run your scan after every upgrade as standard practice.
Audit Workflow
A repeatable Magento audit process for agencies and shop owners:
1. Automated crawl of home, category, product, cart, checkout and account templates — expect 20-50 distinct findings on a typical store.
2. Transactional journeys: complete search → filter → product → cart → checkout end-to-end by keyboard, then by screen reader. These journeys carry the EAA risk.
3. Extension pass: audit each installed module's widgets individually.
4. Fix in theme (not vendor patches where avoidable), deploy to staging, re-scan until clean.
5. Deliver: findings report, fixed-store verification, and an accessibility statement with conformance status and documented limitations. Re-audit after every Magento version upgrade and major extension change.
Going Deeper
Run the free scanner across your storefront first — product grids, layered navigation and forms are where automated findings cluster.
Frequently Asked Questions
Does the EAA really apply to small Magento shops?
Yes for e-commerce: unlike service providers, online shops have no micro-enterprise exemption under the EAA. A small Magento store selling to EU consumers is in scope regardless of headcount.
Is Adobe Commerce more accessible than open-source Magento?
Adobe has improved core accessibility, but nearly every store layers a custom theme and extensions on top, which determines actual conformance. Platform edition matters far less than theme and extension quality.
We use a big commercial checkout extension — are we covered?
Not automatically. Major checkout modules have shipped with serious keyboard and screen-reader issues. Audit your exact installed version on staging; do not rely on marketing claims.
How long does a Magento accessibility remediation take?
A typical mid-size store needs 2-6 weeks of focused theme and template work depending on customisation depth. Automated scanning cuts this substantially by giving developers a precise worklist.
Do we need VPAT/EN 301 549 documentation?
If you sell to public-sector or large B2B customers, yes — they will request an EN 301 549 conformity report. An audit plus your accessibility statement feeds directly into that document.
Related Guides
EAA Enforcement in 2026: What Agencies Must Know
How Much Does an Accessibility Audit Cost?
Free e-book: EAA Compliance Checklist for WordPress Sites
The complete guide is available as a free EPUB — no signup required.
Get the free e-book →Want all six guides? Complete EU Compliance Bundle — combined PDF + all EPUBs, $29.