Running a site
Do accessibility overlay widgets actually work?
18 July 2026 · 6 min read
On this page
Overlays are the small accessibility icon in the corner of a site that opens a panel offering larger text, higher contrast and a "screen reader mode". They are marketed as one line of JavaScript that makes a site compliant.
The short version: they help slightly with some things, do not fix the underlying problems, and are actively opposed by a large part of the disability community. Here is the detail.
What they can do
To be fair, some genuinely offer a few useful features:
- Increasing text size or spacing
- Adjusting contrast or applying a dark mode
- Highlighting links
- Reducing animation
- Pausing carousels
For a sighted user with mild low vision who does not know their browser can already do most of this, an overlay can be mildly useful.
What they cannot do
Here is the problem. An overlay is JavaScript that runs after your page loads and tries to guess what your markup means.
It cannot write meaningful alt text. Automated image description produces "a person standing near a building" where the meaningful alternative was "Dr Sarah Chen, practice partner". Sometimes it is wrong, which is worse than nothing.
It cannot fix a broken heading structure, because it does not know what your page is actually about.
It cannot make a div into a real button. It can add ARIA attributes, and if the element still does not respond to Enter or Space, the screen reader now announces a button that does not work.
It cannot fix keyboard traps, which are the most blocking failure of all.
It cannot caption your videos.
And critically, most screen reader users already have their own configured software. An overlay attempting to intervene in that frequently makes the experience worse rather than better.
What the community says
This is not a balanced-opinions situation. Thousands of accessibility practitioners and disabled users have signed public statements opposing overlays. Several major screen reader user surveys report low confidence in them. The consistent feedback from actual assistive technology users is that overlays interfere more than they help.
That is the strongest evidence available: the people the product claims to serve say it does not serve them.
Do they satisfy the law?
No, and this is the part that costs people money.
Legal requirements — the EAA through EN 301 549, the ADA as applied by US courts — attach to the site being accessible, not to a widget being installed. A site with an overlay and inaccessible checkout is a site with inaccessible checkout.
In the US, a significant number of accessibility lawsuits have been filed against sites that had an overlay installed at the time. Some overlay vendors offer legal indemnities; read what they actually cover before treating that as protection.
If you have an overlay and believe you are compliant, that belief is the risk. It is the reason the underlying issues were never fixed.
What to do instead
Fix the actual problems. On most WordPress sites that is a much smaller job than the overlay marketing implies:
- Colour contrast — a theme setting
- Keyboard operability — test it in ten minutes
- Form labels
- Heading structure
- Alt text on the images that matter
The five failures post covers all of these. It is an afternoon of work, and unlike an overlay it actually changes the experience.
The honest cost comparison
An overlay is typically $500–1,000 a year, forever, and fixes nothing.
Fixing the common issues on a small WordPress site is a few hours of work, once. A proper audit is $349 and tells you exactly what to do, including the things automation cannot find.
If your budget is limited, spend it on the audit rather than the subscription. One tells you the truth about your site; the other puts an icon in the corner.
When an overlay is defensible
One narrow case: as a temporary measure while a genuine remediation is underway, on a large site where the work will take months. Even then it is a comfort blanket rather than a fix, and the remediation is what matters.
What is not defensible is installing one and considering the matter closed. That is the version being sold, and it is the version that leaves people unable to use your site.