Sixty seven percent of accessibility practitioners surveyed rated overlay widgets as “not at all” or “not very” effective, according to the Overlay Fact Sheet, a resource maintained by accessibility practitioners and advocates critical of how this product category has been marketed. Among survey respondents who identified as having a disability themselves, that figure rose to 72%. Only 2.4% called overlays very effective. Those numbers are the clearest available snapshot of a debate that has been running in the accessibility field for years and shows no sign of settling.
What “overlay” means in this debate
An overlay, in the sense this controversy is about, is a script added to a website, usually a single line of JavaScript, that layers an adjustment interface on top of the existing site. Visitors get controls for things like text size, contrast, and reading guides, and some products attempt automated code level fixes, generating missing alt text or adjusting markup, without a developer touching the underlying site. The pitch is speed and simplicity: install once, get broad accessibility improvements without a code audit or a development sprint.
Where the criticism comes from
The core objection isn’t that automated adjustment tools are worthless. It’s that some vendors in this category have marketed overlays as delivering full, or close to full, legal compliance from that single script install, which accessibility practitioners argue overstates what any automated layer can actually do. Automated detection, by its nature, can only catch a subset of real accessibility barriers: it can flag a missing label, but it can’t judge whether a screen reader user can actually complete a multi step form, and it generally can’t fix a fundamentally inaccessible custom component without a developer rebuilding it. There have also been documented reports, discussed widely across the accessibility community, of certain overlay products interfering with assistive technology that a disabled visitor was already using before the overlay loaded, which is arguably worse than doing nothing.
What the practitioner survey actually found
The Overlay Fact Sheet’s numbers matter because they come from the people closest to the problem: accessibility practitioners who test sites professionally, and disabled users who rely on the assistive technology overlays are meant to complement. A 67% “not very effective or worse” rating from practitioners, rising to 72% among disabled respondents, is a strong signal that the skepticism isn’t limited to a handful of vocal critics. It reflects something closer to a professional consensus, at least around the specific claim that a widget alone constitutes real compliance.
Automation itself isn’t the villain
It’s worth separating two different claims that get conflated in this debate. One is “automated detection and adjustment tools have zero value,” which very few serious critics actually argue. The other is “a widget alone, marketed as a standalone fix, is enough to make a site compliant,” which is the claim the practitioner survey and years of documented criticism push back on. Automated scanning genuinely does catch real issues quickly and cheaply, as the WebAIM Million study demonstrates every year by finding widespread, detectable failures across the web. The dispute is about what automation alone can’t do, not whether it does anything at all.
How some vendors have responded
Part of the industry’s response to this criticism has been to stop selling automation as a standalone product. Wawsome pairs its adjustment widget with continuous automated monitoring and a manual, human reviewed checker rather than presenting the widget alone as sufficient. AudioEye takes a similar structural approach, combining automated scanning with human-in-the-loop testing and managed remediation. accessiBe, one of the best known names in the overlay category, was ordered by the U.S. Federal Trade Commission in 2025 to pay $1,000,000 to settle charges of misleading claims about how much accessWidget could automatically fix and about paid customer reviews, which is a concrete example of the marketing overreach this controversy has been about for years, playing out as an actual enforcement action.
What this means if you’re evaluating a widget
The practical takeaway isn’t “avoid every product with the word widget in its marketing.” It’s to ask any vendor, plainly, what percentage of accessibility work their tool handles automatically versus what still requires manual review, and to be wary of any answer that claims full compliance from installation alone. A widget that’s honest about its limits and pairs automation with real human testing is a genuinely different proposition than one marketed as a complete, one-script fix, even though both might look similar from the outside.
The debate isn’t going away soon
Overlay marketing tends to lean on the same pitch: install one script, get broad accessibility improvements without a development sprint or a code audit. That pitch is appealing precisely because manual remediation is genuinely slower and more expensive, which is exactly why the controversy persists rather than resolving. Neither side of the debate is arguing in bad faith. Vendors selling automated tools are responding to real demand from businesses that want a fast, affordable starting point, and practitioners raising concerns are responding to real evidence that a script alone doesn’t reliably produce a site that works for disabled users. Until that tension between speed and thoroughness gets resolved by better technology, better regulation, or both, expect the debate documented in surveys like the Overlay Fact Sheet’s to keep showing up every time a new overlay product launches.