Do accessibility overlays work? An honest look for Squarespace owners

If you run a small restaurant or shop on Squarespace, you've probably seen the pitch. A little floating icon in the corner of a website, usually a person inside a circle. Click it and a panel slides out with buttons to enlarge text, change contrast, or pause animations. The companies selling these widgets say you can paste one line of code, walk away, and your site is handled.

It's a tempting story when you're short on time. It's also, in important ways, not true. This post walks through what overlay widgets actually are, why the accessibility community warns against them, the data showing that sites running overlays still get sued, and what genuinely helps. That means real fixes to your actual Squarespace content, honestly documented.

This is general information, not legal advice.

What an accessibility overlay actually is

An overlay (also called a widget or an accessibility plugin) is a snippet of JavaScript you add to your site. The script loads in the visitor's browser and tries to detect and patch problems on the fly. It guesses at missing image descriptions, adjusts code that screen readers read, and adds a toolbar of visual controls.

The key phrase is "on the fly." An overlay does not change your website. It changes what appears in the browser each time a page loads, by running code on top of your existing pages. Your underlying Squarespace content, the actual image alt text, button names, form labels, and heading structure, is left exactly as it was. If the script is removed, throttled, or fails to load, every adjustment disappears with it.

That distinction matters. It's the difference between repairing a leaky pipe and draping a tarp over the wet spot every morning.

What the alternative looks like

The honest alternative is to fix the source. That means editing the real content of your site so it's accessible whether or not any script is running.

On Squarespace, real source remediation looks like this.

• Writing genuine alt text on your images so a screen reader describes your dishes and your dining room, not "image_4837.jpg."
• Giving buttons and links real, descriptive names instead of "click here" or an empty link.
• Adding proper labels to your reservation and contact form fields.
• Fixing heading order so the page reads as a logical outline.
• Adding skip links and correcting ARIA and list markup where Squarespace leaves gaps.
• Handling color contrast through reversible Custom CSS and Site Styles, so your text meets WCAG 2.1 AA without breaking your brand.

None of this is injected at runtime. It lives in your site. Remove every third party script tomorrow and the work is still there. That permanence is the whole point.

Kat ADA is built on this model. You invite our team to your Squarespace site as an Administrator one time, and a specialist makes these edits inside your own editor. We don't inject a widget. We change the content.

Why the accessibility community is wary of overlays

This is not a vendor squabble. The strongest critics of overlays are the people overlays claim to help.

The clearest statement is the Overlay Fact Sheet (overlayfactsheet.com), an open letter signed by more than a thousand accessibility and disability community professionals, including people who build and test assistive technology every day. Its position is blunt. Overlay products do not deliver the accessibility they advertise, and in many cases they actively interfere with the assistive technology a disabled visitor already uses, such as their own screen reader or browser settings.

The National Federation of the Blind, the largest organization of blind Americans, has formally condemned overlay providers for misleading and unproven claims. When the people a product is supposedly built for are the ones asking you not to use it, that's worth pausing on.

Critics describe the same pattern again and again. A screen reader user lands on a site, the overlay tries to "help" by overriding or fighting their existing setup, and the experience gets worse, not better. An automated script guessing at context cannot match a human who understands what the page is actually for.

The data shows overlay sites still get sued

Here is the part that surprises most owners. Installing an overlay does not appear to reduce lawsuit risk, and the available data points the other way.

Digital accessibility firm UsableNet has reported that roughly a quarter of recent digital accessibility lawsuits were filed against sites that already had an accessibility widget or overlay installed, with the overlay itself cited as a barrier in those complaints. Plaintiffs' attorneys have learned that an overlay icon can flag a shortcut, and the underlying barriers are often still there to be tested.

For context, federal website accessibility lawsuits totaled roughly 3,117 in 2025, up about 27% year over year (Seyfarth Shaw, ADA Title III blog). Restaurants and food service rank among the most targeted industries. In EcomBack's 2025 dataset, "Restaurant, Food, Drinks" was the single most targeted category. If you operate in California, additional exposure comes from state court claims under the Unruh Civil Rights Act (Cal. Civ. Code Sec. 52), where statutory damages start at $4,000 per violation, plus attorney's fees. Again, this is general information, not legal advice.

The takeaway is not "panic." It's that the overlay shortcut does not buy down this risk, and may add to it.

What to do instead

If a widget is not the answer, what is? The honest path has three parts.

1. Fix the real source. Get the actual problems corrected in the content itself, meaning alt text, link and button names, form labels, heading order, skip links, ARIA, list markup, and color contrast through reversible CSS. Work that survives whether or not any script is loaded.

2. Keep watching, because sites change. Accessibility is not a one time project. Every time you add a menu, swap a hero image, or run a promo, you can introduce new issues. Kat ADA scans every page monthly using the axe-core engine against WCAG 2.1 AA, so regressions get caught instead of sitting there for months.

3. Be honest about what cannot be auto fixed, and document everything. Automated scans catch a meaningful subset of WCAG issues, not all of them, and some things genuinely sit outside what we can fix inside Squarespace. Think PDF menus, third party embeds like OpenTable, Tock, or Resy, video captions hosted on outside platforms, and certain theme level constraints. We itemize those in your report so nothing is hidden. Each month you receive a dated PDF good faith record of the diligence and ongoing effort you're putting in, documentation you can keep and share, including with your attorney. It is not a compliance certificate, and it is not lawsuit protection. We will not claim it is.

That combination, real fixes plus monthly monitoring plus honest documentation, is the thing an overlay only pretends to be.

See where your Squarespace site actually stands

You don't have to take any of this on faith. You can run a free, one time accessibility scan at katadaapp.com/scan. No credit card. Enter your URL and see your real violations against WCAG 2.1 AA for yourself.

If you want them handled, that's what we do. You invite our specialist one time, and we make the real fixes inside your own editor while you get back to running your business. Calm, honest, no widget in the corner.

We believe in an open, accessible web. We do not believe in extortion. If you've been on the receiving end of a scare tactic pitch or a demand letter, you're not alone, and you have a fellow owner in your corner.

Frequently asked questions

What is an accessibility overlay, and how is it different from a real fix? An overlay is a JavaScript widget that runs in the visitor's browser and tries to patch accessibility issues at page load. It does not change your underlying website. A real source fix edits your actual content, such as image alt text, button names, form labels, and heading order, so the improvement stays in place whether or not any script is running.

Will an accessibility widget protect me from a lawsuit? No tool or report can guarantee you will not face a lawsuit, and you should be skeptical of anyone who says otherwise. UsableNet has reported that roughly a quarter of digital accessibility lawsuits involve sites that already had an overlay installed, so a widget is not the protection it's often sold as. This is general information, not legal advice.

What is a better alternative to an overlay for a Squarespace site? Real source remediation. Fix the accessibility problems directly in your Squarespace content, monitor the site over time because content changes, and keep honest documentation of the work. Kat ADA makes the fixes for you inside your own Squarespace editor, scans monthly against WCAG 2.1 AA using axe-core, and provides a dated good faith record each month.

Can I check my own Squarespace site for free? Yes. Run a free one time scan at katadaapp.com/scan with no credit card. Enter your URL and see your real accessibility violations against WCAG 2.1 AA. The full report is free with an account, and done for you fixes are available on any plan.

---

Sources include the Overlay Fact Sheet (overlayfactsheet.com); National Federation of the Blind; UsableNet digital accessibility lawsuit data; Seyfarth Shaw, ADA Title III blog; EcomBack 2025 industry dataset; California Civil Code Sec. 52. This article is general information and not legal advice. No tool or report can guarantee accessibility outcomes or prevent a lawsuit.

Further reading. The complete Squarespace accessibility guide covers every fix in one place. Run a salon or spa? See accessibility for Squarespace salon sites.