--- title: "What Is an Accessibility Overlay?" url: https://guavawebcompliance.com/articles/what-is-an-accessibility-overlay description: "An accessibility overlay is a script that patches your site after it loads. What it can fix, what it cannot, the FTC's $1M case against accessiBe, and our own scan of their site." published: 2026-07-23 updated: 2026-07-23 --- An accessibility overlay is a script you add to your site with one line of code. It runs in the visitor's browser and tries to patch accessibility problems after the page has already loaded — adjusting contrast, adding labels, changing how a screen reader announces things — without anyone touching the site's own HTML. It's a bandage stuck over a crack: it covers the middle of the damage and leaves the rest of the crack showing on both sides. ## Why it matters Overlay vendors sell it as the whole job: paste in the widget, display the badge, move on. But a screen reader reads the page's actual markup. An overlay runs as a layer on top of that markup, so it can only work with what's already there. If a button was built with no name a screen reader can announce, the overlay has nothing to read off — it never had access to what the developer meant. The crack runs on underneath the bandage. The site just gained a badge for the visitors that crack still blocks. ## What it looks like The government tested that gap against the company that made this pitch famous. accessiBe told customers its accessWidget plug-in could make any website comply with WCAG. On April 22, 2025, the FTC's commissioners voted 3-0 to approve a final order barring accessiBe from making that claim without evidence to back it, and requiring the company to pay $1 million. We wanted to see the gap for ourselves, so we ran accessiBe's own homepage — the site of the company the FTC fined for exactly that claim — through our scanner on July 16, 2026. It came back with two critical violations: two buttons with no accessible name a screen reader can read aloud, and six elements using an ARIA attribute the specification doesn't permit there — on a page that still scored 84 out of 100 overall. The exact class of defect the FTC said accessiBe couldn't credibly claim to fix was sitting on accessiBe's own site. ## How it's fixed There's no bandage for missing markup. Real remediation means opening the code and fixing each defect where it lives: giving a button real text or an aria-label, writing alt text image by image, tying a form's labels to the fields they describe. It's slower than pasting in a script, and it's the version that holds up when a screen reader — or a plaintiff's expert — tests the actual page instead of the widget sitting on top of it. Overlay features that help sighted users — a contrast toggle, a larger-text button — are worth keeping alongside that work. They add a convenience layer for people who can already see the page. The crack underneath still needs actual mending either way. Want to know what an overlay would miss on your own site? [Run it through our free report](https://guavawebcompliance.com/free-scan) — no login, no credit card, no sales call. --- ## The fine print - **The FTC order is a consent order, not a court ruling.** It binds accessiBe specifically — it doesn't hold that overlays fail as a category, and no court has ruled on that question. [Read our take on what the FTC order does and doesn't establish](https://guavawebcompliance.com/articles/settling-ada-website-lawsuit). - **Our scan is a floor, not a verdict.** A low violation count doesn't mean a site is accessible, and a higher one doesn't mean it's uniquely bad — automated tools catch what's machine-detectable, not whether a label makes sense to a person using it. Our own homepage scores 100 on the same scanner, which isn't a compliance certificate either. - **Scanned July 16, 2026.** Findings and methodology available on request. - **WCAG 2.1** covers both defects found under [Success Criterion 4.1.2, Name, Role, Value](https://www.w3.org/TR/WCAG21/#name-role-value) — the standard courts reference in ADA website cases, not one any court has adopted as binding law. - **We're not lawyers, and this isn't legal advice.** ### Sources - **Federal Trade Commission**, "FTC Approves Final Order Requiring accessiBe to pay $1 Million," Apr. 22, 2025 — https://www.ftc.gov/news-events/news/press-releases/2025/04/ftc-approves-final-order-requiring-accessibe-pay-1-million - **Federal Trade Commission**, "FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines," Jan. 3, 2025 (proposed order, 5-0 vote, preceding the April 22, 2025 final order) — 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 - **W3C**, Web Content Accessibility Guidelines (WCAG) 2.1, Success Criterion 4.1.2 — https://www.w3.org/TR/WCAG21/#name-role-value - Guava's own scan of accessibe.com, run 2026-07-16 (internal findings, methodology on request)