Squarespace EN 301 549 Checker

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

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

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

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

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

• Low-contrast default styling. Several default template styles use light, low-contrast text that fails WCAG’s minimum contrast ratio, especially for secondary text and buttons.
• Missing image alt text. Gallery and summary blocks make it easy to add images quickly, and just as easy to skip the alt text field while doing it.
• Heading levels skipped. Editors often size text visually to "look like a heading" rather than choosing the correct heading level, which breaks the page structure screen readers rely on.
• Vague link text. "Read more" and "Click here" links, common in Squarespace’s blog and summary blocks, are not descriptive out of context for screen reader users scanning a page’s links.
• Custom code injections. Code blocks and embedded third-party widgets bypass Squarespace’s own markup and can introduce issues the platform has no control over.

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

What to Test by Hand on Squarespace

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.
• 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.
• Free Tools to Check Website Accessibility: 6 Best Options ComparedCompare the best free tools to check website accessibility: AccessBell, WAVE, axe DevTools, Accessibility Insights, Lighthouse and ANDI, and when to use each.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Squarespace EN 301 549 Checker: Frequently Asked Questions