Webflow EN 301 549 Checker

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

If you build EU sites with Webflow, check each language version and the cookie banner, which is often a third-party widget. Fix templates once so every page benefits.

Who Should Run the Webflow EN 301 549 Checker

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

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

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

• Styled divs instead of real headings. Text boxes styled with heading-sized fonts, instead of an actual Heading element, look identical visually but are invisible to screen reader navigation.
• Empty alt text fields. Webflow prompts for alt text on every image, but it is optional, and images imported or duplicated quickly often keep it blank.
• Custom interactions and animations. Webflow’s interactions panel makes it easy to build scroll and click animations that move focus unpredictably or hide content from keyboard users.
• Embedded custom code. Custom code embeds and third-party widgets (booking tools, chat, video players) bring their own accessibility issues that Webflow’s Designer has no control over.
• Color contrast in the style guide. Brand color palettes chosen for visual design are not automatically checked against WCAG contrast ratios anywhere in the Designer.

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

What to Test by Hand on Webflow

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.
• What Is a Website Accessibility Checker? How Automated Testing WorksA plain-English guide to website accessibility checkers: what they test, how they map results to WCAG, what they miss, and how to choose one.
• Automated vs Manual Accessibility Testing: Where Each FitsWhat automated accessibility testing catches, what needs a human, and how to combine both into a repeatable process for finding and fixing WCAG issues.
• WCAG 2.2 Checklist: What Changed and How to Test Each CriterionA practical WCAG 2.2 AA checklist: the nine new success criteria, the one that was removed, and how to test your website against each requirement.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Webflow EN 301 549 Checker: Frequently Asked Questions