Accessibility widget for any website.

Title III of the Americans with Disabilities Act applies to public accommodations, and US courts have consistently held that this includes commercial websites. Plaintiffs filed roughly 4,000 ADA Title III web lawsuits in 2024, with ecommerce, hospitality, and education sites the most-targeted. The Department of Justice published a final rule in 2024 confirming WCAG 2.1 AA as the applicable standard for state and local government sites under Title II, and most defense lawyers now treat WCAG 2.1 AA as the de facto standard for Title III as well. A widget alone has not held up as a defense in litigation. Several reported cases involved sites that had deployed an accessibility overlay and were sued anyway, with courts finding that the underlying HTML, alt text, and form labeling were still non-compliant. The widget reduces friction for many visitors and signals good-faith effort, but the underlying code has to do its share.

The European Accessibility Act (EAA, Directive 2019/882) became enforceable across all 27 EU member states on 28 June 2025. It applies to ecommerce, banking, electronic communications, e-books, transport ticketing, and media services that serve consumers in the EU. The technical standard is EN 301 549, which incorporates WCAG 2.1 AA at minimum and WCAG 2.2 in some categories. Penalties vary by member state but include fines, removal from the market, and reputational damage. Non-EU companies are in scope if they offer services to EU consumers. The widget is helpful for the user-facing controls EAA expects, but the back-end remediation work (semantic HTML, real alt text, keyboard reachability, screen reader compatibility) still has to happen. Publishing an accessibility statement and a feedback channel is a hard requirement under EAA, not optional.

WCAG 2.1 Level AA contains 50 success criteria across four principles: perceivable, operable, understandable, and robust. WCAG 2.2, finalized in October 2023, adds nine new criteria including focus appearance, target size minimum, dragging movements, and consistent help. Most regulators reference 2.1 AA as the floor; 2.2 is becoming the working standard. A widget can address some criteria directly: 1.4.3 contrast (via contrast mode), 1.4.4 resize text (via font scaling), 1.4.10 reflow (the widget itself reflows correctly), 2.4.7 focus visible (via the focus-ring helper), 1.4.12 text spacing (via the spacing controls). Many other criteria, including 1.1.1 non-text content (real alt text), 1.3.1 info and relationships (semantic HTML), 2.1.1 keyboard (real keyboard reachability), 4.1.2 name role value (proper ARIA), require fixes in your underlying code that no overlay can patch on the fly without breaking things.

Be honest about this. The disability community has been openly critical of AI-only accessibility overlays for years. Public statements from disability advocates, accessibility consultants, and screen reader users have documented cases where overlays interfered with assistive technology, made navigation harder, or provided a false sense of compliance to site owners. The Overlay Fact Sheet, signed by hundreds of accessibility professionals and disabled people, recommends against marketing overlays as a complete solution. ADA lawsuits have proceeded against sites that deployed overlays. Poper takes the position that a widget is a useful complement: it gives visitors immediate user-facing controls (font sizing, contrast, dyslexic font, animation pause) that they would otherwise have to dig into browser settings to find. It is not a substitute for writing accessible code, conducting manual audits, testing with real assistive technology, and fixing the issues those tests reveal.

Industry-standard accessibility programs combine four things. First, manual code remediation: fixing alt text, heading order, form labels, focus management, and keyboard reachability in the source HTML. Second, automated testing in CI using axe-core or Pa11y to catch regressions before they ship. Third, manual testing with real users of assistive technology (screen readers, voice control, switch access) and with disability consultants who can identify barriers automated tools miss. Fourth, user-facing controls (the widget) so visitors can adapt the experience to their needs without leaving your site. Poper covers the fourth pillar honestly and points you toward providers that handle the other three. We also generate the accessibility statement and the user-feedback channel that ADA and EAA both expect, so visitors who hit a barrier have a clear way to tell you, and you have a documented response process. That layered approach is what holds up legally and what the disability community asks for.