Squarespace accessibility widget
A widget adds
controls.
The fixes stay
in your editor.
A Squarespace accessibility widget is a script you paste into Code Injection, which needs the Core, Plus or Advanced plan. It gives each visitor a menu of their own: bigger text, contrast modes, a dyslexia-friendly font, a reading guide. It does not edit your pages. Missing alt text, skipped headings, unlabelled form fields and weak contrast are still there, and the fix for each is a setting in the Squarespace editor. Below: what a widget does and doesn’t, an 8-point self-check with the Squarespace menu path for each fix, what Squarespace already does for you, and how to install one.
By the Builderify team
Without a script, a visitor to a Squarespace page has the controls Squarespace builds in, and none of the 13 toolbar tools. With a toolbar script in Code Injection, the visitor has 13 tools. The alt text, headings, link wording, form labels, page titles, contrast and captions in the Squarespace editor are the same either way, and the script fixes none of them.
What a Squarespace accessibility widget
adds, and what it can’t touch.
Every widget installs the same way, as a script. What differs is what the script does once it loads. Here are three, as they describe themselves on their own pages.
Visitors who want a different reading setup on your pages, such as larger text, more spacing, a dyslexia-friendly font, higher contrast or a reading ruler, and find a menu on the page the quickest way to get it. The choices stay with the visitor.
What is saved in your Squarespace content and layout: the alt text, heading order, link wording, form labels, page titles, captions and tab order. A change made in the editor is saved with your site. A change a script makes in each visitor’s browser exists only while the script loads.
Checkout. Squarespace says checkout pages don’t support code, so no script-based toolbar loads there. Squarespace’s own checkout comes with pre-labelled fields, which is its answer for that page.
| Widget | How it says it installs | What it adds for visitors | What it says about fixes |
|---|---|---|---|
| Accessora | One script tag in the Footer field of Code Injection, on Core, Plus or Advanced. | 18 adjustments, four one-tap profiles (Low Vision, Cognitive, ADHD, Motor Impairment), 44 languages, and scheduled or on-demand audits. | On Growth and Enterprise, AI writes English alt text for images with none. On Enterprise, it patches common markup issues in the browser, like buttons and form fields with no label. |
| Jotform Accessibility Widget | Copy the embed code from its widget builder, then add it in a new code block in your global footer. | A text resizer, a high-contrast inverter, a link highlighter, a dyslexia-friendly font, a keyboard focus indicator, and presets. | Its post describes visitor controls only and names no fix to your content. |
| Builderify Accessibility | One script tag in the Header field of Code Injection, on Core, Plus or Advanced. | 13 tools in five groups: Font Size, Text Spacing, Dyslexia Friendly, Underline Links, Underline Titles, Disable Animations, Increase Contrast, Black & White, Invert Colors, Large Cursor, Highlight Focus, Read Aloud and Reading Guide. | None. The tools act on the page as it already is, and nothing in your Squarespace content changes. |
Accessora’s Squarespace page and Jotform’s post were read on 8 November 2026. Builderify’s row is from its own Accessibility page, and it sells one of the three, so weigh it that way. Both outside vendors say what their products add; neither is tested here.
A toolbar is a setting for the visitor, not a repair. Whether a site meets a standard depends on the pages themselves, and a script that adds a menu leaves them as they were. Squarespace’s own help says it isn’t legal advice, that it doesn’t advise on the laws that apply to your business, and that you are responsible for making sure your site complies.
For what regulators have said about overlays that promise more than that, read accessibility overlays and the accessiBe FTC order. For whether the law reaches a small shop, see the EAA small business exemption. On WordPress instead? What an accessibility plugin can and can’t fix is the same question there.
Eight checks.
Where each fix lives in Squarespace.
Answer for your own site, with the answers starting as a typical small one, and the list reorders to put what stops a visitor finishing a task first. Each item has the Squarespace route, the catch that is particular to Squarespace, and what a toolbar would do about it. Nothing leaves your browser.
2 to fix · 5 to test
Start here: Give every form field a visible label.
A toolbar would change nothing for 5 of these 7 and only add a visitor setting for the other 2.
-
Test this Layout · Level A
Tab through every page
Put the mouse away, load the page and press Tab. The first press should open a Skip to Content link; keep pressing and watch the outline move through your menu, links, buttons and form fields in a sensible order.
The Squarespace catch. You can’t change the focus outline’s colour or thickness, and Squarespace says to update your browser if it doesn’t show. Its support doesn’t cover custom code you add, so a keyboard problem caused by an embed or script is yours to fix.
A toolbar: A visitor setting only. A Highlight Focus setting, for visitors who find it. It can’t make a control you can’t reach with Tab work, and Squarespace’s own outline is already on.
WCAG 2.2: 2.1.1 Keyboard, 2.4.7 Focus Visible
Squarespace help: Inclusive design, Built-in features, Code injection
-
Fix this Form block · Level A
Give every form field a visible label
Edit the form block and check that each field has a clear label. Add a text block above the form with short instructions on what visitors need to fill in. Squarespace says placeholder text shouldn’t replace the label.
The Squarespace catch. Squarespace’s checkout fields come pre-labelled, but that covers checkout only. A form block is as clear as the labels you wrote.
A toolbar: Nothing. Builderify’s toolbar leaves your forms alone. Some widgets patch missing labels in the browser (Accessora says so for its Enterprise plan), which changes neither what a sighted visitor sees nor the form in your editor.
WCAG 2.2: 3.3.2 Labels or Instructions, 1.3.1 Info and Relationships
Squarespace help: Inclusive design, Built-in features
-
Fix this Content · Level A
Add alt text to every image that carries meaning
Open the Pages panel, click the page, then Edit. Click the image block, then the pencil icon, open the Content tab and fill in Image alt text; it saves by itself. Describe the image as you would to someone who couldn’t see it, and leave out “photo of”. If the image links somewhere, say where: “Engaged couple laughing. Links to engagement photos.” Version 7.1 can also suggest alt text for you to edit: open the SEO/AI Visibility panel, click Improve with AI under Your SEO Completion Score, and review the images it flags. It works in Fluid Engine sections only, and auto layout sections have their own Image alt text field under Edit Content.
The Squarespace catch. An image block with no alt text is invisible to screen readers, but other images borrow text: a page’s featured image uses its file name, a gallery section image its description, a blog or event image its title and a product image its name. A file name like IMG_4729.jpg counts as alt text, so a missing description can look filled in. Section background images and a video block’s custom thumbnail can’t take alt text at all.
A toolbar: Nothing. Nothing in Builderify’s toolbar: only you know what an image is for on that page. Accessora says its Growth and Enterprise plans draft alt text with AI and serve it live, from its script rather than from your Squarespace image.
WCAG 2.2: 1.1.1 Non-text Content
Squarespace help: Alt text, Audio, images and video
-
Test this Content · Level A
Read your links out of context
Read only the links on a page, in order. Does each one make sense on its own? Buttons and image links need the same test.
The Squarespace catch. A link that is an image needs alt text that says where it goes as well as what it shows, because that text is the link’s name.
A toolbar: Nothing. An Underline Links setting makes links easier to spot for a visitor who turns it on. The words stay what you wrote.
WCAG 2.2: 2.4.4 Link Purpose (In Context)
Squarespace help: Inclusive design, Audio, images and video
-
Test this Content · Level A
Look at each page’s heading outline
Squarespace suggests the free WAVE tool for finding broken heading structures. Run it on the live page, and look for bold lines that act as headings.
The Squarespace catch. Squarespace also creates heading tags for some key text itself, such as blog post titles, depending on your version and the type of text. A page can have headings you never typed, so check the live page and not only the editor.
A toolbar: Nothing. An Underline Titles setting marks headings on screen for a visitor. It doesn’t change a heading’s level or turn bold text into a heading.
WCAG 2.2: 1.3.1 Info and Relationships, 2.4.6 Headings and Labels
Squarespace help: Inclusive design, Heading tags, Built-in features
-
Test this Page settings · Level A
Read each page’s title
Open three of your pages in separate browser tabs and read the tab titles. Can you tell them apart?
The Squarespace catch. An SEO title replaces the page title for screen readers, so the words you wrote for search engines are what a screen-reader user hears first.
A toolbar: Nothing. Nothing a toolbar can do: the title is yours.
WCAG 2.2: 2.4.2 Page Titled
Squarespace help: Inclusive design
-
Test this Site styles · Level AA
Run a contrast check on text and buttons
Squarespace suggests the WAVE tool for colour contrast issues. Then look at text over images yourself: automated tools can’t measure text over a photo.
The Squarespace catch. Squarespace says not to rely on colour alone to convey information. A red “required” or a green “in stock” needs words as well.
A toolbar: A visitor setting only. Increase Contrast, Black & White and Invert Colors, for visitors who turn them on. Your own colours stay as they are for everyone else, so they still have to pass.
WCAG 2.2: 1.4.3 Contrast (Minimum), 1.4.1 Use of Color
Squarespace help: Inclusive design, Built-in features
-
Looks fine Content · Level A
Captions and motion: you said yes
Worth a look again after big edits. Play every video with the sound off, scroll each page watching for background movement, and play any GIF to see whether it flashes.
The Squarespace catch. On version 7.1, Squarespace says visitors who turn on reduced motion in their device settings see some animations, such as background image effects and background art, stop. It says nothing of the kind for 7.0.
A toolbar: A visitor setting only. A Disable Animations setting that stops motion for visitors who turn it on. It can’t add captions to a video it can’t hear.
WCAG 2.2: 1.2.2 Captions (Prerecorded), 2.2.2 Pause, Stop, Hide, 2.3.1 Three Flashes or Below Threshold
Squarespace help: Audio, images and video, Built-in features
Installing a toolbar
Your plan can take a toolbar
Code Injection is on your plan, so a script goes in once and loads on every page except checkout, where Squarespace doesn’t run code. The eight fixes above are editor changes: they stay whether or not any script loads.
These are eight checks Squarespace’s own help pages cover, not every WCAG 2.2 criterion: the WCAG 2.2 checklist has all 55 at levels A and AA. Squarespace says its guidance is a resource and not legal advice, and so is this page. The checker doesn’t read your Squarespace account; it only sorts your answers. A page that passes all eight can still fail others.
Seven things Squarespace already does,
and what stays yours.
A widget that repeats these adds little. Knowing the line between them and your own content is what makes the self-check short.
| Built in | What Squarespace says | Still yours | Source |
|---|---|---|---|
| Skip to Content link | Opens by itself the first time a visitor presses Tab; the spacebar then jumps past the header. | What comes after the jump: headings, links and layout in a sensible order. | Help page |
| Keyboard focus outline | Appears on links and form fields when a visitor tabs through the page. You can’t change its colour or thickness. | Whether every control can be reached, and whether blocks overlap. | Help page |
| Checkout fields and buttons | Checkout fields come with clear text labels, and the main buttons use descriptive labels. | Every form block you build yourself, and any text you add around checkout. | Help page |
| Heading tags | Formatting text as Heading 1 to 4 applies a real heading tag, and Squarespace creates some itself, such as blog post titles. | Which text is a heading, in what order, under one Heading 1. | Help page |
| Reduced motion (version 7.1) | Visitors who turn on reduced motion in their device settings see some animations stop, such as background image effects and background art. | Videos, GIFs and any motion Squarespace doesn’t list. | Help page |
| Alt text fields and tools | Each image block, gallery section and auto layout has its own field, the SEO report flags images with none, and on 7.1 an AI tool suggests descriptions in Fluid Engine sections. | Writing and checking every description, including collection items the report doesn’t scan. | Help page |
| An accessibility statement and a VPAT | Squarespace publishes both for its platform and points to them when someone asks for proof of accessibility. It also says it’s not legal advice, and that you are responsible for making sure your site meets the law that applies to your business. | The pages you build and the law that applies to you. | Help page |
Read on 8 November 2026. Squarespace’s accessibility statement and VPAT are published by Squarespace and not read here; open them from its built-in features page. A toolbar sits on top of all of this and replaces none of it.
Background images are the Squarespace gap to know about. Squarespace says section background images can’t take alt text, because decorative ones don’t need a description. If the picture carries meaning, such as a menu or a price list, put it in an image block, where Image alt text is a field, and say the same thing in text on the page.
The visitor-side settings are a different job. Our guide to dyslexia-friendly fonts for websites covers what the research says about the typeface you choose for everyone, and the accessibility statement template shows how to mention a toolbar honestly, as extra help and not as a compliance claim.
Five steps,
fixes last.
The screens named here are Builderify’s; the Squarespace half is the same for any script-based toolbar. For the same steps on other platforms, how to add custom code to your website has the menu path for each.
Builderify’s accessibility toolbar is free to start: every account gets 250 free credits a month, and page loads with the widget on them cost 10 credits per 1,000, so the free credits cover about 25,000 page loads a month. Packs start at $9, never expire and carry no monthly fee; see pricing.
The honest limits: the toolbar is a button over the corner of your page that a visitor has to find and choose to use, it shows “Powered by Builderify”, and it doesn’t make a site compliant with any law. Outside the tools, every fix on this page is yours either way. To hear about what is still in the way, a support ticket form in the same website widget gives each report a reference and a status.
-
1
Check your plan
Squarespace lists code injection on the Core, Plus and Advanced plans and on some legacy plans. Jotform’s route, a code block that runs a script, sits on the same plans. Without one of them there is nowhere for a script to go.
-
2
Switch the module on and copy your snippet
In your Builderify dashboard, switch on Accessibility, open Install Builderify and copy your snippet. It is the same line for every page and every platform.
-
3
Paste it into Header and save
Open the Code Injection panel (on a 7.1 site: Pages, then Custom Code at the bottom, then Code Injection; Squarespace’s page names the panel but not the route). Paste the whole snippet into Header, leave anything already there, and click Save.
-
4
Look at it on the live site
Squarespace can switch scripts off in its preview, and says to open your site’s address in a private window to see custom code. Then press Check now in Install Builderify. Checkout pages don’t run code, so the toolbar won’t show there.
-
5
Then make the eight fixes
Go through the self-check above. The toolbar is the part visitors can switch on; the fixes are the part that is yours.
From Squarespace’s code injection and custom code help pages, 8 November 2026. Squarespace’s support doesn’t cover problems caused by custom code, so keep a note of what you pasted and where. Translating the site too? Translating a Squarespace website says what that needs.
Squarespace accessibility widgets, before you ask.
Yes, several are free to start, and they install the same way: a script pasted into Squarespace's Code Injection panel, which Squarespace lists on the Core, Plus and Advanced plans and on some legacy plans. Builderify's accessibility toolbar is free to start: every account gets 250 free credits a month and page loads cost 10 credits per 1,000, so the free credits cover about 25,000 page loads a month. Jotform calls its Squarespace widget free as well. Whichever you pick, it adds controls for visitors and does not edit your pages.
No. A widget gives visitors controls and leaves the pages as they were, and whether a site meets a standard depends on the pages. Squarespace says its own accessibility guidance is not legal advice, that it does not advise on the laws that apply to your business, and that you are responsible for making sure your site complies. The eight checks on this page are editor fixes, and the guides on overlays and on the European Accessibility Act explain where the law stands.
Into the Code Injection panel (on a 7.1 site: Pages, then Custom Code at the bottom, then Code Injection), in the field the widget's instructions name. Header goes into the head of every page and Footer before the closing body tag; Builderify's snippet goes in Header and Accessora's Squarespace page says Footer. Checkout pages don't support code, so a script-based toolbar won't show there. Open your live address in a private window to see it, because Squarespace can switch scripts off in its preview.
No. Squarespace says section background images and the custom thumbnail of a video block don't support alt text, and that purely decorative images don't need a description. If an image carries meaning, such as a menu or a price list, put it in an image block, where Image alt text is a field, and say the same thing in text on the page.
Squarespace says its sites show a keyboard focus outline when a visitor presses Tab and open a Skip to Content link on the first press, that checkout fields are pre-labelled, and that formatting text as a heading applies a real heading tag. You can't change the focus outline's colour or thickness. On version 7.1, visitors who turn on reduced motion in their device settings also see some background animations stop. Alt text, link wording, heading order, form labels and contrast are left to you.
Sources
Read on 8 November 2026. Builderify’s own figures are from its pricing and Accessibility pages.
- Squarespace Add alt text to images for accessibility and SEO (updated 1 Oct 2026)
- Squarespace Make your site accessible with built-in features (updated 22 Jul 2026)
- Squarespace Make your site accessible with inclusive design practices (updated 23 Sep 2026)
- Squarespace Making audio, images, and videos more accessible (updated 15 Oct 2025)
- Squarespace Heading tags and Squarespace (updated 14 Aug 2025)
- Squarespace Customize parts of your site with code injection (updated 16 Sep 2026)
- Squarespace Add custom code to your site (updated 27 Aug 2026)
- Accessora Accessibility widget for Squarespace
- Jotform How to add a free accessibility widget to Squarespace
More on website accessibility
All 7 website accessibility guides- Accessibility Overlays and the accessiBe FTC Order Do accessibility overlays make you compliant? The $1M accessiBe FTC order, what a widget can fix in WCAG 2.2, overlay lawsuits, and a claim checker.
- Dyslexia Friendly Font: What Helps on a Website Which dyslexia friendly font to use on a website, what the research says about OpenDyslexic, the BDA spacing rules, and a free font tester with the CSS.
- EAA Small Business Exemption: Does It Apply? The EAA small business exemption covers microenterprises providing services, not products. Check headcount, turnover, group firms and EU sales for free.
- WCAG 2.2 Checklist: 55 AA Checks in Plain English A free WCAG 2.2 checklist for small sites: all 55 level A and AA criteria in plain English, how to check each one, and what changed from WCAG 2.1.
- Accessibility Statement Template: Free Generator Free accessibility statement template and generator: WCAG 2.2 status, known issues, contact details, and what the European Accessibility Act requires.
- WordPress Accessibility Plugin: Which Kind You Need Which WordPress accessibility plugin do you need? Checkers find issues, toolbars don't fix them. Free 12-point triage with WCAG 2.2 fixes and an EAA check.
The Builderify module behind these guides: Accessibility (free accessibility widget).
Stop losing the visitors
you already paid for.
More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.