Magento (now Adobe Commerce) is the platform of choice for mid-market and enterprise e-commerce. Its flexibility comes from a deep module system and extensive customisation - but that same flexibility means accessibility is rarely consistent across a store. Under the EAA, any Magento store selling to EU consumers must meet EN 301 549 requirements, and the platform's complexity makes manual auditing impractical.
Common Magento accessibility issues
Third-party extensions inject inaccessible markup
Magento's extension marketplace has thousands of modules that inject HTML into the storefront - product tabs, review widgets, checkout steps, loyalty programmes. Most extension developers don't test for WCAG compliance, and their markup often lacks ARIA attributes, keyboard support, and proper focus management.
Checkout flow accessibility barriers
Magento's multi-step checkout relies on JavaScript-heavy UI components built with Knockout.js or custom JS. These dynamic steps frequently fail to announce state changes to screen readers, trap keyboard focus incorrectly, or lose focus entirely when sections expand and collapse.
Layered navigation filtering is keyboard-hostile
Magento's layered navigation (faceted search) uses AJAX to reload product grids without proper focus management. Keyboard users lose their place after filtering, and screen readers aren't informed that the product grid has updated.
Product image galleries lack proper controls
The default Fotorama gallery in Magento 2 and many third-party gallery replacements have incomplete keyboard navigation, missing alt text propagation from the admin, and no screen reader announcements for image changes.
Admin-entered content bypasses structure enforcement
Magento's WYSIWYG editor lets content teams enter HTML directly into CMS blocks, product descriptions, and category pages. This content routinely has missing heading hierarchy, empty links, and images without alt text - and nothing in the admin prevents it.
Configurable product options lack accessible labelling
Colour swatches, size selectors, and custom option dropdowns on configurable products frequently use visual-only indicators. Swatch colours are not communicated to screen readers, and custom option groups often lack proper fieldset and legend markup.
How Lumi works with Magento
Lumi scans your Magento storefront end to end - product listing pages, product detail pages, category pages, CMS pages, the cart, and multi-step checkout. Our five scanning engines catch issues in Magento's core Luma/Hyvä markup, extension-injected content, and admin-authored CMS blocks. Set up continuous monitoring to catch regressions from extension updates, theme changes, and content edits.
Magento-specific WCAG gotchas
Extension updates can silently break accessibility
Magento stores typically run dozens of third-party extensions. Any extension update can change the rendered HTML, introducing new accessibility failures without any visible change on screen.
Knockout.js templates are hard to audit manually
Magento 2's frontend relies on Knockout.js templates that render client-side. Accessibility issues in these templates don't appear in server-rendered HTML, meaning they're invisible to basic HTML validators.
Hyvä and custom frontends need independent scanning
If you've replaced Magento's default Luma frontend with Hyvä, a PWA Studio frontend, or a headless build, the accessibility profile is completely different. The same extensions can produce different markup in different frontends.
Scan your Magento site for free
See how your site measures up against WCAG 2.2 and EN 301 549 - in 30 seconds, no signup required.
Frequently asked questions
Is Magento accessible out of the box?
Magento's default Luma theme has some accessibility support, but it does not meet WCAG 2.2 AA in full. Key areas like checkout, layered navigation, and product galleries have known accessibility gaps that require remediation.
Does the EAA apply to Magento stores?
Yes - if your Magento store sells products or services to EU consumers, the EAA applies. E-commerce is explicitly in scope, and Magento's use in mid-market and enterprise retail means most Magento stores serve EU markets.
How do Magento extensions affect accessibility?
Extensions are the biggest accessibility variable in Magento. Each extension injects its own HTML, CSS, and JavaScript into your storefront. Most are never tested for accessibility, and they can override core accessibility features. Every extension should be scanned individually.
Can I fix accessibility issues without rebuilding my Magento theme?
Many issues can be fixed through template overrides, layout XML changes, and CSS adjustments without a full theme rebuild. However, stores with deeply customised checkout flows or heavily modified themes may need more significant development work.
Related resources
Last reviewed: April 2026. Content is reviewed quarterly for accuracy.