Adobe Commerce EN 301 549 Checker

EN 301 549 for Adobe Commerce Sites

EN 301 549 is the European standard for accessible information and communication technology. For websites, its clause 9 reuses WCAG: version 3.2.1 uses WCAG 2.1 Level AA, and version 4.1.1, published in September 2026 for the European Accessibility Act, uses WCAG 2.2 Level AA.

The European Accessibility Act has applied to e-commerce and other consumer services since June 28, 2025, wherever the business is based. This checker runs the scan with the EN 301 549 preset, which tests the WCAG 2.1 AA web requirements. Run the Adobe Commerce WCAG 2.2 checker as well to cover version 4.1.1.

A Adobe Commerce store selling to EU consumers is an e-commerce service under the European Accessibility Act. Scan product, cart and checkout pages, check every language version, and publish accessibility information about the service.

Who Should Run the Adobe Commerce EN 301 549 Checker

• Adobe Commerce businesses that sell products or services to consumers in the EU.
• Public sector bodies in the EU running a site on Adobe Commerce.
• Vendors selling software or services to EU public bodies.
• Non-EU companies with EU customers, since the EAA follows the customer.

EN 301 549 Requirements to Check on Adobe Commerce

• 1.4.10 Reflow

  Pages must reflow on a narrow screen without scrolling in two directions.

• 1.4.11 Non-text Contrast

  Controls, icons and focus indicators need 3:1 contrast.

• 3.1.1 Language of Page

  Each page must declare its language, which matters on multilingual EU sites.

• 3.3.2 Labels or Instructions

  Form fields, including checkout and consent forms, need visible labels or instructions.

• 4.1.2 Name, Role, Value

  Custom controls such as cookie consent switches need a name, role and state.

• 4.1.3 Status Messages

  Status messages, such as cart updates and form errors, must be announced.

Where Adobe Commerce Sites Usually Fail EN 301 549

These problems come up again and again on Adobe Commerce sites, and each one fails EN 301 549. The Adobe Commerce accessibility checker explains how to fix them in Adobe Commerce.

• Page Builder content. Rows, banners and tabs built with Page Builder are easy to make visually, but heading levels get skipped, images lack alt text and buttons are styled links with unclear names.
• B2B account pages. Company users, quote requests, requisition lists and quick-order forms are data-heavy tables and forms where labels, headers and error messages are easy to miss.
• Multi-store and language variants. Each storefront view can have its own theme and content. A missing page language or wrong lang attribute on a translated store view makes a screen reader read in the wrong voice.
• Search and product recommendations. Live search overlays, autocomplete and recommendation carousels often lack names, roles and announcements for results.
• Custom checkout and payment integrations. Agency-built checkouts and payment or financing widgets frequently add unlabeled fields and iframes without titles.

Worried about ADA claims as well? The Adobe Commerce ADA compliance checker covers the Adobe Commerce risks behind most complaints.

What to Test by Hand on Adobe Commerce

Automated testing finds many, but not all, EN 301 549 failures. Check these yourself after the scan:

1. Check every language version, including the page language setting (3.1.1).
2. Test the cookie consent banner with a keyboard and screen reader.
3. Publish accessibility information for your service, as the EAA requires.
4. Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.

Start 3-day free trial

Related Guides

• EN 301 549 CheckerThe EN 301 549 standard in full, for any website.
• The European Accessibility Act: Technical Aspects of ComplianceThe European Accessibility Act for technical teams: who it covers, EN 301 549 and WCAG requirements, exemptions, national rules and a compliance checklist.
• 5 Best ADA Compliance Software for Small Businesses (Updated 2026)The 5 best ADA compliance software for small businesses in 2026: AccessBell, AccessibilityChecker.org, AudioEye, UserWay and accessiBe, by price and features.
• WCAG 4.1.2 Name, Role, Value Explained in Plain EnglishWCAG 4.1.2 Name, Role, Value explained simply: give every control a name, role and state with native HTML and ARIA, with code examples and how to test.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Adobe Commerce EN 301 549 Checker: Frequently Asked Questions