Remediation vs. Overlay: Which Holds Up in Court?

remediation vs. overlay: which holds up in court?

Website accessibility lawsuits under the Americans with Disabilities Act have grown steadily over the last several years. Federal court filings show thousands of cases each year targeting inaccessible websites. The complaints usually describe the same problems: images without alt text, forms that screen readers can’t understand, menus that don’t work without a mouse, videos with no captions.

Businesses facing those complaints often end up deciding between two approaches.

One option is remediation. That means fixing the underlying code and design problems that make a site inaccessible.

The other option is installing an accessibility overlay. Overlays are third-party scripts that add an accessibility widget to the page. The widget usually offers tools like text resizing, color adjustments, or screen reader assistance.

Overlay vendors advertise the tools as fast solutions for ADA compliance. Some promise compliance in “48 hours” or “one line of code.”

Court filings tell a different story.

Across multiple lawsuits filed between 2019 and 2024, overlays appear frequently in complaints. In many cases they are mentioned as evidence that the website still contained accessibility barriers despite the overlay.

Understanding how courts treat remediation and overlays requires looking at the technical side of accessibility, the legal standards used in ADA website cases, and the way plaintiffs document barriers.

The difference between remediation and overlays becomes obvious once the evidence in those cases is examined.

what remediation actually means in accessibility work

Website remediation means correcting accessibility problems directly in the code.

Developers fix HTML structure, ARIA attributes, navigation logic, and form labeling so that assistive technologies can interpret the page correctly.

Most remediation work is guided by the Web Content Accessibility Guidelines, known as WCAG. Courts in the United States often reference WCAG 2.0 or WCAG 2.1 in ADA website complaints.

Typical remediation tasks include:

Adding alternative text to images so screen readers can describe them.

Correcting heading structure so users can navigate pages by headings.

Labeling form fields so assistive technologies announce them correctly.

Fixing keyboard navigation so all interactive elements can be accessed without a mouse.

Adding captions and transcripts to video content.

Improving color contrast so text is readable for users with low vision.

A small business site might take a few days to remediate. A large e-commerce platform with thousands of product pages can take months.

Remediation work usually involves manual testing with assistive technologies such as screen readers. Automated scanners help identify some errors, but they detect only part of the problem. Many accessibility professionals estimate automated tools detect roughly 25 to 40 percent of accessibility issues.

Manual testing fills the gaps.

When remediation is done correctly, the accessibility improvements exist directly in the page structure. They remain in place regardless of which browser, device, or assistive technology the visitor uses.

That permanence matters in litigation.

how accessibility overlays work

Accessibility overlays operate very differently.

Instead of changing the underlying site code, overlays add a JavaScript layer that modifies how the page behaves in the browser.

Most overlays include a floating button on the page. Clicking the button opens a panel offering accessibility adjustments.

Typical overlay features include:

Text resizing controls.

Color contrast changes.

Link highlighting.

Reading guides that follow the cursor.

Text-to-speech playback.

Some overlays claim to use artificial intelligence to detect and repair accessibility issues automatically.

The site owner usually installs the overlay by adding a single script tag to the page header.

Setup can take less than ten minutes.

That speed is the selling point. Overlay companies market the tools as simple compliance solutions.

The problem is that overlays do not fix the underlying accessibility errors present in the site code.

If a form field lacks a label in the HTML structure, the overlay still sees the same problem. The screen reader also sees the same problem.

The overlay might attempt to inject labels dynamically, but those attempts often fail or produce inconsistent results.

This limitation is why overlays appear frequently in ADA website complaints.

what courts actually examine in accessibility lawsuits

ADA website lawsuits rarely focus on whether a company installed an overlay.

Courts examine whether the website is accessible to people with disabilities.

Plaintiffs typically document barriers encountered when attempting to use the site. The complaint may describe actions such as trying to order a product, schedule a service appointment, or view a menu.

The complaint then lists the accessibility failures encountered during that process.

A common example appears in restaurant website lawsuits. A blind user attempts to view the menu but encounters a PDF that contains only scanned images. The screen reader cannot read the content.

Another example appears in e-commerce complaints. A user tries to complete checkout but cannot activate the purchase button using keyboard navigation.

These barriers remain even if an overlay is present.

Because overlays do not correct the code itself, the barriers continue to exist.

That distinction shows up repeatedly in litigation.

a case example involving overlays

A lawsuit filed in the Southern District of New York in 2021 involved an online retail site that had installed an accessibility overlay.

The complaint described multiple accessibility failures despite the overlay being active.

According to the filing, the plaintiff attempted to navigate the website using a screen reader but encountered several barriers:

Images without alt text.

Buttons that lacked accessible labels.

Form fields that were not announced correctly by the screen reader.

Keyboard navigation that skipped important elements.

The complaint specifically noted that the overlay widget was present but did not resolve the issues.

The site still failed accessibility testing under WCAG criteria referenced in the complaint.

The case later settled, with the business agreeing to remediate the website and pay legal fees.

The overlay was not treated as evidence of compliance.

It was treated as irrelevant to the underlying accessibility barriers.

criticism of overlays from disability organizations

Several disability rights organizations have publicly criticized accessibility overlays.

In 2021, more than 400 accessibility professionals and disability advocates signed an open letter opposing overlays as compliance solutions.

The letter was published on the website Overlay Fact Sheet.

Signatories included accessibility consultants, developers, and researchers who work in digital accessibility.

The letter stated:

“Overlays do not fix the underlying code errors that make websites inaccessible.”

The group argued that overlays often interfere with assistive technologies rather than helping them.

Some screen reader users report that overlays override their preferred accessibility settings or introduce new navigation problems.

These criticisms appear regularly in accessibility conferences and developer forums.

The debate has become a persistent issue in the accessibility field.

why overlays appear attractive to businesses

Despite criticism, overlays continue to sell well.

The appeal is obvious.

Remediation requires technical work. It may require developer hours, accessibility audits, design changes, and testing.

Overlays promise something simpler.

A monthly subscription. A single script installation. A dashboard that claims compliance.

Some overlay vendors advertise pricing around $49 to $149 per month for small business sites.

For companies that receive demand letters threatening ADA lawsuits, the promise of a quick solution is appealing.

Some business owners install overlays immediately after receiving a complaint, hoping the issue will disappear.

In many cases, the lawsuit continues.

The presence of the overlay rarely changes the legal argument.

how plaintiffs document accessibility barriers

Accessibility lawsuits rely heavily on documented testing.

Plaintiffs typically use a combination of automated scans and manual screen reader testing.

Common testing tools include WAVE, Axe, and Lighthouse.

These tools generate reports identifying accessibility failures such as missing alt text, color contrast issues, and improper heading structures.

The plaintiff’s complaint may include screenshots from these reports.

Manual testing often follows. A tester may navigate the site using a screen reader such as NVDA or JAWS.

The tester documents what happens during the attempt.

The documentation might read something like this:

“On March 12, 2023, the plaintiff attempted to navigate the defendant’s website using the NVDA screen reader. When reaching the navigation menu, the screen reader announced multiple links labeled only as ‘button’ with no descriptive text.”

Those descriptions become evidence in the complaint.

If the overlay fails to correct those issues, the presence of the overlay becomes irrelevant to the accessibility barrier.

remediation as part of settlement agreements

Many ADA website lawsuits end in settlement agreements rather than trials.

Those agreements often require the defendant to remediate the website to meet WCAG guidelines.

Settlement terms sometimes include deadlines for completing remediation work.

For example, a settlement agreement might require the website to reach WCAG 2.1 Level AA compliance within 12 months.

Some agreements also require ongoing accessibility audits and employee training.

Overlays rarely appear in those agreements as acceptable compliance solutions.

Instead, the agreements focus on code-level remediation.

This pattern appears repeatedly in publicly available settlement documents.

the role of wcag in accessibility lawsuits

Although the ADA does not explicitly mention websites, courts frequently rely on WCAG as the benchmark for digital accessibility.

The Web Content Accessibility Guidelines were developed by the World Wide Web Consortium.

WCAG 2.1 includes dozens of success criteria covering accessibility issues such as text alternatives, keyboard access, color contrast, and error identification.

Most ADA website complaints cite specific WCAG criteria.

For example:

WCAG 1.1.1 for missing image alt text.

WCAG 2.4.4 for unclear link purpose.

WCAG 3.3.2 for missing form labels.

When these criteria appear in complaints, the evidence typically refers to underlying code problems.

An overlay does not remove those problems.

That technical reality explains why overlays rarely appear as valid defenses in accessibility litigation.

an example from a restaurant website lawsuit

In 2022 a lawsuit filed in California federal court involved a restaurant website that included an accessibility overlay.

The plaintiff attempted to view the restaurant’s menu using a screen reader.

The menu page used images for each menu category instead of text headings.

None of the images included alt text.

The screen reader announced the images simply as “graphic.”

The overlay allowed the user to increase text size and adjust color contrast.

Those adjustments did nothing to address the missing image descriptions.

The plaintiff documented the issue and included the findings in the complaint.

The case eventually settled.

The restaurant agreed to remediate the website and provide accessible menu content.

The overlay remained on the site but did not resolve the accessibility violation.

the limitations of automated fixes

Accessibility overlays often rely on automated analysis.

The script scans the page and attempts to modify elements dynamically.

Automation has limits.

Accessibility issues frequently require human judgment.

An automated tool cannot determine the appropriate alt text for a product image.

It cannot decide whether a heading structure accurately represents the page hierarchy.

It cannot write meaningful form labels.

Those tasks require manual intervention.

Accessibility professionals often describe overlays as cosmetic adjustments rather than structural fixes.

The analogy used in developer discussions is simple.

An overlay is like placing a filter on top of a photograph with scratches. The scratches remain in the image underneath.

The overlay changes the surface appearance, not the underlying content.

accessibility professionals’ perspective

Developers who specialize in accessibility generally favor remediation.

Accessibility consulting firms typically conduct audits followed by structured remediation work.

A typical accessibility audit may cost anywhere from $3,000 to $15,000 depending on site size and complexity.

Remediation costs vary widely.

A small business site with 20 pages may require $2,000 to $5,000 in remediation work.

A large e-commerce platform with thousands of pages may require ongoing accessibility engineering.

These numbers vary by developer and project scope, but they illustrate the difference between remediation and overlay pricing.

Overlays often cost less in the short term.

Remediation costs more but addresses the actual accessibility barriers.

That difference explains why remediation appears in legal settlements while overlays rarely do.

the trade-off businesses face

Businesses facing ADA website complaints often compare short-term costs against long-term legal risk.

Installing an overlay can happen in minutes.

Remediation may require weeks or months.

The faster option does not necessarily reduce legal exposure.

Some companies install overlays after receiving demand letters and then begin remediation work afterward.

The overlay becomes a temporary measure rather than a compliance strategy.

Critics argue that overlay marketing sometimes misleads business owners about the legal protection provided by these tools.

Several lawsuits have included allegations that overlay advertising overstated compliance claims.

accessibility testing by real users

Some ADA lawsuits involve plaintiffs who are experienced assistive technology users.

They test websites personally and document barriers they encounter.

A blind user using the JAWS screen reader might attempt to purchase an item on an online store.

If the checkout button lacks a proper label, the screen reader may announce it simply as “button.”

The user cannot determine its purpose.

If the overlay fails to correct the label, the accessibility barrier remains.

The user documents the problem and includes it in the complaint.

This type of real-user testing appears in numerous accessibility lawsuits.

It highlights the difference between automated adjustments and genuine accessibility.

what holds up when courts evaluate accessibility

When accessibility lawsuits proceed beyond early settlement discussions, courts typically evaluate whether the website allows disabled users to access the goods or services offered.

The analysis focuses on usability.

Does the screen reader user reach the menu?

Can a keyboard-only user complete checkout?

Can a deaf visitor watch the video with captions?

If the answer is no, the accessibility barrier exists.

The presence of an overlay does not remove that barrier.

Remediation directly addresses the barrier.

That difference determines which approach holds up in court.

what the litigation record shows

Publicly available ADA website complaints filed between 2019 and 2024 show repeated references to WCAG violations, screen reader testing, and automated accessibility reports.

They rarely describe overlays as solutions.

When overlays appear in complaints, they are usually mentioned as ineffective.

Settlement agreements consistently require remediation steps such as accessibility audits, WCAG conformance, and employee training.

The pattern is clear across hundreds of cases.

Accessibility barriers documented in code require code-level fixes.

Overlay scripts do not replace that work.

the practical takeaway from accessibility litigation

Businesses evaluating accessibility solutions often encounter two very different messages.

Overlay vendors promise rapid compliance through automated scripts.

Accessibility professionals emphasize manual audits and remediation work.

Court filings show which approach survives legal scrutiny.

Accessibility barriers documented in ADA lawsuits are tied to the underlying structure of the website.

Fixing those barriers requires direct remediation.

Overlay tools operate on top of the site rather than inside it.

When courts examine whether disabled users can access the site, the underlying code determines the outcome.