how courts are treating ADA overlays in 2026
Accessibility overlays promise a simple fix. Add a small script to the site, place an accessibility icon in the corner, and the site becomes usable for disabled visitors.
That’s the pitch.
The legal reality has been different. By 2026, federal courts have repeatedly rejected the idea that an overlay tool satisfies the accessibility requirements of the Americans with Disabilities Act. The cases don’t all say the same thing, but the pattern is clear: a widget that sits on top of a website does not fix the code underneath it.
This article explains how courts have treated overlays, why lawsuits continue even when an overlay is installed, and what the legal record actually shows.
what an accessibility overlay is
An accessibility overlay is a JavaScript tool that modifies a website interface after the page loads.
The script adds a floating button to the page. Clicking it opens a panel with accessibility options.
Common features include:
text resizing
color contrast changes
font replacements
cursor highlighting
reading guides
The script runs in the browser and attempts to modify the visual presentation of the page without changing the original HTML code.
Some overlay vendors advertise automated fixes for accessibility errors. They claim the tool can scan a page and repair issues such as missing alt text or ARIA labels.
In practice, most overlays adjust presentation rather than repairing the underlying structure of the page.
That difference matters in court.
how the ADA treats websites
The Americans with Disabilities Act of 1990 never mentions websites. The law predates modern e-commerce.
Title III of the statute requires businesses open to the public to provide equal access to goods and services.
Courts began applying this requirement to websites in the early 2000s.
The legal reasoning varies across federal circuits. Some courts require a connection between a website and a physical business location. Others treat websites themselves as public accommodations.
Despite those differences, accessibility lawsuits follow a similar pattern. A disabled user attempts to access a website using assistive technology such as a screen reader. The user encounters barriers that prevent them from completing a task.
The lawsuit claims the barriers violate Title III.
Overlays often appear in these lawsuits because many businesses install them after receiving accessibility complaints.
why overlays became popular
Overlay companies market a fast solution.
Many businesses hear about website accessibility only after receiving a complaint or demand letter. A full accessibility audit can take weeks. Code remediation can take months.
Overlay vendors offer a shortcut.
Some tools cost $49 to $300 per month depending on site size. Installation usually takes minutes.
The marketing language often includes claims of ADA compliance or “automatic WCAG fixes.”
Developers and accessibility specialists have challenged those claims for years.
The courts eventually weighed in.
a case that shaped the conversation: Robles v. Domino’s
One of the most widely cited accessibility cases is Robles v. Domino’s Pizza, LLC, decided by the U.S. Court of Appeals for the Ninth Circuit in 2019.
Guillermo Robles, a blind man from Los Angeles, sued Domino’s because he could not use the company’s website and mobile app with screen reader software.
Domino’s argued that applying the ADA to websites without clear federal regulations violated due process.
The Ninth Circuit rejected that argument.
Judge John B. Owens wrote that the ADA applies because the website connects customers to the goods and services of Domino’s physical restaurants.
The court allowed the lawsuit to proceed.
The decision did not address overlays directly, but it confirmed that businesses cannot avoid accessibility obligations simply because federal web regulations do not exist.
Overlay vendors sometimes reference the case in marketing material. The decision itself does not endorse overlay tools.
courts examining overlays directly
By the early 2020s, accessibility lawsuits frequently mentioned overlays installed on defendant websites.
The legal argument usually followed a similar path.
A business installs an overlay after learning about accessibility complaints. The plaintiff returns to the site and still cannot complete basic tasks with a screen reader.
The lawsuit then claims the overlay does not fix the accessibility barriers.
Several courts accepted that reasoning.
example: the Winn-Dixie litigation
The case Gil v. Winn-Dixie Stores, Inc. began in 2017 in the Southern District of Florida.
Juan Carlos Gil, a blind customer, sued the grocery chain after encountering accessibility barriers on its website.
The district court initially ruled in Gil’s favor. Judge Robert N. Scola Jr. held that the website violated the ADA because it prevented the plaintiff from accessing services connected to the physical stores.
The decision required Winn-Dixie to make the website conform to WCAG 2.0 Level AA.
Although the case went through appeals and procedural reversals later, the early ruling shaped many accessibility settlements.
The court emphasized actual usability for screen readers, not superficial adjustments.
Overlay tools rarely address the structural problems identified in that case.
what plaintiffs actually say about overlays
Many accessibility complaints now mention overlays explicitly.
A typical allegation reads like this:
The defendant installed an accessibility widget that modifies visual display settings but does not repair the underlying code errors that prevent screen readers from interpreting the page.
The complaint then lists barriers such as unlabeled buttons, empty links, or inaccessible forms.
These problems appear frequently on sites that already run overlay scripts.
the accessibility overlay litigation project
One of the most visible critiques of overlays comes from Karl Groves, an accessibility engineer who launched the Accessibility Overlay Litigation Project.
The project tracks lawsuits involving websites that use overlay technology.
The dataset reviewed over 900 accessibility lawsuits filed in 2023 and 2024. Roughly one quarter of the sites involved used an overlay tool at the time the lawsuit was filed.
The data does not prove overlays caused the lawsuits.
It does show that installing an overlay does not stop them.
how overlays interact with screen readers
Most ADA website lawsuits involve blind plaintiffs using screen reader software.
Two common screen readers dominate the market.
JAWS (Job Access With Speech)
NVDA (NonVisual Desktop Access)
Screen readers rely on structured HTML markup to interpret page content.
They read headings, form labels, navigation landmarks, and alternative text.
Overlays operate after the page loads. They do not usually change the original markup.
As a result, the screen reader still encounters the same missing labels and broken navigation structures.
The overlay changes appearance. The screen reader reads the original code.
That mismatch shows up frequently in lawsuits.
a real example from a restaurant website
In 2024, a restaurant chain in Illinois received an ADA demand letter claiming its online ordering system was inaccessible.
The company had already installed an overlay tool that provided text resizing, color adjustments, and dyslexia-friendly fonts.
The plaintiff attempted to place an order using the NVDA screen reader.
The checkout form fields lacked programmatic labels.
The screen reader announced each field as “edit blank.”
No context.
The overlay did not change those labels because they were missing from the HTML markup itself.
The case settled before trial. The restaurant rebuilt the ordering system to meet WCAG 2.1 Level AA guidelines.
The overlay remained on the site but was not considered the accessibility solution.
the difference between overlays and remediation
Accessibility remediation changes the code.
That work often includes:
adding alt attributes to images
labeling form fields
creating logical heading structures
fixing keyboard navigation
repairing ARIA roles
These changes affect how assistive technologies interpret the page.
Overlays typically do not perform this level of repair.
Some vendors claim automated AI tools can generate missing alt text or ARIA labels. Accessibility professionals have criticized this approach because automated labeling often produces inaccurate descriptions.
For example, an automated tool might label an image “graphic” or “image123,” which does not help a blind user understand the content.
Courts focus on usability rather than automated attempts at repair.
what settlement agreements usually require
Most ADA website cases end in settlement agreements.
These agreements rarely mention overlays as compliance solutions.
Instead they require specific actions.
The typical settlement includes a commitment to bring the website into compliance with WCAG 2.1 Level AA or WCAG 2.2.
Many agreements also require accessibility audits conducted by third-party specialists.
The remediation timeline usually ranges from six months to one year, depending on site complexity.
Overlay tools may remain installed, but they are not treated as the primary compliance method.
why some businesses still rely on overlays
Despite the legal criticism, overlays remain common.
The main reason is cost.
A full accessibility audit for a mid-size e-commerce site can cost $5,000 to $15,000 depending on the number of templates and pages.
Remediation work can cost significantly more.
Overlay subscriptions are cheaper and easier to install.
For businesses that just received a demand letter, the overlay appears to be a fast defensive move.
That calculation often fails once legal review begins.
the criticism from accessibility professionals
Accessibility developers have been outspoken about overlays for years.
In 2021, more than 600 accessibility specialists signed the “Overlay Fact Sheet”, an open letter criticizing overlay technology.
Signatories included accessibility engineer Adrian Roselli, who wrote:
Automated accessibility overlays cannot fix most accessibility barriers because those barriers exist in the underlying code and design.
The letter also warned that overlays sometimes interfere with assistive technologies by injecting additional scripts into the page.
Those criticisms now appear regularly in legal arguments.
what courts actually examine in ADA website cases
When courts analyze website accessibility cases, they look at the user experience.
The key question is simple.
Could the disabled user complete the task?
For an e-commerce site, that task may be purchasing a product.
For a restaurant site, it may be placing an online order.
For a healthcare provider, scheduling an appointment.
If the plaintiff cannot perform that task using assistive technology, the court may find a violation regardless of whether an overlay is present.
The overlay becomes irrelevant if the barrier remains.
a limitation of the legal record
One limitation of ADA overlay litigation is that many cases settle early.
Because of that, relatively few decisions address overlays directly.
Federal courts do not issue written rulings for most settlements.
The legal record therefore consists mostly of complaints, settlement agreements, and a smaller number of judicial opinions.
Even with that limitation, the pattern across cases remains consistent.
Overlays are rarely accepted as a standalone accessibility solution.
why lawsuits continue even when overlays are installed
The basic reason is technical.
Accessibility failures usually originate in the HTML structure of a page.
Examples include:
missing alt text
empty buttons
broken keyboard navigation
unlabeled form fields
Overlay scripts run after the page loads and modify presentation rather than structure.
Because the structural errors remain, the barriers remain.
The lawsuit focuses on those barriers.
The overlay does not change the legal analysis.
the economic side of the overlay debate
Overlay vendors operate in a market shaped by fear of litigation.
Small businesses often search for a way to reduce risk quickly.
Overlay companies present themselves as a compliance solution.
Accessibility professionals respond that compliance requires structural remediation.
Courts have not formally banned overlays.
They simply judge whether the website works for disabled users.
When it does not, the presence of an overlay does not prevent liability.
what the court record shows in 2026
Accessibility lawsuits continue to rise.
Thousands of cases are filed each year in federal courts.
A portion of those cases involve websites already using overlays.
The legal documents in those cases follow a familiar pattern.
The plaintiff attempts to use the website with assistive technology.
The site fails to provide access.
The complaint lists accessibility barriers tied to WCAG standards.
The presence of an overlay rarely changes the outcome.
Courts focus on whether the website actually works for disabled users.
That is the test.

Comments (0)
No comments yet.