The complete guide

Squarespace accessibility, explained

Making a Squarespace site accessible means fixing a short list of real things in your content: image alt text, color contrast, form labels, link and button names, and heading order, measured against WCAG 2.1 AA. This guide covers every one of them, how to check your site free, and when to have the work done for you.

Run a free accessibility scanSee done-for-you plans

What “accessible” actually means

An accessible website is one a person with a disability can actually use: a blind visitor hearing the page through a screen reader, a low-vision visitor who needs readable contrast, a motor-impaired visitor navigating by keyboard alone. The measuring stick used in the US is WCAG 2.1 AA, the Web Content Accessibility Guidelines. ADA website demand letters and lawsuits almost always point at WCAG failures, and restaurants and other small businesses are among the most frequent targets. Beyond risk, the practical case is simple: an accessible site works better for every customer, including the ones using their phone in bright sunlight.

What Squarespace handles for you, and what it cannot

Squarespace templates give you a reasonable structural starting point: responsive layouts, mostly-semantic markup, and a few built-in behaviors. But the issues that actually show up in scans and demand letters live in the content you add, and no template can write your alt text or pick your colors for you. There is also no general content API and no real accessibility plugin for the platform (here is the honest answer on plugins and widgets), so the work happens in the editor itself.

The seven fixes that matter most

Scan a hundred Squarespace small-business sites and the same short list shows up every time. In rough order of how often we see them:

  • Missing image alt text. Alt text is the short description a screen reader speaks for an image. Every meaningful photo needs one; decorative images should be marked so they are skipped. In Squarespace you set it on each image block.
  • Low color contrast. Body text needs a 4.5:1 contrast ratio against its background (3:1 for large text). The classic Squarespace failure is light text over a hero photo. The honest fix is darkening the backdrop, via Site Styles or a reversible CSS scrim, not nudging the font color.
  • Unlabeled form fields. Placeholder text that disappears when you start typing is not a label. Contact, newsletter, and reservation forms need a visible label per field.
  • Vague link and button names. “Click here” and “learn more” tell a screen-reader user nothing. Links should say where they go, and icon-only buttons need an accessible name.
  • Broken heading order. One H1 per page, no skipped levels. Screen-reader users navigate by headings the way sighted users skim.
  • Fake lists and missing structure. Dashes typed into a paragraph are not a list. Real list formatting, skip links, and correct ARIA let assistive tech understand the page.
  • PDF menus and third-party embeds. A linked PDF menu is usually unreadable to a screen reader, and reservation or ordering widgets run on someone else’s code. These cannot be fixed from inside your site, but they should be identified and addressed: put the menu on a real page, and note the embeds in your records. Restaurants, this is the big one for you; see accessibility for restaurant sites.

How to check your site

Start with a scan against WCAG 2.1 AA so you are working from facts, not guesses. Our free scan crawls your pages, no credit card, and shows the real issues in plain English. Automated scanning honestly catches only a portion of possible issues, so add two hand checks: tab through your site with just a keyboard (can you reach and operate everything?), and listen to your home page with the screen reader built into your phone. If you would rather see the common problems first, start with is my Squarespace site accessible?

Do it yourself, or have it done for you

Everything above is doable by a patient owner inside the Squarespace editor, and this guide plus the FAQ will get you a long way. The honest catch is time and recurrence: every edit, new page, or seasonal menu can introduce new issues, so accessibility is a habit, not a one-time project. That is the gap Kat ADA exists to fill. Kat ADA is a done for you Squarespace accessibility service: a specialist makes real source fixes inside your site, documents the work per WCAG 2.1 AA, and sends a monthly report. Not an overlay. You grant access once, a specialist makes the fixes in your actual content, and each month you get a dated good-faith record of the work. If a widget has been pitched to you instead, read overlays vs. real fixes and what to use instead of an overlay before you decide.

Keep a dated record

Whichever path you choose, write down what you fixed and when. A dated log of real remediation is documentation of an ongoing good-faith effort, and owners who have faced demand letters will tell you it matters. Doing the work and being able to show it beats hoping.