Overlay widgets promise WCAG compliance in a snap. Add a script, get a badge, sleep well. That’s the pitch.
The reality: plaintiffs’ firms have specifically named overlay products in ADA lawsuits — by brand. The widget doesn’t stop the suit. In some cases, it becomes the evidence.
Three signs your overlay isn’t doing what you think it’s doing:
1. The widget is present, but tab navigation is broken
Try it: click into your address bar, then press Tab repeatedly. If focus jumps around unpredictably or gets stuck, the underlying HTML is inaccessible. The overlay isn’t fixing the DOM — it’s overlaying visual affordances on top of a broken structure. Real keyboard-only shoppers can’t use your site. Real screen-reader users can’t use your site. The widget just makes it look like they can.
2. What the screen reader announces doesn’t match what’s on screen
Turn on VoiceOver (Mac) or NVDA (Windows) and navigate to a vehicle detail page. If the reader says “image, image, image” instead of “2022 Honda CR-V EX-L” — or if it announces a “Get pre-qualified” button as just “button” — the alt text and ARIA labels are missing or wrong. The widget can’t invent them.
3. Your widget vendor is named in filings
Search PACER for your widget vendor’s name plus “ADA” or “WCAG”. Some vendors show up in dozens of cases as evidence that the site tried something inadequate. Judges and juries are increasingly reading “we bought a widget” as “we knew there was a problem and didn’t fix it.”
Real accessibility is semantic HTML, real alt text, real labels, real focus management. Tested with real assistive tech. Not bought as an add-on.