Toolbar Plugins/Widgets for Website Accessibility Aren’t ADA/508 Compliant

Man in long sleeve shirt (Kris Rivenburgh) looks intently at a Microsoft Surface while sitting at a conference room table.

Thinking about using one of those accessibility widgets on your website.

This article will make you think again.

Here’s what’s happening:

There are about 7–10 “accessibility” widget vendors that really want to sell you an instant-fix widget to supposedly make your website accessible.

They’ll give you a piece of JavaScript code to paste in your website and then, boom, you’ve got a clickable icon that opens up to a menu of “accessibility” options somewhere in the sidebar of your website.

The toolbar, when activated, typically has some combination of the following features:

Users have the ability to

  • read the page aloud
  • change color contrast
  • stop animations, gifs, etc.
  • navigate through the website using links, headers
  • increase font size
  • change the cursor
  • change the font
  • add focus to elements

Oh, and the accessibility companies won’t need to go inside your website or touch a line of code to make this all come together.

Sounds pretty good, right?

These vendors sure hope so. They really want you to buy into their monthly or yearly subscription.

So much so they’ll claim their toolbar meets every guideline and law under the sun.

“WCAG 2.0 AA — absolutely!”

“WCAG 2.1, why of course it does, it’s a little embarrassing that you even asked!”

“Is it Americans with Disabilities Act (ADA) compliant? You can bet your first born! We’ve got our rubber stamp of approval right here.”

“Section 508? Double Yes!”

And, if you’re lucky, you might even get a sales demo on how their solution uses artificial intelligence (AI) to ensure your website is accessible.

If you weren’t skeptical before, you should be as soon as you start hearing about AI miracles.

You’ve probably heard and experienced the adage, “If it sounds too good to be true, it probably is.”

This is another one of those times.

Making your website accessible is not as easy as copying and pasting a single line of JavaScript code on your website.

Let’s go over the reasons toolbars/overlays don’t work.

Activation is Required

This one’s a big one.

Not every person who lands on your website will know the toolbar option even exists.

Also, many others will not want to use an overlay.

Will screen reader users know?


Will users who don’t use a screen reader know?

Maybe but probably not. Either way, it’s not enough.

Enough is when everybody gets “full and equal” use and enjoyment of your website.

(The “full and equal” standard is the foundation of the Americans with Disabilities Act.)

And for those websites that rely on an overlay “solution”, if a user is not aware of or doesn’t think to activate an accessibility toolbar or doesn’t want to experience your website through said toolbar, then they’re left to deal with an inaccessible website.

When that situation inevitably occurs, your website, in effect, discriminates against users with disabilities and violates the ADA.

Falls Well Short of Full Accessibility

Overlays don’t account for all disabilities.

In other words, some users will have difficulty accessing or will not have access to content or functions because the toolbar can’t or doesn’t have features to meet their needs.

It’s essential to account for different disabilities and degrees of disability when designing/developing a website for accessibility (and also when adding/uploading content).

This is why we must make our websites, both within the content and at the code level, accessible.

We’re making our websites accessible to everyone, regardless of disability, and regardless of whether we can automate remediation to account for those different disabilities.

Overlay vendors want to emphasize all the different things they supposedly accomplish with automation but you’ll never hear them exclaim what features they can’t or won’t build in to their widget/plugin.

computer screen showing website code

What’s ironic is many of the overlay vendors tout the “We won’t touch your website code” line as a selling point when, in fact, this is what buyers should want and expect from claims of ADA compliance.


Most of the features in accessibility toolbars are redundant with the features found inside screen readers.

Depending on how many options a toolbar has, it may add some marginal benefit to someone who activates them but, as you might guess, this doesn’t make for a fully accessible experience.

Also, users are accustomed to their own screen reader/assistive technology and usually don’t want to bother with learning what amounts to an entirely experience just to access the functions or content on one specific website.

No Manual Content Remediation

No closed captioning or text transcripts are included in the “automated accessibility” package you are being sold.

Captions and transcripts for multimedia content on your website such as podcasts and YouTube videos are critical for accessibility.

Most overlay vendors won’t even talk about this until you see their price tables which add transcripts and captions as an additional cost.

Why, then, do most of them claim they can make you fully accessible through just their toolbar?

AI Doesn’t Work Like They Claim

Artificial intelligence sounds really fancy and wonderful in sales pitches but doesn’t play out so well in real life.

One way in which AI is purported to provide benefit is through automatic alt text.

All meaningful, non-decorative images on a website need to have an alt text value inside an alt attribute that conveys the meaning of that image so that people who cannot see the image know what the image is.

AI can go in and apply alt tags to images throughout a website. The problem is the AI-generated alt text us generic and non-descriptive which mostly defeats the whole point of adding the alt text.

Let’s use an example image to illustrate.

Smiling woman excitedly looking at phone in coffee shop.

The alt text I added to the image was:

“Smiling woman excitedly looking at phone in coffee shop.”

An AI program is going to use object recognition to extract the objects it can identify and recite those. At best, AI alt text might look like:

“Woman, phone, coffee cup”

That doesn’t accurately convey the meaning of the image so, in effect, the image is inaccessible.

(You can experience AI alt text firsthand by checking the automatically generated alt text on your Facebook image uploads.)

While this will pass an automated scan, it fails a manual audit.

Two More Notes


There aren’t any automated scans — scans created by the most reputable of accessibility companies and experts — that claim to flag all of the accessibility deficiencies on a website (they only get about 25% of issues per WCAG 2.1 AA).

So if there isn’t technology to even flag all of the errors, what are the odds a technology exists that will “fix” your website to fully conform with WCAG 2.1 AA?


Think about the word, overlay, for a second.

Overlay means that the toolbar and its features sit on top of your website which, again, means that your website itself isn’t accessible.

The overlay, when activated, can modify certain aspects and elements of your website but it does not alter the fundamentals of your website to be accessible.

There’s a strong “separate but equal” argument to be made by plaintiffs’ lawyers with an overlay because, in effect, there’s a different website/experience available to someone who activates the overlay.

Continuing with that argument, rather than having one website that’s accessible for everyone, you’ve got two different versions of the website — an alternate version and the original version.

The Department of Transportation agrees with this assessment.

Legal Precedent

While the “separate but equal”/alt website issue hasn’t yet been litigated in courts, it has been addressed in a consent order from the Department of Transportation (DOT) against Scandinavian Airline Systems (SAS).

Here, SAS was actually using an accessibility toolbar on an alternate website in hopes they met WCAG 2.0 AA as called for by the Air Carrier Access Act (ACAA).

In its defense, SAS stated:

The assistive version of its Website was developed by a third-party vendor…who assured SAS that the assistive version conformed to WCAG 2.0 Level AA success criteria and that its use complied with DOT requirements and was also being used by other U.S. carriers

Included in the decision was this from DOT:

It is a “well-established principle of disability non-discrimination law that separate or different aids, benefits or services can only be provided to individuals with disabilities (or a class of such individuals) when necessary to provide aids, benefits, or service that are as effective as those provided to others.

In other words, you can only provide separate offerings when they are absolutely necessary.

Would SAS have been in the clear if they used the toolbar on their primary website?

Probably not. The key to website accessibility is to provide the same accommodation to everyone and make it so that it’s fundamentally adaptive and responsive enough to be accessible to those with disabilities.

End result/DOT’s decision:

The Enforcement Office finds the website (with toolbar) was found to be in violation of the ACAA.

SAS and Enforcement Office enter into a settlement agreement for $200,000.

And remember, the toolbar company assured them that their toolbar would meet WCAG 2.0 AA. (detrimental reliance)

Although this was not the Department of Justice (DOJ) ruling on a Title III violation, I am 99% certain the DOJ would rule the same way.

Will Accessibility Toolbars Prevent Lawsuits?

front of Supreme Court building, showing stairs leading up to columns

Without the information above, it’s quite logical to reason, “Well, I’ll get one of these overlays and put it up while we get our website accessibility worked out. At least that will probably reduce our risk of an ADA Website Compliance lawsuit in the meantime.”

In theory, this makes sense, right?

At the very least you’ve become “more accessible” and have provided users with more options with which to better access content and functions across your website.

Paradoxically, an overlay might actually put a target on your back.

First of all, the serial plaintiffs’ lawyers filing ADA Title III lawsuits aren’t going to activate the overlay before scanning a website (not that the overlay takes care of everything anyway).

Second, as more plaintiffs’ lawyers realize that people have installed an overlay that doesn’t work and walked away from accessibility, they’re going to start targeting these website owners specifically.

And when they do, they can simply grab a list of showcased clients off the overlay vendors’ websites. Or they can just perform various reverse searches to grab a client list.

Overlays are quite literally risky business.

Update: Websites using overlays are being sued.

What Should You Do About Website Accessibility?

Website layout on computer screen next to tablet view of a web page indicating web design work.

Manual remediation.

To make your website accessible, you should invest in manual remediation.

What this means is you need to have a developer remediate (fix) your website to make it accessible according to WCAG 2.0 AA or 2.1 AA.

Subscribe to to my WCAG 2.1 AA checklist for free.


Assistant Attorney General Stephen E. Boyd,, and the Ninth Circuit Court of Appeals have all stated that you have flexibility in how you make your website accessible.

The key part of that is that you make your website, itself, accessible.

As I’ve covered above, overlays 1) can’t be used if not activated, 2) don’t account for all disabilities anyways, and 3) don’t fundamentally make your website accessible.

Think of the flexibility statement as more in line with a scenario where your color contrast doesn’t quite meet the 4.5:1 threshold under WCAG — that doesn’t mean you’re in violation of the ADA.

However, a toolbar overlay isn’t even the same discussion; an overlay wouldn’t come into play for flexibility because it doesn’t actually make your website accessible.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store