Please, Don’t Use an Accessibility Widget

Here is a rundown on what an accessibility widget, also called an accessibility overlay, is. It is a small program or code snippet that is added to the site. It usually has an icon on the side or corner of your screen. The idea is that a person with a disability would just click on the icon and be able to change font size, change the site’s color contrast, pause animation, or make it screen reader friendly.

If your site has one of those little accessibility icons in the corner, here’s something you should know: it’s not doing what you think it’s doing.

Why the widget doesn’t hold up

Widgets are built to fix what’s easy to see: contrast, font size, maybe a missing alt tag here and there. What they can’t touch is the stuff that breaks someone’s experience, a checkout page a screen reader can’t get through, a form that fails silently without a mouse, navigation that traps a keyboard user in a loop.

Those are the barriers that stop someone from using a site. Nobody gives up on your site over font size. They give up because they couldn’t finish buying something.

It gets worse. Some widgets get in the way of screen readers. So, a site with a widget can be harder for someone using assistive technology to use than a site with no widget at all. That’s not just failing to fix the problem, that’s adding a new one.

What fixing it looks like

There’s no shortcut here. Real accessibility means going into the code itself: clean HTML, keyboard navigation that works, checkout flows and forms built so assistive technology can read them, alt text that describes the image instead of just filling a field. It means testing against WCAG 2.2, the current standard, instead of guessing.

It takes longer. It costs more up front than a widget subscription. But it’s the only version that lets someone with a disability use your site the way it’s meant to be used.

3. What real fixes give people with disabilities

Here’s what gets lost when the conversation stays on lawsuits: for the person using your site, this was never really a legal question. It’s a question of whether they can finish what they came to do.

A screen reader user doesn’t need your widget’s “screen reader mode” toggle. They already have a screen reader, JAWS, NVDA, VoiceOver, whatever they’ve used for years, and they know it better than anyone at your company ever will. What they need is a site built to work with it: form fields with real labels, buttons that announce what they do, a checkout flow that reads in the right order. A widget sitting on top of broken code doesn’t create any of that. It can’t

The research backs this up. In WebAIM’s 2021 survey of accessibility practitioners, 67% rated overlays as not at all or not very effective. Among the respondents who were themselves disabled, that number rose to 72%, and only 2.4% called overlays effective.

A code fix gives someone the same site everyone else gets, not a separate workaround.
Nobody wants to hunt for a special “accessible mode” bolted onto the corner of a page. They want the site to just work, the same experience, the same features, no detour. That only happens when accessibility is built into the product, not layered on top of it.If your site has real accessibility gaps, a widget on the homepage won’t change that. It just hides the gaps a little better, until someone finds them, whether that’s a customer who couldn’t check out or a plaintiff’s attorney.

A code fix works with the tools people already rely on, instead of competing with them.
Screen readers, keyboard navigation, browser zoom, high-contrast mode, these are things people have already set up the way they like on their own devices. A site with clean code just works with all of it. A widget adds its own layer of controls that can clash with a person’s existing setup, and in some documented cases has made screen readers behave worse, not better.

Disabled users and the people who build assistive technology have said this themselves.
Over 1,000 people have signed the Overlay Fact Sheet, an open statement written and endorsed by accessibility specialists, WCAG and ARIA contributors, disability rights advocates, assistive technology developers, and disabled users. Its message is blunt: overlays don’t deliver the compliance or usability their marketing promises, and the people the widgets claim to help are often the ones saying so most clearly.

None of this makes a widget worthless in every sense; a couple of its surface controls just duplicate settings a person’s own device already handles better. But it’s not a substitute for the work, and the people it’s supposed to serve are the ones with the least reason to pretend otherwise.

Where I stand

If your site has real accessibility gaps, a widget on the homepage won’t change that. It just hides the gaps a little better, until someone finds them, whether that’s a customer who couldn’t check out or a plaintiff’s attorney.

Fixing the code is the only thing that works, so it’s the only thing I build. If you want to know where your site stands, that’s worth finding out before your users do.