Real human. Fast replies.
💬Text me(386) 569-1227
📞Call me(386) 569-1227
✉️Email mechenzo@honesty.im
📝Send a messageI reply same day
You’ve seen it. The little blue circle in the bottom corner of a website, usually a stick figure with its arms out like it’s about to hug you. Click it and you get a menu of font sizes, contrast toggles and a button that says something like “accessibility mode.” The business owner paid for it because someone told them it makes the site ADA compliant.
It doesn’t. And the federal government has already said so, with a seven-figure receipt attached.
The short version
An accessibility overlay is a third party script you paste into your site that adds a toolbar and tries to automatically fix accessibility issues as the page loads. You install it in five minutes, it puts that little icon on every page, and the sales page promises compliance.
The pitch is irresistible if you run a business and have never heard the word “WCAG” before last Tuesday. One line of code, a monthly fee, done. It’s the website equivalent of buying a gym membership and counting that as working out.
The problem is that a screen reader user doesn’t need a bigger font button. They need your images described, your form fields labeled, your menus reachable by keyboard and your headings in an order that makes sense. Most of that has to be right in the code itself. A script guessing at it on the fly is guessing.
No. An overlay can’t promise compliance, and the Federal Trade Commission went after one company that did.
In April 2025, the FTC approved a final order requiring accessiBe to pay $1 million. The FTC said the company claimed its accessWidget plug-in could make any website compliant with the Web Content Accessibility Guidelines, and that those claims weren’t backed up. It also alleged the company dressed up reviews and articles to look independent without disclosing its connections to the people writing them.
The order bars the company from claiming its automated products can make any site WCAG compliant unless it has evidence to support it. Read that again slowly. The regulator had to put in writing that you can’t just say your robot fixed the internet.
To be fair, that order is about one company’s advertising. It isn’t a ruling that every overlay is illegal. But if your whole reason for buying the widget was “now I’m covered,” that reason just got a lot thinner.
Because the lawsuit is about whether a disabled person could actually use your site, not about whether you had a widget on it.
If a blind customer can’t get through your checkout with a screen reader, the little blue guy in the corner doesn’t change that. Plenty of plaintiffs’ attorneys know what an overlay icon looks like. Some folks in the accessibility community will tell you it can make a site look like an easier target, since it signals somebody tried to cover their ass with a shortcut instead of fixing the thing.
I see this all the time: a small business site with an overlay installed, images with no alt text, a contact form whose fields are just gray placeholder text with no labels, and a phone number baked into a JPEG. The widget’s been billing them monthly for two years. The actual problems never moved.
Fix the site itself. It sounds like more work because it is more work, but it’s a lot less than people expect, and it stays fixed.
Here’s where I’d start on a typical small business site:
None of this is glamorous. It’s also the stuff that helps your SEO, your AI search visibility and your regular customers squinting at your site in a parking lot. Clean structure is clean structure. The W3C’s WCAG overview is the actual standard everyone is measured against, and it’s more readable than you’d fear.
If you’ve already fixed the site properly and you just like giving people a text size toggle, fine. That’s a convenience, not a compliance plan.
Most modern browsers and phones already let people zoom, bump up text size and switch on high contrast. People who rely on those settings have them set up the way they like. Your widget showing up with its own version is like a waiter cutting your steak for you. Nice gesture, a little weird, and you didn’t ask.
What’s not okay is keeping it as the reason you think you’re done. That’s the half-assed version, and it’s the one that costs money twice.
No U.S. law bans them. The issue is that they don’t make a site accessible on their own, and the FTC took action against one vendor for claiming they did. You can keep one, but don’t count on it to protect you.
It depends on how the site was built and how many pages it has. A simple, well built site often needs a focused cleanup rather than a rebuild. A site held together with page builder duct tape might need more. A real audit tells you which one you’ve got.
AI tools are useful for spotting problems and drafting alt text, and I use them that way. But a person still has to check that the alt text is right and that the page actually works with a keyboard and a screen reader. Automation finds the problems. A human signs off.
If you’ve got the little blue guy on your site right now, don’t panic and rip it out tonight. Just stop treating it like a seatbelt. I can look at what’s actually under the hood and tell you what needs fixing in plain English. Start with my ADA compliance page to see how I handle it, or tell me about your site and I’ll give you the straight answer, overlay and all.
