EAA compliance for Squarespace: WCAG 2.1 AA checklist & fixes

What the EAA actually requires from a Squarespace site

The European Accessibility Act (Directive 2019/882) applies to consumer-facing online services from 28 June 2025. For a Squarespace site selling to EU consumers, that means the storefront, checkout, account area, and any embedded payment flow have to meet WCAG 2.1 Level AA via the harmonised standard EN 301 549. Microenterprises with under 10 employees and below €2 million in turnover are exempt for services, but not for products.

Fines vary by member state. Germany caps individual penalties at €100,000; France can fine up to 4% of group turnover; Spain reaches €600,000 for serious or repeated breaches. None of those numbers are theoretical — market surveillance authorities have already started auditing storefronts in Germany and France in the run-up to enforcement.

In practice, the work breaks down into three buckets: theme-level fixes (focus styles, contrast, semantics), interaction-level fixes (carousels, modals, drawers, gallery widgets), and content-level fixes (alt text, headings, descriptive link text). The list below covers the Squarespace-specific failure points we see most often during scans.

Top WCAG failures we see on Squarespace sites

Across hundreds of Squarespace scans, the same handful of issues show up over and over. None of them require ripping the theme apart — most are fixable in a few hours by someone comfortable in the platform's editor or template files.

• Color palettes failing 4.5:1

  Many templates default to gray-on-gray text, especially in footers and small caption text.

  1.4.3 — Level AA

• Image blocks without alt text

  Image alt is set per block; bulk uploads usually skip it.

  1.1.1 — Level A

• Accordion blocks not keyboard-accessible in some templates

  Older templates use mouse-only handlers. Switching template family can fix this.

  2.1.1 — Level A

Concrete code fixes for Squarespace

Below are copy-paste fixes for the most common Squarespace issues. They assume you have access to your theme code or the platform's custom-code injection panel. If you cannot edit code directly, share these snippets with whoever maintains the site — every one of them is a ten-minute change.

// Use the built-in contrast checker on text colors.
// Aim for 4.5:1 (normal text), 3:1 (large text/UI).

Tools and plugins worth installing first

• Built-in Squarespace Site Styles contrast hint

• Code Injection for global focus styles

How to scan a Squarespace site without missing anything

Automated scanners catch about 30–40% of WCAG issues; the rest need manual review. The good news is that the 30–40% includes the most expensive issues to remediate after the fact, so an automated scan is the cheapest way to get unstuck. Run one before you change a line of theme code.

• Use the Squarespace preview link to scan; published-only changes can lag.

Frequently asked questions

Other website builder platforms