Accessibility overlays don’t ensure ADA compliance because they bolt a JavaScript widget onto a finished page instead of fixing the underlying code. They can’t reliably repair broken HTML, ARIA, keyboard traps, or color contrast, they frequently conflict with assistive technology, and courts have shown overlaid sites are still sued. The dependable fix is manual remediation.
What an overlay actually is
An accessibility overlay (sometimes called an accessibility widget or plugin) is a snippet of third-party JavaScript you paste into your site. At page load it scans the DOM and tries to auto-correct issues or layer on a toolbar with options like bigger text, a high-contrast theme, or a “screen reader” mode.
The pitch is seductive: one line of code, instant compliance, a tidy “ADA accessible” badge. The reality is that an overlay never touches the source of the problem. Your underlying markup, structure, and design stay exactly as they were — the widget just paints over them at runtime. That distinction is the whole reason overlays don’t reliably work.
The technical reasons overlays fail
ADA-related web claims are measured against the WCAG 2.1 AA standard, built on the POUR principles — content must be Perceivable, Operable, Understandable, and Robust. Overlays struggle on every one.
1. They don’t fix your source code
The barriers that matter live in your HTML, CSS, and JavaScript: a button that’s really a <div>, an image with no alt text, a form field with no label, a heading order that jumps from H1 to H4. A remediation has to change that markup. An overlay can’t — it only manipulates the rendered page after the fact, and it has no reliable way to know what a decorative image versus an informative one should say, or what a mislabeled control is supposed to do. Guesswork at runtime is not conformance.
2. They conflict with assistive technology
This is the most damaging failure. People who are blind or low-vision already run their own assistive technology — screen readers like NVDA, JAWS, and VoiceOver — tuned to their needs. An overlay that injects its own ARIA, hijacks keyboard focus, or adds a competing “screen reader mode” can actively fight the user’s software. The result is duplicated announcements, lost focus, and controls that stop responding to keyboard navigation. For the very users overlays claim to help, they can make a site harder to use.
3. They miss most of WCAG
Automated tooling — which is all an overlay is — can only catch a fraction of WCAG success criteria. Industry testing consistently finds automated detection identifies roughly a third of issues at best. Judgment-based criteria (is this alt text meaningful? does the focus order make sense? is the error message understandable?) require a human. That’s the entire case for manual accessibility testing over a script, and why automated vs manual testing is the foundational decision.
4. They’re fragile and Robust-unfriendly
The “R” in POUR is Robust — content should work across browsers and assistive tech. An overlay adds a runtime dependency that can break with browser updates, slow your page, and behave differently for different users. Real code fixes are baked into the page and degrade gracefully; a widget is one more thing that can fail.
| Accessibility task | Overlay widget | Manual remediation |
|---|---|---|
| Fix invalid or missing HTML semantics | No — runtime only | Yes — in source |
| Write meaningful alt text & labels | Guesses | Human-authored |
| Repair color contrast in the design | Adds a theme on top | Fixed in CSS |
| Correct ARIA roles and states | Can worsen | Corrected properly |
| Verify with NVDA / JAWS / VoiceOver | No | Yes |
| Produce a defensible VPAT | No | Yes |
The legal reasons overlays fail
Here’s the part that surprises business owners most: an overlay can increase your legal exposure rather than reduce it.
- Lawsuits continue against overlaid sites. Thousands of ADA web lawsuits and demand letters are filed in the U.S. each year, and a large share name sites that were actively running a popular overlay. Plaintiffs’ experts test with real assistive technology — and a widget that leaves barriers in place gives them their cause of action. See how an ADA demand letter actually unfolds.
- No regulator endorses overlays. The DOJ has never approved any overlay or plugin as a way to meet ADA Title III, and the same is true under Section 508 for federal contexts. Guidance points to making the actual site accessible — which in practice means conforming to WCAG. (For how these frameworks relate, see ADA vs Section 508 vs WCAG.)
- A badge isn’t a defense. Claiming compliance you don’t have can read as misleading. An “accessible” badge over an inaccessible site doesn’t help in a demand-letter exchange — and may not help your credibility with a court either.
- Serial plaintiffs know the pattern. Some firms specifically target sites running known overlays because the barriers are predictable. Read more on serial ADA plaintiffs.
This page is educational, not legal advice. For your specific situation, consult an attorney who handles ADA matters.
The accessibility community’s consensus
This isn’t a fringe opinion. Disability advocates, screen-reader users, and accessibility professionals have publicly and repeatedly stated that overlays do not deliver compliance and can harm usability. Hundreds of accessibility practitioners have signed open statements against overlay products, and the W3C / WAI (w3.org/WAI) and groups like WebAIM (webaim.org) consistently direct organizations toward fixing the underlying site rather than installing a widget. When the people who actually use assistive technology say a product makes their lives harder, that’s the signal that matters.
What to do instead
The good news: every barrier an overlay tries to mask is genuinely fixable in your code — and once fixed, it stays fixed and works for everyone.
- Audit honestly. Start with a real accessibility audit against WCAG 2.1 AA, combining automated scanning with manual testing and screen-reader verification. Not sure where you stand? Check if your website is ADA compliant.
- Remediate the source. Fix the actual HTML, ARIA, contrast, forms, and keyboard support. That’s what accessibility remediation means — and it’s how a site becomes an ADA-compliant website you can stand behind.
- Document and maintain. Keep your accessibility statement current and monitor for regressions as your site changes.
Overlays promise a shortcut that doesn’t exist. Curbcut takes the opposite, anti-overlay approach: we fix your real code by hand so your site is accessible to screen-reader and keyboard users — and defensible if a demand letter ever lands. Start with a free accessibility scan to see exactly what an overlay would have left behind.