Home › Accessibility widgets
Accessibility widgets: what a free widget gives you, and what it does not
A widget adds a toolbar. It does not change the code an audit or a lawsuit tests.
The short version. An accessibility widget, free or paid, is a toolbar layered on top of your pages. It does not change the HTML that an auditor, a screen reader user, or a plaintiff's tester actually encounters. In 2025 the FTC ordered the largest widget vendor to pay $1 million over claims that its product made sites WCAG compliant, and roughly a quarter of the ADA website lawsuits filed in early 2026 named sites that already had a widget installed.
What an accessibility widget actually is
Technically it is one script tag. When the page loads, the script draws a floating button, usually a little person icon in a corner. Clicking it opens a panel: bigger text, a high contrast theme, a larger cursor, a reading guide, pause animations, maybe a dyslexia friendly font and a "screen reader mode". Some vendors go further and run automated repairs in the background: they guess alt text for images with an image recognition model, inject ARIA attributes on elements that look like buttons or menus, and try to manage keyboard focus.
Everything the widget does happens at runtime, inside the visitor's browser, on top of whatever HTML your site served. Turn the script off and every change disappears. That single fact explains most of what follows.
"Accessibility widget free": what you actually get for free
Several vendors offer a free tier of the toolbar, usually limited to one small site and carrying the vendor's branding. Before you install one, it is worth knowing that the features it sells are already built into every browser and operating system your visitors use, and that people with disabilities have generally set those up long before they reach your site:
- Text size and zoom. Every browser zooms to at least 500 percent with Ctrl or Cmd and the plus key. WCAG success criterion 1.4.4 (Resize Text) requires your site to remain usable at 200 percent zoom without any assistive technology, which is a property of your CSS, not of a toolbar.
- Contrast and color. Windows contrast themes, macOS "Increase contrast", iOS and Android color filters, and the operating system dark mode (which your CSS can respect with
prefers-color-scheme) are all system wide, so they work on every site, not just the ones that paid for a widget. - Reduced motion. A system setting exposed to your CSS as
prefers-reduced-motion. A widget's "pause animations" button is a per site copy of it. - Screen readers. VoiceOver ships with every Mac, iPhone and iPad, Narrator with Windows, TalkBack with Android, and NVDA is a free download. A blind visitor arrives with a screen reader already running. A widget's "screen reader mode" is a second, weaker reader that competes with the one they trust.
The Overlay Fact Sheet, a community statement signed by more than 1,000 accessibility practitioners including specification editors for WCAG, ARIA and HTML, makes exactly this point: the widget features duplicate what the operating system already provides. The genuinely free path is to make sure your site does not break those built in tools. Our free color contrast checker and alt text checker run in the browser and test the two most common failures in seconds, and the free site scan runs the full automated rule set against any page.
What a widget cannot fix
The list below is not a matter of opinion. Each item is a WCAG success criterion that depends on information a script cannot reliably infer at runtime.
| Barrier | WCAG | Why a widget cannot repair it |
|---|---|---|
| Missing or wrong alt text | 1.1.1 | Image recognition can say "man in suit"; it cannot know the image is your CEO, or that the chart shows revenue fell 12 percent. Wrong alt text is a barrier in its own right. |
| Unlabeled form fields | 3.3.2, 4.1.2 | A script can guess that the field next to the word "Email" is the email field. It guesses wrong on multi column layouts, custom selects and checkout iframes, and a wrong label is worse than none. |
| Keyboard traps and focus order | 2.1.2, 2.4.3 | Modals, carousels, date pickers and cookie banners trap focus because of how they were coded. Injected scripts cannot rewrite a third party component's event handling. |
| Heading and reading order | 1.3.1, 1.3.2 | Deciding whether a bold line is a heading, and at what level, is an editorial decision about your content. |
| Captions and transcripts | 1.2.2, 1.2.5 | Media accessibility is produced, not injected. |
| PDFs, canvas, SVG charts, embedded checkouts | various | Outside the DOM the widget can touch. Most retail sites lose the sale in exactly these places. |
Automated testing has the same ceiling. When the UK Government Digital Service planted 143 known barriers in a test page, the best automated tool found 41 percent of them (including barriers flagged for manual inspection). A widget's repair engine is an automated tool with less context than a scanner, running in a hurry, on every page load.
What the lawsuit data says
UsableNet's 2024 year end report adds a detail that should end the "at least it shows good faith" argument: many of those complaints cited the widget's own features as barriers, alongside the usual WCAG failures. The people filing these cases are professional testers using their own screen readers. They do not click the little icon.
On 3 January 2025 the Federal Trade Commission announced an order requiring accessiBe Inc. and accessiBe Ltd. to pay $1 million, after alleging that the company falsely claimed its accessWidget could make any website WCAG compliant and presented paid reviews as independent. The order prohibits claims that an automated product can achieve or maintain WCAG compliance unless the company has evidence to back them. Read the full ADA website lawsuit guide for the year by year filing counts and what the complaints cite.
Performance and privacy costs you do not see in the demo
A widget is a third party script on every page. It is downloaded from the vendor's servers, executes before or after your own code depending on how it was installed, and rewrites the DOM after the page has rendered. On slow connections that shows up as layout shift and a delayed first interaction, which also affects Core Web Vitals.
The privacy issue is subtler. Several overlays remember which profile a visitor chose ("blind", "motor impaired", "cognitive") in a cookie or local storage so it can be reapplied on the next visit, and some vendors sync that across sites they serve. Information about a disability is a special category of personal data under Article 9 of the GDPR, which means you need an explicit legal basis to process it. The Overlay Fact Sheet has a section on exactly this. If you serve EU visitors, a widget is something your privacy notice has to cover.
Widget versus fixing the code
| Capability | Accessibility widget | Fixing the code |
|---|---|---|
| Changes the HTML a screen reader receives | No, only at runtime, only while the script runs | Yes, permanently |
| Works with the visitor's own assistive technology | Often conflicts with it | Yes, that is the point of WCAG |
| Survives a redesign or a new theme | Every page change is re guessed | Yes, if you re-test after changes |
| Evidence you can send in reply to a demand letter | Complaints cite the widget itself | Dated scan reports and a remediation log |
| Time to first visible change | Minutes | Days to weeks, depending on the backlog |
| Monthly cost | Free tier to several hundred dollars | Your developer's time plus a scanner |
When a widget is acceptable
Being fair to the category: a preference panel that lets people adjust font size or spacing is a reasonable convenience feature, as long as three things are true. The underlying code already passes, so the panel is a nicety and not a patch. The panel can be dismissed and never covers content, form controls or the checkout button, especially at 375 pixel widths. And you make no compliance claim based on it, on your site or in your accessibility statement. If any of those is false, the widget is a liability, not a feature. Moving off one? Our accessiBe alternatives page compares the options side by side.
What to do instead, starting free
- Scan the five pages that matter. Home, a product or service page, the contact or checkout form, login, and one long content page. The free scan returns a score and the failing elements in about 30 seconds, no signup.
- Fix the two failures found on most home pages. WebAIM's 2026 study of one million home pages found low contrast text on 83.9 percent of them and missing alt text on 53.1 percent. Both are quick to fix in any CMS and both have a free checker on this site.
- Do the keyboard test. Put the mouse away, press Tab through the page, and make sure you can see where you are and reach every control. Escape must close dialogs.
- Label every field and every icon button. A visible label, or an
aria-labelon icon only buttons. This is the third of WebAIM's six categories (51 percent of pages). - Write an honest accessibility statement with a contact address and a response time. Many demand letters begin with an email that nobody answered.
- Re test after every deploy. Accessibility regresses the same way performance does. Monitoring is what keeps the fixes fixed.
AdaClear runs the automated layer against your live site with an industry standard engine, lists the failing elements with the exact code, and re-checks on a schedule. It never injects anything into your pages. For the parts a machine cannot judge, an optional Expert Fix has human specialists review and correct the remaining items.
Find the failures a widget hides
Free 30 second scan of any page: score, the failing elements and their code. No overlay, no signup.
Scan my site free →Frequently asked questions
Does an accessibility widget make my site ADA compliant?
No. There is no ADA certification, and a widget only changes what the visitor's browser shows while the script is running. The HTML that a screen reader, an auditor or a plaintiff's tester encounters is unchanged. In 2025 the FTC ordered accessiBe to pay $1 million over claims that its widget made sites WCAG compliant, and about a quarter of ADA website lawsuits in early 2026 targeted sites that already had a widget.
Is there a genuinely free accessibility widget?
Some vendors offer a free tier of their toolbar for a single small site, usually with their branding. The features it provides (zoom, contrast themes, reduced motion, a screen reader) are already built into every browser and operating system for free, and people with disabilities have them configured before they reach your site. The free tools that actually help are ones that find code failures, such as a contrast checker, an alt text checker and a full page scan.
Why do screen reader users complain about overlays?
Because they already run a screen reader they trust, and an overlay inserts a second layer that can override keyboard shortcuts, re announce content, or replace real labels with guessed ones. More than 1,000 accessibility practitioners have signed the Overlay Fact Sheet asking site owners not to use overlays as a compliance substitute, and the National Federation of the Blind adopted a resolution against overlays in July 2021.
Can a widget fix missing alt text automatically?
It can guess. An image recognition model produces a caption such as "person holding object", which is rarely the meaning the image carries on your page and is sometimes wrong in ways that mislead. WCAG 1.1.1 asks for a text alternative that serves the same purpose as the image, which is an editorial decision. Our free alt text checker lists every image on a page with its current alt attribute so you can write the real thing.
Does an accessibility widget slow down my website?
It adds a third party script that loads on every page and rewrites the DOM after render. The effect ranges from negligible to a visible layout shift and delayed interaction on slow connections. Measure it with your browser's performance panel before and after, and keep the script off the checkout if you keep it at all.
What should I use instead of a widget?
Fix the code. Run an automated scan to find the machine-detectable failures (contrast, alt text, labels, ARIA, keyboard reachability), correct them in your CMS or theme, test with the keyboard and a screen reader, publish an accessibility statement with a working contact, and re-scan after every deploy. AdaClear does the scanning and monitoring and never injects anything into your site.
Sources
- FTC press release, 3 January 2025: order requires accessiBe to pay $1 million over deceptive WCAG compliance claims: https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-order-requires-online-marketer-pay-1-million-deceptive-claims-its-ai-product-could-make-websites
- Overlay Fact Sheet (community statement, more than 1,000 signatories): https://overlayfactsheet.com/en/
- National Federation of the Blind, 2021 Resolutions (Resolution 2021-04 on overlays): https://nfb.org/resources/speeches-and-reports/resolutions/2021-resolutions
- UsableNet, 2023 Year-End Report on ADA Digital Accessibility Lawsuits (933 suits against widget sites, 4,605 total): https://3280432.fs1.hubspotusercontent-na1.net/hubfs/3280432/2024-ADA-Report-Digital-Accessibility-Lawsuits.pdf
- UsableNet, 2024 Year-End Report (1,023 suits against widget sites, 4,000+ total): https://3280432.fs1.hubspotusercontent-na1.net/hubfs/3280432/UsableNet-2024-Year-End-ADA-Web-Lawsuit-Report.pdf
- Accessibility.Works, Accessibility Overlay Widgets Attract Lawsuits (28 percent in 2025, up from 25 percent in 2024, citing UsableNet): https://www.accessibility.works/blog/accessibility-overlay-widgets-attract-lawsuits/
- EcomBack, Q1 2026 ADA Website Lawsuit Report (1,037 suits; 265 against sites with widgets): https://www.ecomback.com/ada-website-lawsuits-recap-report/q1-2026
- WebAIM Million 2026: accessibility of the top 1,000,000 home pages: https://webaim.org/projects/million/
- GOV.UK accessibility blog, What we found when we tested tools on the world's least-accessible webpage (best tool found 41 percent of 143 barriers): https://accessibility.blog.gov.uk/2017/02/24/what-we-found-when-we-tested-tools-on-the-worlds-least-accessible-webpage/
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2: https://www.w3.org/TR/WCAG22/
- Regulation (EU) 2016/679 (GDPR), Article 9 on special categories of personal data: https://eur-lex.europa.eu/eli/reg/2016/679/oj