Framer EN 301 549 Checker

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

If you build EU sites with Framer, 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 Framer EN 301 549 Checker

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

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

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

• Text that looks like a heading. Large styled text layers become headings only when you choose a heading tag, so pages can end up with no h1 or with levels in the wrong order.
• Icon-only buttons and links. Social icons, menu toggles and arrow buttons made from a vector frame have no name until you add an ARIA label.
• Tickers, marquees and autoplay. Scrolling logo tickers, looping carousels and background video move constantly, with no way for a visitor to pause them.
• Hover-only interactions. Menus and cards that reveal content only on hover are out of reach for keyboard and touch users unless the same state is available on focus and tap.
• Contrast and focus over imagery. Text over photos and gradients can fail contrast, and custom components often hide or replace the default focus indicator.

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

What to Test by Hand on Framer

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 2.2.2 Pause, Stop, Hide Explained in Plain EnglishWCAG 2.2.2 Pause, Stop, Hide explained simply: what moving and auto-updating content needs, the 5-second rule, carousel fixes and how to test your pages.
• WCAG 2.4.12 Focus Not Obscured (Enhanced) Explained in Plain EnglishWCAG 2.4.12 Focus Not Obscured (Enhanced) explained simply: how it differs from 2.4.11, who it helps, CSS scroll-padding fixes and how to test for it.
• 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.

Framer EN 301 549 Checker: Frequently Asked Questions