ADA / WCAG Accessibility · Phoenix AZ

Is Your Website an ADA Lawsuit Waiting to Happen?

Thousands of businesses get sued every year over inaccessible websites — and if you installed an accessibility "plugin" to be safe, it may be making you a bigger target, not a smaller one. We find the real issues with a free, read-only audit and fix them in the code.

Get a Free Accessibility Audit →Why the plugin backfires

Read-only audit. We change nothing without your approval. Information, not legal advice.

The short version: courts and the DOJ treat your website as covered by the ADA, and the technical standard is WCAG 2.1 AA. Real compliance lives in the code — keyboard navigation, screen-reader labels, alt text, contrast, focus order. An accessibility overlay widget can't deliver that, and it advertises to plaintiffs' firms that you tried to take a shortcut. Fixing it properly protects you; the plugin often does the opposite.

The lawsuits are real — and climbing

4,000+

ADA website lawsuits filed in 2024 — most against businesses under $25M in revenue, not just big brands (UsableNet). [3]

1,023

sites that HAD an accessibility widget installed were sued in 2024 — over 25% of all cases (UsableNet). [4]

$1M

FTC fine against accessiBe in 2025 over what the agency charged were deceptive claims that its overlay made sites compliant. [2]

The "accessibility plugin" trap

Overlay widgets (accessiBe, UserWay, AudioEye and the like) promise instant compliance with one line of code. The accessibility community, the courts of public opinion, and now the FTC disagree.

Installing a widget didn't stop the lawsuit — in 2024 it was the lawsuit, for more than a quarter of all cases.

Source: UsableNet 2024 Year-End ADA Digital Accessibility Lawsuit Report.

They don't actually make you compliant

Over 1,000 accessibility professionals signed the Overlay Fact Sheet, which states plainly: "No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard." They can't reliably fix alt text, form labels, focus control, or keyboard access. [5]

They attract lawsuits

UsableNet found 1,023 sites with an accessibility widget installed were sued in 2024 — over a quarter of all cases. To a plaintiff's firm, the widget is a flag that the site isn't truly accessible. [4]

The government fined the biggest vendor

In 2025 the FTC required accessiBe to pay $1 million and barred it from claiming its AI product makes sites WCAG-compliant — a deceptive-marketing action, not an ADA ruling, but a clear signal the "one-click compliance" promise doesn't hold up. [1][2]

Some can even get in the way

Many screen-reader users turn overlays off because they interfere with the assistive technology they already use — so the "accessibility" never reaches the people it's for, and badly-injected code can make navigation worse. [5]

Real compliance lives in the code

WCAG 2.1 AA is built on four principles — content must be Perceivable, Operable, Understandable, and Robust. Every one of them depends on the site's actual markup, which a script that runs after the page loads can only guess at. [10]

An overlay plugin

✕Runs after the page loads — can only guess at what it finds
✕Can't write real alt text or know what a form field is for
✕Often breaks the screen readers users already rely on
✕Leaves the underlying code untouched
✕A recurring subscription, billed forever
✕No documentation to show if a demand letter arrives

Code-level remediation

Fixes the markup itself — the source of every issue
Real alt text and labels, written by a human who looked
Works with assistive technology instead of fighting it
Leaves you with a genuinely faster, better-built site
A one-time fix you own
A documented compliance packet: audit, VPAT, before/after

Perceivable

Real text alternatives for images, captions for media, and content that keeps its meaning however it's presented — the overlay can't know what an unlabeled image actually shows.

Operable

Every function reachable by keyboard, with logical focus order, skip links, and landmarks — so someone who can't use a mouse can still get through your site.

Understandable

Readable content, predictable behavior, and forms with proper labels, instructions, and error handling — not a widget guessing at your field names.

Robust

Valid, semantic markup with correct name/role/value so assistive technology can parse it. Bad injected ARIA breaks screen readers — no ARIA beats bad ARIA.

Where the law stands

The ADA covers websites. In Robles v. Domino's Pizza, the Ninth Circuit held the ADA applied to the company's website and app, and the Supreme Court declined to hear the appeal — leaving that ruling in force. The absence of detailed federal web regulations is not a defense. [9]

WCAG 2.1 AA is the standard. The DOJ has consistently said the ADA applies to web content, and in its 2024 rule for state and local governments it formally adopted WCAG 2.1 Level AA as the technical standard (with compliance deadlines of April 2027 and April 2028). That rule binds government directly, but it cements WCAG 2.1 AA as the benchmark that plaintiffs and defense counsel reference for everyone. [7][8]

Small businesses are the main target. Most ADA website suits are filed against companies under $25M in revenue, often starting as a demand letter — and because the ADA's fee rules favor plaintiffs, defending one can cost as much as settling it, even when you're in the right. [12][13]

This is information, not legal advice. Your specific exposure is a question for your attorney — we bring your site into real WCAG 2.1 AA conformance and document it, and we recommend a legal review.

How we fix it — and what you get

We audit with the industry-standard engine (axe-core, the same one behind Google Lighthouse) plus manual screen-reader testing, fix the issues in the code, and hand you a documented compliance packet — not a widget and a false badge.

WCAG 2.1 AA audit report

Every failure, with screenshots, the exact code at fault, severity, and the success criterion it violates.

VPAT / Accessibility Conformance Report

The industry-standard document lawyers and procurement teams actually recognize.

Before/after remediation record

Evidence of each issue fixed — the proof of real work that an overlay can never produce.

Accessibility statement + plan

A published statement and documented remediation plan — the good-faith paper trail.

That packet is the difference between "we installed a plugin" and a defensible, documented record of real remediation — the kind of evidence that actually matters if a demand letter shows up. We can also monitor the site after launch so new content doesn't quietly break compliance again.

What it costs

Every engagement starts with the free audit. If we find problems, most remediations land in the low-to-mid four figures, with optional monthly monitoring — far less than defending a single ADA lawsuit, and you end up with a genuinely better website.

The price depends on your site's size and how much is broken, so we scope it to exactly that and give you a fixed quote after the audit. No surprise agency bills, and no monthly "accessibility subscription" that never actually fixes the code.

Find out if your site is a target — free

We'll run a read-only accessibility audit and send you a plain-English report: your WCAG 2.1 AA failures, how serious each is, whether your overlay is helping or hurting, and what to fix first. No changes, no obligation.

Get my free accessibility audit →

Questions, answered

Isn't an accessibility plugin or widget enough?

No — and it can make things worse. Over 1,000 accessibility professionals (the Overlay Fact Sheet) state plainly that no overlay can make a website fully compliant, and UsableNet found 1,023 sites that HAD an accessibility widget installed were still sued in 2024 — more than a quarter of all cases. In 2025 the FTC fined the best-known overlay vendor, accessiBe, $1 million over what the agency charged were deceptive claims that its product could make any site compliant. The widget is a tell that the site isn't actually accessible, not a shield.

Does the ADA really apply to my website?

Courts and the Department of Justice say yes. In Robles v. Domino's the Ninth Circuit held the ADA covers a company's website and app, and the Supreme Court declined to hear the appeal, leaving it standing. DOJ has consistently taken the position that the ADA applies to web content, and its chosen technical standard is WCAG 2.1 Level AA — the benchmark plaintiffs and defense counsel both reference.

How bad is the lawsuit risk, really?

UsableNet tracked over 4,000 ADA website lawsuits in 2024, and the majority target businesses under $25M in revenue — small and mid-size companies, not just big brands. Most start as a demand letter; many settle in the low five figures, and defense costs can equal or exceed the settlement even when you win, because the ADA's fee rules favor plaintiffs.

What does the free audit include?

A read-only accessibility scan using the industry-standard engine (axe-core, the same engine behind Google Lighthouse) plus manual testing with real assistive technology, then a plain-English report of your WCAG 2.1 AA failures, how serious each is, and what to fix first. We change nothing without your approval.

What do I actually get when you remediate?

A documented compliance packet: the full WCAG 2.1 AA audit report with screenshots, a VPAT/Accessibility Conformance Report, a before/after record of every fix, and a published accessibility statement. It's the defensible paper trail that shows a real, good-faith remediation — the opposite of a widget and a false badge.

Will this guarantee I won't get sued?

No one can honestly guarantee that, and we won't pretend to. What we do is bring your site into real WCAG 2.1 AA conformance — in the code, verified by automated and manual testing — and document it as evidence of good-faith compliance. We're not a law firm; for your specific exposure we recommend your attorney review the work. This page is information, not legal advice.

Sources & references

Every claim is tied to a government, court, standards-body, or recognized industry source. The FTC action against accessiBe was a deceptive-marketing consent order, not a court ruling on the ADA; lawsuit figures are UsableNet's; cost figures are reported estimates.