01

#What a dealership website accessibility widget does

An overlay widget runs a script that adjusts what a sighted visitor sees: larger text, higher contrast, a reading guide, sometimes a floating accessibility menu. Several also inject a compliance statement claiming WCAG conformance.

What it does not do is change the underlying HTML. A screen reader does not read a page's visual contrast or font size; it reads markup: whether a button has an accessible name, whether a form field has a label, whether an image has real alternative text or none at all. An overlay sits on top of the page a screen reader already cannot use, and mostly leaves that page exactly as it was.

This is not a new or disputed finding. In April 2025 the FTC fined accessiBe, one of the largest overlay vendors, one million dollars specifically for claiming its product made websites WCAG compliant when it did not.

02

#The lawsuit trend the widget was sold to prevent

Federal web accessibility lawsuits filed under ADA Title III reached roughly 3,100 in 2025, up 27 percent from 2024, and website accessibility claims made up a larger share of all ADA Title III federal filings than the year before. Include state court filings and the 2025 total is well over 5,000.

A meaningful share of those lawsuits named sites that already carried an overlay widget, and in some of those cases the complaint specifically cites the widget itself as a barrier rather than a fix. A widget marketed as a defense has, in a real number of cases, become evidence that the site owner knew about the exposure and addressed it with a product that did not work.

03

#What reduces dealership website accessibility exposure

Courts reference the Web Content Accessibility Guidelines, most often WCAG 2.1 AA, as the practical benchmark, with 2.2 AA treated as current best practice. That standard is checked against the page's real markup: color contrast values, form labels, keyboard navigation, focus order, alternative text on meaningful images, and headings that describe the content under them.

Automated scanning tools catch a real share of issues quickly and cheaply, and they miss the ones that require a person: whether alt text describes the image, whether a keyboard-only visitor can complete a checkout or a trade-value form, whether a screen reader announces a modal dialog correctly when it opens. A credible remediation combines both instead of stopping at whichever an overlay vendor's dashboard reports.

Six issue types account for the large majority of WCAG failures found across audited sites: low contrast text, missing alternative text, missing form labels, empty links, empty buttons, and a missing document language attribute. All six are markup fixes. None of them is something an overlay script changes.

TABLE

What an overlay changes, next to what a screen reader depends on

The six issue types on the right account for 96% of WCAG failures found across audited sites. An overlay widget does not touch any of them.

What an overlay widget changesWhat a screen reader or keyboard-only visitor depends on
Font size and spacing, on demandWhether form fields have real labels (48.2% of sites fail this)
Color contrast, on demandWhether text meets contrast requirements in the page's own CSS (79.1% of sites fail this)
A floating accessibility menuWhether links and buttons have an accessible name (45.4% and 29.6% of sites fail these)
A compliance statement in the footerWhether images carry real alternative text (55.5% of sites fail this)

Failure-rate figures as commonly reported in 2025-2026 web accessibility litigation and compliance research; check current figures before citing a specific percentage in anything published.

04

#Where this sits relative to a dealership's marketing work

A dealer platform's inventory filters, modal vehicle-detail popups and multi-step forms are named repeatedly in accessibility complaints across the industry, because most dealer platforms ship the same handful of patterns to every store on them. That makes a real remediation partly a platform question and partly a content and template question the store controls directly.

The pages and elements a marketing team writes directly (menu labels, image alt text on hero and inventory photos, form field labels, heading structure on content pages) are within a store's control regardless of platform, and are exactly the categories that make up most WCAG failures. Fixing what is controllable does not resolve platform-level issues, but it is real progress and it is not nothing.

What a specific complaint or demand letter means for a specific store, and what response it requires, is a question for an attorney. This page describes the technical and marketing side of the problem, not the legal one.