BigCommerce EN 301 549 Checker

EN 301 549 for BigCommerce 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 BigCommerce WCAG 2.2 checker as well to cover version 4.1.1.

A BigCommerce 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 BigCommerce EN 301 549 Checker

• BigCommerce businesses that sell products or services to consumers in the EU.
• Public sector bodies in the EU running a site on BigCommerce.
• 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 BigCommerce

• 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 BigCommerce Sites Usually Fail EN 301 549

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

• Product options and swatches. Swatch and radio-style options that are restyled with CSS can lose their visible focus ring or their label, so shoppers cannot tell which option is selected.
• Faceted search filters. Filter lists on category and search pages update the results without telling screen reader users how many products remain, and collapsible filter groups often ignore the keyboard.
• Quick view and cart preview dialogs. Modal windows that do not take focus when they open, or do not return it when closed, strand keyboard users behind them.
• Script Manager additions. Chat widgets, cookie banners, review badges and pop-ups added through Script Manager load on every page, so one inaccessible script affects the whole store.
• Images in Page Builder. Banners and promotional tiles added in Page Builder with no alt text, or with text baked into the image, hide offers from screen reader users.

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

What to Test by Hand on BigCommerce

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.
• WCAG 1.1.1 Non-text Content Explained in Plain EnglishWCAG 1.1.1 Non-text Content explained simply: how to write alt text for every kind of image, icon, chart and CAPTCHA, with code examples and a test routine.
• 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.
• Keyboard Accessibility TestingA practical guide to keyboard accessibility testing: what to check, the exact keys to use, and a component-by-component reference table mapped to WCAG.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

BigCommerce EN 301 549 Checker: Frequently Asked Questions