Accessibility Widgets Truth - What Overlays Can and Cannot Do
Accessibility widgets, often called overlays, are small scripts that add a toolbar to your website so visitors can adjust text size, contrast, spacing and more. The honest truth is this: a good accessibility widget can genuinely help many visitors personalise their experience, but no widget can make an inaccessible website compliant on its own. If a vendor promises instant ADA or WCAG compliance from one line of code, be very careful.
We build an accessibility widget at Openwise, so we have a stake in this topic. That is exactly why we want to be clear about what these tools can and cannot do.
What accessibility widgets actually are
There are two broad kinds of products sold under the "accessibility widget" or "overlay" label:
- Personalisation toolbars. A menu of visitor-controlled settings: bigger text, high contrast, dark mode, dyslexia-friendly fonts, reading guides, pausing animations, larger cursors, text spacing and read-aloud.
- Automated "remediation" overlays. Scripts that claim to detect and repair accessibility problems in your code automatically, often using AI, for example by guessing alt text or injecting ARIA attributes.
The first kind offers user preferences. The second makes claims about fixing your website, and that is where most of the controversy lies.
What accessibility widgets do well
Used honestly, a widget is a convenience layer that gives visitors more control:
- Low vision users can enlarge text or boost contrast without learning browser settings.
- People with dyslexia may find a dyslexia-friendly font, extra letter spacing or a reading guide helpful.
- People sensitive to motion can pause animations.
- People who are easily distracted can use a reading mask to focus on one section.
- Older visitors who never touch browser zoom can find a big, obvious accessibility button.
Many of these adjustments are possible with browser or operating system settings, but plenty of people do not know they exist. A clearly labelled toolbar puts them one click away.
What no accessibility widget can fix
The barriers that matter most to many disabled users live in your HTML, design and content. A script running on top of the page cannot reliably understand your intent, so it cannot fix these properly:
| Problem | Why a widget cannot reliably fix it |
|---|---|
| Missing or poor alt text | Only you know what an image means in context; AI guesses can be wrong or misleading |
| Unlabelled form fields | A script cannot know what each field is truly for |
| Custom controls built from divs | Real keyboard behaviour needs real code changes |
| Keyboard traps in embeds | Third-party iframes are often out of the script's reach |
| Illogical heading structure | Fixing it requires understanding the content |
| Inaccessible PDFs and documents | They are separate files outside the page |
| Video without captions | Accurate captions need human review |
| Confusing error messages | Good wording requires knowing the form's logic |
| Low contrast in the brand design | A visitor toggle helps, but the default design still fails |
Also, many screen reader users already have their own tools configured exactly the way they want them. A widget offering text-to-speech does not help them; what helps is correct semantic code. Some accessibility advocates and users have publicly criticised overlays for interfering with their assistive technology.
For the code-level fixes, see our guides to writing alt text, keyboard accessibility and accessible forms.
The legal reality for accessibility widgets
Two facts are worth knowing.
First, many US web accessibility lawsuits have targeted websites that already had an overlay installed. Having a widget has not, by itself, protected businesses from being sued. Courts and plaintiffs look at whether disabled people can actually use the site.
Second, regulators have started looking at marketing claims. In January 2025, the US Federal Trade Commission (FTC) announced a proposed order requiring accessiBe to pay $1 million over misleading claims that its AI tool could make websites WCAG compliant.
A widget is not a compliance certificate. Compliance depends on whether your actual website meets the standard.
Laws vary by region. In the US, read our overview of ADA compliance. In Europe, the European Accessibility Act now applies to many products and services. Indian businesses can check our guide to website accessibility law in India. None of these laws accept "we installed a plugin" as a defence on its own.
The right approach: three layers
The approach that actually works treats a widget as one layer, not the whole solution.
Layer 1: Fix the code
This is the foundation. Use semantic HTML, label every form field, write meaningful alt text, ensure keyboard access and visible focus, maintain colour contrast, caption videos, and structure headings logically. Work through our WCAG checklist and involve designers and content authors, not only developers.
Layer 2: Monitor continuously
Websites change every week. New pages, plugins, campaigns and content can introduce new barriers. Run automated scans regularly and combine them with manual testing, including keyboard checks and screen reader testing. Automated tools catch only part of the issues, so they support human review rather than replace it.
Layer 3: Offer personalisation
Once the foundation is sound, a widget adds real value by letting each visitor tailor the page to their needs. This is the honest role for a toolbar.
| Layer | What it does | Who does the work |
|---|---|---|
| Fix the code | Removes barriers at the source | Developers, designers, content teams |
| Monitor | Catches regressions and new issues | Automated scans plus manual testing |
| Personalise | Lets visitors adjust their experience | A widget, plus browser and OS settings |
This is how we position Openwise: the widget gives visitors tools like bigger text, contrast, dark mode, a reading guide and pause animations, while the free checker and dashboard help you find and fix the underlying issues. We say plainly that the widget helps but does not make a site compliant on its own.
How to evaluate an accessibility widget vendor
If you are choosing a widget, ask hard questions.
Red flags
- "Instant compliance" or "100% compliant" guarantees. No script can guarantee that.
- Fake or self-issued certification badges. There is no official ADA or WCAG certification for widgets. A badge saying "ADA certified" is marketing, not an official status.
- Litigation "protection" promises. Be skeptical of claims that a widget will stop you being sued.
- AI that "fixes everything". Automated repairs of alt text and ARIA can introduce new errors.
- No way to disable it. Visitors who rely on their own assistive technology should be able to ignore or close the toolbar easily.
- Pressure to skip code fixes. A good vendor encourages you to fix the source.
Green flags
- Clear, honest wording about what the tool does and does not do.
- The widget itself is keyboard accessible and works with screen readers.
- Settings that respect user choice and persist sensibly.
- Tools to find real issues, such as an accessibility checker or reports.
- Transparent pricing and an easy way to remove the script.
Test the widget yourself: tab through it with the keyboard, try it with a screen reader, and check it does not hide content or break your layout. If you use a CMS, our WordPress accessibility guide covers plugin choices.
Frequently asked questions
Do accessibility widgets make a website ADA compliant?
No widget can make a website ADA or WCAG compliant on its own. Compliance depends on your underlying code, design and content. A widget can add helpful personalisation options for visitors, but issues like missing alt text, unlabelled forms and keyboard traps must be fixed in the site itself.
Are accessibility overlays bad?
It depends on what they claim and how they behave. Personalisation toolbars can genuinely help some visitors. Problems arise when vendors promise instant compliance, when automated fixes introduce errors, or when the overlay interferes with a user's own assistive technology. Judge a tool on honesty and real usability.
Can I still be sued if I have an accessibility widget?
Yes. Many US web accessibility lawsuits have targeted sites that already had overlays installed. What matters is whether disabled people can actually use your website, so fixing the underlying issues is the best way to reduce risk.
What did the FTC say about accessiBe?
In January 2025, the US Federal Trade Commission announced a proposed order requiring accessiBe to pay $1 million over misleading claims that its AI tool could make websites WCAG compliant. It is a clear signal that compliance claims in marketing are being scrutinised.
Is there an official ADA certification for websites?
No. There is no official government certification that a website is ADA compliant, and no official badge for widgets. Be wary of vendors displaying certification seals; an independent audit and ongoing testing are what actually demonstrate your accessibility work.
Should I use a widget at all?
A widget is worth using if you treat it as an extra layer for visitor comfort, not as your accessibility strategy. Fix your code first, monitor regularly, and then offer personalisation on top.
Conclusion
The truth about accessibility widgets is simple: they are useful for personalisation and harmful only when sold as a shortcut to compliance. Fix the code, keep monitoring, and offer visitor tools on top. To see where your site stands today, run a scan with our free accessibility checker and start with the issues it finds.
Is your website accessible?
Run a free WCAG check, or add the Openwise widget with one line of code.
Check my website Get started free