Bench note
Squarespace Accessibility: Strong Defaults, No Scanner
Squarespace inherits you a skip link and a visible focus outline without being asked, which is more than most platforms manage. Then it leaves you to find every problem yourself.
Published 17 August 2026Re-measured 19 September 2026
Jump to a section5 sections
Squarespace's accessibility position is the inverse of Wix's. There is no wizard, no scanner and no dashboard. What there is instead is a set of defaults that arrive switched on, and documentation that is unusually straight about the limits of what a platform can offer.
For a lot of small sites, that trade is better than it sounds. For a lot of others it is exactly the wrong way round.
Assessed
Squarespace, assessed on accessibility headroom only
Headroom 7.6 out of 10 — Workable headroomWorkable headroom
Inherits you several things most sites get wrong — a skip link, a visible keyboard focus outline, pre-labelled form fields, semantic structure — without asking you to configure any of it. Then offers no way whatsoever to discover your own failures, and says so by pointing you at outside tools. Strong floor, no instrumentation.
Given to you
- A Skip to Content link, present without being configured
- A keyboard focus outline that appears when visitors tab through links and form fields
- Pre-labelled form fields and semantic page structures
- Alt-text fields, media captions and transcripts, and playback controls
- Colour-contrast options intended to be reachable without custom CSS
- Documentation that states plainly it is not legal advice
Still yours to build
- Finding every problem, because there is no built-in scanner of any kind
- Keeping contrast honest once you have customised the palette
- Heading structure, which the style system makes easy to break
- Anything a third-party embed or code injection introduces
- All testing, with a keyboard and with assistive technology
What arrives without being asked
Squarespace's own documentation lists what it builds in, and the list is more substantial than its silence on tooling suggests: colour-contrast options, a keyboard focus outline, a Skip to Content link, semantic page structures, pre-labelled form fields, distinct call-to-action buttons, alt-text fields, media captions and transcripts, and playback controls.
- Colour-contrast options
- Keyboard focus outline
- Skip to Content link
- Semantic page structures
- Pre-labelled form fields
- Distinct call-to-action buttons
- Alt-text fields
- Media captions and transcripts
- Playback controls
- Built-in checker: none
Two of those deserve singling out because they are the ones most sites get wrong on other platforms.
The skip link. SC 2.4.1 Bypass Blocks is a Level A criterion, and the reason it exists is that tabbing past a full navigation on every page is punishing. A great many sites never build one. Squarespace users get it without knowing it happened.
The focus outline. SC 2.4.7 Focus Visible is Level AA, and the most common way to fail it is a developer removing the browser default for aesthetic reasons. When a platform provides the outline as part of the system, there is one fewer opportunity for somebody to delete it.
Inherited defaults are worth more than they look, because they are the ones you cannot forget.
The disclaimer, which is better than most
Squarespace's accessibility guidance says this:
This guide is a resource, but it's not legal advice. Squarespace doesn't give advice on specific accessibility laws or standards applicable to your site or business.
And alongside it: "You're responsible for making sure your site complies with all legal requirements that apply to your business."
That is a platform declining to imply something convenient. It is the correct position, it is the position this site takes, and a buyer who reads it is better informed than a buyer who has just been shown a dashboard with a green number on it.
The gap: no way to find your own failures
There is no accessibility checker in Squarespace. Its own documentation sends readers to outside resources including WAVE and The A11y Project, and suggests consulting an accessibility or compliance expert for deeper work.
This is an honest answer to a real question, and it is still a gap. Compare the practical position of two site owners:
A Wix user runs the built-in scanner and has a list of what it detected, page by page. A Squarespace user has excellent defaults and no idea whether the image they added last Tuesday has alternative text on it.
The defaults protect you from the failures you would have introduced by omission. They do nothing about the failures you introduce by action — the pale grey you chose for captions, the heading you picked because it looked the right size, the block you added that renders an image with no field.
The two failures Squarespace sites actually have
In practice, the same pair recurs.
Contrast, after customisation. Squarespace's section and colour-theme system makes it genuinely easy to apply a palette across a whole site. It also makes it easy to apply a palette whose lighter text colours sit under 4.5:1 on their backgrounds. SC 1.4.3 asks 4.5:1 for body text and 3:1 for large-scale text; the enhanced criterion, SC 1.4.6 at Level AAA, asks 7:1 and 4.5:1. Nothing in the editor will stop you, so measure it yourself — the contrast piece covers the method and the places it usually goes wrong.
Heading levels chosen for size. Every visual style system has this problem and Squarespace is no exception. Heading 1, Heading 2 and Heading 3 are presented as three text sizes, so people pick them by appearance. The result is pages with three h1 elements, or an h4 immediately after an h1 because the smaller one looked better. SC 1.3.1 Info and Relationships is what this breaks, and someone navigating by heading is who it breaks for.
Who Squarespace is genuinely good for
If you are building a brochure site, a portfolio or a small service business, and you are prepared to do a keyboard pass and a contrast check yourself, Squarespace hands you a better starting position than most of the field and does not lie to you about the rest.
If you are running something with a real compliance obligation and a team publishing regularly, the absence of any instrumentation is a material problem. Nobody is going to run a manual audit after every blog post, and a platform that cannot tell you what changed is a platform where regression is invisible.
Either way, the assessment of ADA-compliant website builders sets this against the other four platforms. And to be explicit, because the phrase in that title misleads people: no platform on that page, Squarespace included, makes a website compliant with anything. Nothing on this site is legal advice.
Questions from the bench
Does Squarespace have an accessibility checker?
Are Squarespace templates accessible?
Does Squarespace say its sites are ADA compliant?
What should I check first on a Squarespace site?
Where this is filed
Every note here sits underneath one assessment: ADA-compliant website builders, which is where the platforms are read side by side. Nothing on this site is legal advice, and no builder on that page is sold as a route to compliance.
The recheck notice
When a platform quietly changes what it gives you
Builders move accessibility features without a changelog: a theme restyles its focus ring, a wizard learns a check, a field migrates to another panel. The recheck list is meant to carry one short note whenever a page here has to be corrected. It is not switched on yet, so this form keeps nothing — until it is, the re-measured date at the foot of each page is the record.