For overlay-widget users
You bought the widget in good faith. Then you read the news.
In 2025, 983 websites running accessibility overlays were sued anyway[2] — and the FTC fined accessiBe $1M for claiming automation ensures compliance[3]. This isn't your fault; the pitch was excellent. But a script tag can't rewrite your source code, and that's where the real barriers live.
Free: up to three verified issues living under your widget right now, screenshots included.
What a widget can and can't do
Adds a settings panel (font size, cursor, colors) and script-side patches on top of your page. Some of that is genuinely convenient for some users.
Fix your source: missing labels your form was built without, keyboard traps in your own scripts, focus indicators your theme deleted, image descriptions nobody wrote. Screen-reader users routinely turn overlays off — the barriers underneath remain.
Keep it or cancel it — honestly, your call and your budget. Our job is different: find what's underneath, prove it, and give your developer the exact fixes. Source-level fixes are the part that actually changes outcomes for users.