Accessibility overlays promise a one-line fix: paste a script, a widget appears, and your website is “compliant”. It is an attractive pitch for any business worried about ADA lawsuits or the European Accessibility Act. The reality is more nuanced. A widget can genuinely help visitors, but on its own it does not make your website meet WCAG, and regulators and courts have started to say so.
This guide explains what an accessibility overlay actually does, where it falls short, and how to combine a widget with real fixes so you get both a better experience for visitors and a defensible compliance position.
What is an accessibility overlay?
An overlay is a piece of JavaScript that runs on top of your website after it loads. Most overlays add a floating button that opens an accessibility menu, and many also try to repair problems automatically in the visitor’s browser, for example by guessing alt text for images or adding labels to unlabelled buttons.
Typical overlay features include:
- Text size, spacing and readable fonts
- Contrast and colour adjustments
- Reading guides, cursor enlargement and animation stopping
- Automatic “fixes” applied to the page as it renders
The first three groups are visitor preferences. The fourth is where the problems start.
Why an overlay alone isn’t enough
1. WCAG is about your code, not a layer on top of it
The Web Content Accessibility Guidelines describe how your content and code must behave: images need meaningful text alternatives, form fields need labels, focus order must be logical, and every function must work with a keyboard. When an audit or a legal demand letter tests your site, it tests the underlying page. A script that patches the page in some browsers does not change the source that assistive technology and auditors rely on.
2. Automated repair can’t make human judgements
Writing useful alt text, choosing a sensible reading order or rewriting an unclear error message all need context. Software can guess, but a guess such as “image of person” on a product photo does not help a blind shopper decide what to buy. Many issues also live in places a script cannot reach reliably, such as PDFs, embedded videos and third-party checkouts.
3. Overlays can conflict with assistive technology
Screen reader users already have tools tuned to their needs. Some overlays change keyboard behaviour or inject content that clashes with those tools. That is one reason more than 700 accessibility professionals have signed the public Overlay Fact Sheet warning against relying on overlays for compliance.
4. Regulators and plaintiffs have noticed
In 2025 the US Federal Trade Commission required an overlay vendor to pay $1 million over claims that its product could make any website compliant. Industry trackers have also reported that a significant share of US digital accessibility lawsuits now name websites that already had an overlay installed. Having a widget is not, by itself, a defence.
Where an accessibility widget does help
None of this means widgets are useless. A well-built accessibility menu gives visitors real control: people with low vision can enlarge text, people with dyslexia can switch to a more readable font, and people with ADHD or vestibular disorders can stop animations. Those preferences make a site more comfortable to use, and many visitors appreciate them.
The key is to treat the widget as a visitor convenience, not as your compliance strategy. The Reguweb accessibility widget is built on that principle. It offers profiles such as low vision, dyslexia and ADHD, plus tools like a reading guide and text magnifier, while the rest of the platform finds and fixes the issues in your actual code.
Overlay only vs a real compliance programme
| Capability | Overlay only | Real compliance programme |
|---|---|---|
| Visitor preference tools | Yes | Yes |
| Finds issues across every page | Rarely | Yes, with scheduled scans |
| Fixes the underlying code | No | Yes |
| Manual testing with screen readers | No | Yes |
| VPAT and accessibility statement | No | Yes |
| Evidence of ongoing effort | No | Yes, with scan history and reports |
How to build compliance that holds up
- Scan every page. Run an automated WCAG 2.2 scan across your whole site, not just the home page. Automated checks quickly catch issues such as missing labels, low contrast and empty links.
- Prioritise by risk. Fix the issues that block people first: checkout, contact forms, navigation and login. These are also the journeys most often cited in complaints.
- Fix the source. Correct templates, components and content in your CMS so the fix applies everywhere and survives the next update.
- Test manually. Use a keyboard and a screen reader on your key journeys, or have specialists do it. Manual testing finds the problems automation misses.
- Document your work. Publish an accessibility statement and keep reports. If you sell to enterprises or government, prepare a VPAT.
- Monitor continuously. New pages, plugins and content can reintroduce problems. Schedule regular scans and retest after releases.
- Offer visitor tools. Add an accessibility widget for comfort and personalisation, on top of, not instead of, the steps above.
Frequently asked questions
Will an accessibility widget stop ADA lawsuits?
No. A widget can improve the experience for some visitors, but lawsuits and demand letters focus on barriers in your actual website. Fixing those barriers and documenting your work is what reduces risk.
Should I remove my overlay?
Not necessarily. If it offers useful preferences and doesn’t interfere with screen readers, it can stay. Just don’t rely on it for compliance, and switch off any “automatic repair” features that change how assistive technology reads your page.
How long does real remediation take?
It depends on the size of your site. Many small business sites can fix their highest-risk issues within a few weeks once they know exactly what to change. A full audit gives you that list.
Find out where your website stands
Reguweb combines the parts that matter: an accessibility widget for visitors, WCAG 2.2 scanning across every page, AI-assisted fixes, expert manual audits and the documentation to prove your progress. Run a free scan to see your WCAG and SEO scores in about a minute, or start a 14-day free trial. No credit card needed.
On this page
Is your website compliant?
Get your WCAG 2.2 and SEO scores in about 60 seconds. No sign-up needed.
