Do Accessibility Overlay Widgets Actually Make My Website ADA Compliant?
A small icon appears in the corner of a website, usually a person in a circle. Click it and a panel opens: font size, contrast, a cursor that's easier to see, maybe a "reading guide" line. The site that installed it is often marketing itself as "ADA compliant" the moment the script loaded, sometimes with a badge to prove it. It's an appealing pitch: one line of code, a monthly fee smaller than a single hour of a developer's time, no code review, no waiting. It's also, on its own, not what it's being sold as.
What an accessibility overlay actually is
An overlay (sometimes called an accessibility widget or plugin) is a small script added to a page, on top of everything else already on the site. It doesn't touch your site's own HTML, CSS, or content. Instead it runs in the browser after the page loads and adjusts what it can reach at that point: it can resize text, swap in a higher-contrast color scheme, enlarge the cursor, pause animations, or offer a screen-reader-style read-aloud feature. Some go further and claim to use "AI" to automatically write alt text for images or fix contrast issues site-wide without a developer touching the code.
That's the whole model: a layer bolted on top of the site at runtime, not a change to the site underneath it. Turn the widget off, or load the page with JavaScript disabled, and the original page - problems included - is exactly what's still there.
What it can fix, and what it genuinely can't
Some of what an overlay does is real and can genuinely help a visitor who wants larger text or higher contrast on demand - that's a legitimate convenience feature, and there's nothing wrong with offering it. The trouble is the list of things it's marketed to fix but structurally cannot:
Alt text it has to guess at
An "AI-generated" alt text feature has no idea your product photo is a 1998 Ford F-150 with a new transmission, not just "a truck." Real alt text has to say what the image actually means in context - a job that needs someone who knows the business, not a script reading pixels after the fact.
Form fields with no real label
A widget can't retroactively attach a proper <label for="..."> to an input that never had one. It can make the placeholder text bigger. It can't make a screen reader announce what the field is actually for.
A broken keyboard tab order
If a positive tabindex or a custom menu throws keyboard-only visitors around the page out of order, an overlay running after the fact doesn't rewrite that structure. The trap is still there under the panel.
Heading levels that skip around
Screen reader users navigate by heading outline. An overlay can change how a heading looks. It can't decide, correctly, that an H3 should actually be an H2 in your document's real structure.
Every item on that list is exactly the kind of thing our own free audit checks for directly in the underlying code - see Is My Website ADA Compliant? for the full list of what actually shows up in real demand letters. An overlay sits one layer above all of it.
Why it's become a legal red flag, not a shield
The pitch behind most overlays is that installing one lowers your legal risk. What's actually played out in a growing number of real cases is closer to the opposite: a website carrying an overlay, with none of its underlying code actually fixed, can read to a plaintiff's attorney as proof the owner already knew accessibility was a live issue and chose the fastest, cheapest-looking option instead of a real fix. Disability advocates have raised the same objection from a different angle - some overlays actively interfere with the assistive technology a blind or low-vision visitor already has installed and knows how to use, replacing a tool the visitor trusts with one they didn't ask for.
None of that means every business with a widget gets sued, or that every widget is worthless as a small convenience feature. It means a widget alone is not the compliance strategy it's marketed as, and treating it as one can leave a business no better protected than it was before, sometimes with a new detail for a demand letter to point at.
What actually works instead
There's no shortcut around this one: the fix has to happen in the code itself, not in a layer running on top of it. In practice that means going through the real, specific list - alt text that actually describes each meaningful image, a real <label> on every form field, color combinations that hit the WCAG contrast ratio in your own CSS (not just an optional toggle), a keyboard tab order that follows the page visually, and heading levels used in order. Most of that list is a few hours of real, targeted work once it's identified, not a redesign.
That's exactly what our free audit measures - not whether a widget is installed, but whether the site itself, underneath everything, actually meets the bar. Enter your site below and we'll tell you plainly what's there, in plain English.
Frequently asked questions
Are accessibility overlay widgets illegal?
No, installing one isn't illegal. But an overlay widget doesn't satisfy WCAG or ADA on its own, and plaintiffs' law firms have specifically targeted sites that rely on one instead of fixing the underlying code - in some cases treating the widget itself as evidence the owner knew accessibility mattered and chose a shortcut.
Can an overlay widget make my site ADA compliant by itself?
No. A widget can adjust things it can see and control at runtime, like font size or a contrast toggle, but it cannot add real alt text to a photo it doesn't understand, attach a proper label to a form field, fix a broken keyboard tab order, or correct a skipped heading level. Those need a real code fix.
What should I do instead of installing a widget?
Find and fix the actual issues in the code: real alt text on every meaningful image, real labels on every form field, sufficient color contrast, a working keyboard tab order, and correct heading levels. A free automated audit will surface most of this in minutes.
If I already have an overlay installed, should I remove it?
Removing it doesn't undo anything, since it was never changing your underlying code in the first place. The safer move is to keep or drop the widget as you like, but treat the real code-level fixes as the actual project - they're what protects you and what genuinely helps visitors.
The cheapest way to find out
Run the free audit below. We measure your site's accessibility, speed, and SEO with Google's own tooling and email you a plain-English report - which findings are real, why they matter, and how they get fixed. If something needs fixing, it's a flat $149 for your fixable speed/image/SEO/broken-link issue, or $299 for everything, with before-and-after proof once it's done.