Skip to main content

Free Squarespace Accessibility Checker

Squarespace gives you a clean starting point, but templates, the Style Editor, and image blocks quietly introduce accessibility barriers as you build. Paste your URL to scan your live site against WCAG 2.2, the standard behind ADA compliance, and get specific, Squarespace-aware fixes in seconds.

No signup requiredWorks on 7.0 and 7.1Results in seconds

Where Squarespace Sites Trip Up on Accessibility

The barriers are rarely in the theme itself. They come from the day-to-day choices you make in the editor. These three account for a large share of what a scan finds on Squarespace sites.

Alt text

Filenames become alt text

Gallery blocks, product images, and some banners inherit alt text from the uploaded filename, so IMG_4821.jpg is what a screen reader reads aloud. Set explicit alt text per image in the block editor.

Contrast

Style Editor color pairs

Preset theme colors and text placed over background images often fall below the 4.5:1 contrast ratio. These are set globally in the Style Editor or Site Styles, so one bad pairing repeats across the whole site.

Headings

Levels chosen for size

Text blocks let you pick Heading 1 through 4, so editors often choose a level for how big it looks. That skips levels (H1 straight to H3) and breaks the outline screen reader users navigate by.

7.0 vs 7.1: Your Version Changes What You Can Fix

Squarespace ships two generations, and where you edit accessibility settings depends on which one you are on. If you are unsure, the template family name in your site design settings is a giveaway: named families like Brine or Bedford are 7.0, while a single unified editor with section-based pages is 7.1.

7.0

Squarespace 7.0 — Template Families

In 7.0 the layout is dictated by your template family, and each family has its own fixed rules for how headings, banners, and navigation are structured. Banner areas often hard-code the H1, so a page can end up with a decorative banner as its only H1 while your actual page title sits in a lower level. Color and type are controlled in the Style Editor, which applies globally, so a single low-contrast setting repeats everywhere.

Custom CSS and header or footer code injection are available on Business and Commerce plans, which gives you an escape hatch for the fixes the editor cannot reach. That same code access is also a common source of new issues when injected markup skips labels or roles.

7.1

Squarespace 7.1 — One Template, Section Themes

7.1 drops separate template families in favor of one system where every page is built from sections. Color is handled through Site Styles and per-section color themes, so you can accidentally place light text on a light section theme and repeat that pairing across many sections at once. Heading levels are chosen inside each text block, which is flexible but makes it easy to skip from H1 to H3 purely for visual size.

The upside is that most fixes in 7.1 are reachable without code: alt text, heading levels, button and link text, and section color themes are all editable in the standard interface. A scan tells you which section and which element to open.

Fixing Common Squarespace Issues Without Custom Code

Most of what a scan flags on Squarespace is editable in the standard editor. Here is where each fix lives, and where the platform makes it harder than it should be.

Image blocks and galleries

Add alt text per image in the image editor rather than relying on the filename. Gallery, product, and summary blocks are the usual culprits for filename-derived alt text. For images that are purely decorative, leave the alt text empty so assistive technology skips them instead of reading a meaningless string.

Color and contrast

Change failing pairings in the Style Editor (7.0) or Site Styles and section color themes (7.1). Because these settings apply globally or per section theme, fixing one pairing usually clears the same issue across many pages at once. Test a color pair before you commit to it.

Headings and form blocks

Set heading levels in text blocks by meaning, not size, so the outline reads H1, then H2, then H3 without gaps. In form blocks, keep visible field labels rather than replacing them with placeholder text, since placeholders disappear on focus and are not a reliable label for screen readers.

Code injection and embeds

Anything you drop into a code block, embed block, or header and footer injection bypasses Squarespace guardrails, so those areas need direct attention to labels, roles, and contrast. If you use a third-party widget, check that it does not remove keyboard access or hide content from assistive technology.

A word on accessibility overlay widgets

You will find overlay and widget plugins marketed as one-click Squarespace accessibility fixes. They do not correct the underlying markup and do not make a site compliant. An overlay cannot add real alt text you never wrote or fix a heading order baked into your content, and some overlays introduce their own problems for screen reader users. The durable fix is to correct the content itself in the editor.

CompliaScan can suggest concrete fixes with your own AI provider key (bring your own key), and those suggestions never modify your Squarespace site automatically. You review each one and apply it in the Squarespace editor yourself, so you stay in control of what ships.

What Automated Scanning Catches on Squarespace

CompliaScan uses axe-core, the industry-standard accessibility engine, plus nine additional checks of our own. Together they reliably detect roughly 30 to 40 percent of WCAG 2.2 success criteria: the objective, machine-testable ones. On a Squarespace site that maps directly onto the issues you are most likely to have.

What the scan detects automatically

  • Missing or filename-style alt text on image, gallery, and product blocks
  • Insufficient color contrast from Style Editor and section theme color choices
  • Missing form labels on form block fields that rely on placeholder text
  • Broken heading structure such as skipped levels from banners and text blocks
  • Invalid ARIA and link text including empty links and vague button labels

What still needs a human

The remaining 60 to 70 percent of criteria call for judgment no scanner can make. Whether the alt text you wrote actually describes the image, whether a gallery slideshow or carousel is fully operable by keyboard, and whether your reading order makes sense are all things a person has to check. A clean automated scan is necessary but not sufficient for full WCAG conformance.

Honest about compliance claims

No automated scan, this one included, can certify that a site is fully ADA compliant or lawsuit-proof, and any product that promises that is overselling. What a scan does well is clear the objective barriers fast and give you a documented, repeatable baseline. Pair it with periodic manual review for a defensible position.

Catch regressions after edits

Squarespace sites change often, and a new image, a restyled section, or an added form block can reintroduce an issue you already fixed. Paid plans re-check your pages on a schedule so fixes do not quietly regress after you publish an update.

Frequently Asked Questions

Is my Squarespace site ADA compliant?
Squarespace gives you an accessible foundation, but it does not make your site ADA compliant on its own. The theme handles some basics, yet the content you add is where most barriers appear: images uploaded without real alt text, text color chosen in the Style Editor that fails contrast, headings picked for size rather than order, and form blocks with hidden labels. A free scan checks your live page against WCAG 2.2 criteria and shows exactly which of these are present. No tool, Squarespace included, can certify full ADA compliance, because some criteria require human review.
How do I add alt text on Squarespace?
Open the image block in the editor, click the image, and use the image editor to set alt text (in 7.1 this is the 'Alt text' field; older setups fall back to the image filename). This is the single biggest gotcha on Squarespace: gallery blocks, product images, and some banner images inherit their alt text from the uploaded filename, so a file called IMG_4821.jpg becomes the alt text a screen reader announces. Rename files before upload or set explicit alt text per image. Decorative images should get empty alt text so they are skipped. A scan flags every image that is missing alt text or is using a filename-style value.
Can I fix accessibility on Squarespace without custom code?
Most of the common issues, yes. Alt text, form field labels, heading levels in text blocks, button text, and link wording are all editable in the standard Squarespace editor. Color and contrast are fixed in the Style Editor (7.0) or Site Styles and section color themes (7.1) without touching code. A smaller set of issues comes from code injection blocks, embed blocks, or third-party widgets, and those need edits to the injected markup. Be cautious with accessibility overlay widgets sold as one-click fixes: they do not correct the underlying markup and do not make a site compliant.
What does an automated scan catch on Squarespace?
CompliaScan runs axe-core plus nine additional checks and reliably detects roughly 30 to 40 percent of WCAG 2.2 success criteria, the machine-testable ones: missing alt text, insufficient color contrast, missing form labels, invalid ARIA, and broken heading structure. On Squarespace that covers the most frequent real-world problems. The remaining criteria, such as whether alt text is actually meaningful or whether a slideshow is operable by keyboard, need manual review. Treat the scan as the fast first pass that clears the objective issues, then follow up with human testing.

Check Your Squarespace Site Now

See exactly which images, colors, headings, and forms need attention before a visitor or a demand letter finds them. Run a free scan of your live Squarespace site against WCAG 2.2. Results in seconds, no signup required.