Insights
Why an accessibility overlay won't make a city or county website ADA compliant.
How to buy itBy Whitelam Media7 min read
All insightsAn accessibility overlay won't make a city or county website meet the ADA Title II rule, which measures the site itself against WCAG 2.1 AA. In our November 2026 test, 13 of 15 home pages running an overlay still failed automated checks. Here is what the rule asks for and what to do with the overlay you pay for.
An accessibility overlay won't make a city or county website meet the ADA. The Title II web rule measures the site itself against WCAG 2.1 Level AA, and an overlay is a script that runs on top of the page without fixing the templates, forms and documents underneath. In November 2026 we tested 27 city and county home pages with the automated checks a WCAG audit starts with. 13 of the 15 that ran an overlay still failed, with the overlay loaded and running. Below are those results, what the rule asks for and what to do with the overlay you already pay for.
We wrote this in November 2026 from the rule on ada.gov, the Federal Trade Commission's order against an overlay maker and our own tests. It isn't legal advice. Talk to your ADA coordinator and counsel before you change what your website says about compliance.
What an overlay is and what it promises.
An overlay is a line of code from an outside company that adds a button to every page, usually a small person icon in a corner. Click it and a panel opens with settings such as bigger text, higher contrast or a reading guide. Many also run a script in the background that tries to repair problems as the page loads, for example by guessing a description for an image that has none.
Some are sold to local governments as the quick way to meet the rule, for a yearly fee. The pitch is easy to like: one line of code, no work for staff and a badge in the footer.
What the ADA web rule measures.
The rule requires the web content and mobile apps a state or local government provides to meet WCAG 2.1 Level AA, including content provided through a contract or a license (ada.gov). Places of 50,000 people or more must comply by April 2027. Smaller places and special districts have until April 2028. Our guide to the deadlines and what to fix first covers who is in scope.
WCAG is written about the content itself: whether each image has a text alternative, whether each form field has a label, whether text has enough contrast and whether everything works from a keyboard. A setting a visitor has to find and switch on doesn't change what the page gives everyone else. A guessed image description can be wrong in ways nobody on staff ever sees. People who use screen readers already have their own software. What they need is a page built so that software can read it.
Testing tools can't settle every check either. W3C, which writes WCAG, says tools can't check every accessibility aspect automatically and human judgment is needed (Selecting web accessibility evaluation tools). A site that passes automated checks still needs a person with a keyboard and a screen reader. A site that fails them, overlay or not, has problems a person will find too.
13 of 15 overlay sites still failed our test.
In October 2026 we looked closely at 30 US city and county websites for places of 50,000 to 250,000 people (what we found). In November 2026 we went back to their home pages with axe, the open source accessibility testing engine from Deque that many audit tools are built on (axe-core), limited to the WCAG 2.0 and 2.1 Level A and AA rules. We loaded each page in a desktop browser, waited eight seconds so any overlay could load and run its repairs, then ran the checks.
One site refused automated visits, so it isn't counted. Two had a reading toolbar that only loads when a visitor clicks it, so we left them out too. Of the 27 left, 15 ran an overlay from one of five vendors as the page loaded and 12 had none.
| What axe found on the home page | With an overlay (15 sites) | Without an overlay (12 sites) |
|---|---|---|
| At least one failure axe rates serious or critical | 13 | 12 |
| Text with too little contrast against its background | 12 | 6 |
| Links with no text a screen reader can read out | 5 | 8 |
| Images with no text alternative | 5 | 2 |
| Zooming blocked on phones | 4 | 3 |
| Median number of different checks failed | 2 | 2.5 |
Every site without an overlay failed. So did 13 of the 15 with one, while the overlay was running. These are sites we chose, not a random sample, and the groups are too small to say which does better. What the table does show is that an overlay doesn't clear the failures an automated test finds, and those are the easy ones to find. Faint text and images with no description are the two most common failures on the web as a whole: WebAIM's February 2026 test of a million home pages found low contrast on 83.9% of them and missing image descriptions on 53.1% (WebAIM Million).
The two overlay sites with no automated failures aren't proof the overlay worked. A clean automated result covers only the part of WCAG a tool can check. We tested the home page only, not the agendas, forms and PDFs behind it, which is where our October check found most of the problems.
What regulators and accessibility experts have said.
In April 2025 the Federal Trade Commission approved a final order requiring accessiBe, an overlay maker, to pay $1 million over claims that its AI tool could make any website WCAG compliant (FTC).
The Overlay Fact Sheet is a public statement signed by more than 1,000 accessibility consultants, engineers, lawyers and disabled users. It says no overlay product can make a website fully compliant and asks site owners to fix problems at the source instead (Overlay Fact Sheet). It also warns that some overlays detect when a visitor uses assistive technology, which can reveal a disability.
Installing an overlay doesn't settle whether a site meets the rule. The site has to meet WCAG 2.1 AA as visitors get it, and a resident who can't use it can still file a complaint with the Justice Department at ada.gov, overlay or not.
What to do with the overlay you already pay for.
- Stop citing it as compliance. Take any line that credits the overlay for meeting the ADA off your accessibility statement and footer. Our guide to what a city or county accessibility statement should say has wording you can copy.
- Test the site with it switched off, then on. With it off you see the problems in your own templates and content, which is where they get fixed. With it on you see what visitors get, and that has to meet the standard too. Our WCAG 2.1 AA checklist for city and county websites lists 16 checks to run first, and our free website health check gives you a quick automated read.
- Try it with a keyboard and a screen reader. If the overlay's button, panel or repairs get in the way of either one, it is adding problems, not removing them.
- Read the contract before it renews. Note the renewal date and what the vendor promises in writing. The fee may do more good spent on fixing templates and documents.
- Write the standard into the next contract. If you're replacing the site, ask bidders how they test against WCAG 2.1 AA and rule out answers that rest on a widget. Our guide to writing a county website RFP for ADA Title II covers the wording.
When the fixes are bigger than your team.
If switching the overlay off shows failures in the templates, the forms and hundreds of documents, price the work. Our guide to what it costs to make a city or county website meet WCAG 2.1 AA sets out what drives the number. Our ADA website compliance program starts with an audit against every WCAG 2.1 AA criterion, fixes what fails in the code and checks the site every month after that. Where fixing the old site would cost more than replacing it, a rebuild made to the standard is the better buy. Or book a call and we'll look at your site with the overlay switched off.







