ADA Website Compliance in 2026: Lawsuit Risk, WCAG 2.2, Overlays and Cost

Key takeaways

• Plaintiffs filed 3,117 website accessibility lawsuits in US federal courts in 2025, up 27% from 2,452 in 2024, per Seyfarth Shaw; UsableNet, which also counts New York and California state courts, tracked more than 5,000.
• In UsableNet's 2025 report, 70% of digital accessibility suits targeted e-commerce, 64% of the companies sued had revenue under $25 million, and 1,427 suits named a company that had been sued before.
• About 20% of companies sued in 2026 had an accessibility widget or overlay installed, per UsableNet's July 2026 update, and in April 2025 the FTC ordered accessiBe to pay $1 million over claims its tool could make any website WCAG-compliant.
• The European Accessibility Act has applied since June 28, 2025 to e-commerce offered to consumers in the EU, whoever offers it; service microenterprises with fewer than 10 staff and turnover or a balance sheet of €2 million or less are exempt.
• The UAE's National Policy for Digital Accessibility (TDRA, March 2024) requires WCAG 2.1 AA for public service sites; it applies to federal entities and the companies that build for them or transact with them, and asks other private firms for best efforts.

If your business sells to the US public, treat WCAG 2.2 AA as your website's target. No ADA regulation sets a web standard for private businesses, but the Justice Department says the ADA covers what they offer online, and its 2022 guidance names WCAG as helpful guidance. Plaintiffs filed 3,117 website accessibility suits in federal court in 2025, up 27% from 2024, and UsableNet counted more than 5,000 once New York and California state courts are included.

This guide is for US owners who got a demand letter or fear one, and for UAE companies that sell to the US or the EU or work with government. It covers the rules as of October 30, 2026, who gets sued, what WCAG 2.2 changed, why overlays don't protect you, and what a fix involves and costs.

Do you need ADA website compliance?

It depends on where your customers are and whom you work for. Sell to the US public, and ADA claims apply. Sell to EU consumers, and the European Accessibility Act does. Build for the UAE federal government or transact with it digitally, and the TDRA policy does.

Accessibility rules a US or UAE business may meet online. Laws, rules and policies as published, checked October 30, 2026.

What does the ADA require for websites in 2026?

Title III of the ADA covers businesses open to the public, and the DOJ says that includes the goods and services they offer on the web. Its March 2022 guidance is not binding. It calls WCAG and the federal Section 508 standards helpful guidance and lists common barriers such as poor color contrast, missing alt text, videos without captions, unlabeled forms and pages that work only with a mouse. Outside the ADA, airlines and recipients of HHS funding have their own federal web rules.

There is still no Title III web regulation; the DOJ wrote one for governments instead. Its Title II rule, published April 24, 2024, requires state and local government websites and apps to meet WCAG 2.1 AA. An interim final rule on April 20, 2026 moved the deadlines back a year: to April 26, 2027 for governments serving 50,000 people or more, and to April 26, 2028 for smaller ones and special districts. Seyfarth Shaw, a law firm that tracks these cases, notes that Title III rulemaking is now paused indefinitely.

On May 21, 2026, the National Federation of the Blind sued in federal court in Maryland to set the extension aside and restore the original dates. We found no ruling as of October 30, 2026.

For a business, this matters in two ways. A site you build for a city, county or state agency must meet WCAG 2.1 AA by that client's deadline. For private sites, WCAG is the standard the DOJ itself points to, so build and test to it.

How many website accessibility lawsuits are filed, and who gets sued?

Two trackers count these suits, by different methods. Seyfarth Shaw counts federal court only: 3,117 website suits in 2025, up from 2,452 in 2024, or 36% of all 8,667 Title III suits. New York led with 1,021, then Florida with 961 and Illinois with 585. California's federal courts had 4, which Seyfarth ties to rulings there that online-only businesses are not covered by the ADA.

UsableNet, which sells accessibility services, adds New York and California state courts: more than 5,000 suits in 2025, 3,195 in federal court and 1,919 in state courts. By its method, federal filings fell slightly. Its report shows who gets sued:

• Online stores. 70% of suits targeted e-commerce.
• Smaller companies. 64% of the companies sued had revenue under $25 million.
• Repeat targets. 1,427 suits, 45% of federal cases, named a company that had been sued before.

The pace rose in 2026. Seyfarth's mid-year report counts 5,006 federal Title III suits of all kinds in the first half, up 9% from 4,575, without a website split. UsableNet's July 2026 update puts website and app suits on pace for about 6,000 this year, up roughly 20–25%. About 80% target e-commerce, about a quarter hit repeat defendants, and demand letters run two to three times the number of suits. More of the risk arrives as a letter than as a lawsuit.

California, New York and other states

California's Unruh Civil Rights Act bars all businesses in the state from discriminating on the basis of disability, with damages of at least $4,000 per violation, per the state's Civil Rights Department.

We found no New York law that sets a web standard for private sites, yet New York is where most suits land. Seyfarth notes that New York federal judges have grown more demanding about standing, which has led many plaintiffs to file in New York and New Jersey state courts. Those suits are not in its federal count.

Some states push back on volume filers. Missouri enacted a law in early May 2026, in effect since August 28, 2026, that presumes a website suit abusive if the business, after written notice, began substantial good-faith steps and fixed the problem within 90 days, as the court determines. A Missouri resident or a business registered there can then sue the plaintiff, lawyer or law firm behind the suit for its legal fees and costs, and the court may add sanctions of up to three times those fees. In courts and statehouses alike, prompt fixes and records of them count.

Does the European Accessibility Act apply to you?

If you sell to consumers in the EU, probably yes. Directive (EU) 2019/882, the European Accessibility Act, has applied since June 28, 2025. It covers e-commerce, meaning services provided at a distance through websites and mobile apps at a consumer's request to conclude a consumer contract. It also covers consumer banking, e-books, electronic communications, access to audiovisual media, and passenger transport websites, apps and e-tickets.

For US and UAE sellers, the key is the definition of a service provider: anyone who provides a service on the EU market or offers it to consumers in the EU. A store abroad that sells to EU shoppers fits that wording. The limits:

• Microenterprises. Fewer than 10 staff and annual turnover or a balance sheet of €2 million or less: exempt for services, though not for products.
• Older content. Recorded media and office files published before June 28, 2025, unmaintained archives and third-party content you don't fund, develop or control are out of scope.
• Transition. Until June 28, 2030, services may keep using products they already used before June 28, 2025, and older service contracts may run to their end, for five years at most.

The directive does not name WCAG. It sets its own accessibility requirements, and each EU country sets penalties that must be "effective, proportionate and dissuasive". Our advice: build to WCAG 2.2 AA and ask EU counsel what the countries you sell to expect.

Is WCAG mandatory in the UAE?

For government work, yes. For most private sites, not yet. The TDRA's National Policy for Digital Accessibility, issued in March 2024, says all public service sites must comply with WCAG 2.1 level AA. It applies to:

• Federal government. Ministries, authorities and institutions, which must also publish an accessibility statement.
• Companies working with them. Semi-government entities, consultants and private companies in electronic transactions with a federal entity, plus partners, contractors and outsourced staff.
• Builders. Service providers that develop websites and apps for federal entities.
• Regulated sectors. A federal regulator must liaise with the private companies it licenses to ensure compliance.

Local government, semi-government and the private sector at large "should take this document into account, and exert the best efforts in compliance".

Dubai adds its own layer. Law No. 3 of 2022, on the rights of persons with disabilities, cites Federal Law No. 29 of 2006 and defines accessibility to include information and digital platforms. Its implementing bylaw requires government entities to make digital services accessible and tasks the Dubai Digital Authority with technical standards for digital channels and with supervising compliance by the public and private sectors. One private duty is explicit: banks must make their websites, smart apps and ATMs accessible to the latest standards, checked by the Department of Economy and Tourism. The bylaw's fines run from AED 5,000 to AED 50,000 and double for a repeat within a year, up to the law's cap of AED 100,000, but the fine schedule has no line for websites. We found no website requirement in the Dubai Universal Design Code, which deals with buildings and transport.

We found no published Dubai Digital Authority standard for private websites as of October 30, 2026. So for a UAE company: build for a federal entity or deal with one electronically, and the policy and its WCAG 2.1 AA target apply to you. Run a bank in Dubai, and accessible websites and apps are required too. Sell to US or EU consumers, and the rules above apply. Otherwise it is best effort today, and a build or a redesign is the easiest moment to get there.

WCAG 2.2 compliance: what changed from 2.1

WCAG 2.2 became a W3C Recommendation on October 5, 2023, and in October 2025 it was approved as ISO/IEC 40500:2025. The 2.1 criteria carry over with one exception: 4.1.1 Parsing is obsolete and removed. Six of the nine new criteria are at levels A and AA:

• Focus Not Obscured (Minimum), AA. A link or field a keyboard user tabs to stays at least partly visible, not hidden under a sticky header or a cookie banner.
• Dragging Movements, AA. Anything done by dragging, such as a slider, also works with a simple click or tap.
• Target Size (Minimum), AA. Buttons and links are at least 24 by 24 CSS pixels or have enough space around them.
• Consistent Help, A. Help, such as a phone number or a chat, sits in the same place on every page.
• Redundant Entry, A. Don't ask for the same information twice in one session, such as a shipping address at checkout.
• Accessible Authentication (Minimum), AA. Don't make people solve, recall or transcribe something to log in.

The other three are AAA. If your site meets 2.1 AA, the gap to 2.2 AA is mostly focus visibility, target sizes, and login and checkout forms.

The basics still fail most often. The WebAIM Million, an automated scan of the top million home pages in February 2026, found detected WCAG 2 failures on 95.9% of them, up from 94.8%, with 56.1 errors per page on average, up from 51.

The six most common WCAG failures on the top million home pages. WebAIM Million 2026, checked October 30, 2026.

These are template problems more than page problems: fix the button, the product card or the color tokens once, and the error leaves every page.

Do accessibility overlays work?

An overlay, or accessibility widget, is a script that adds a toolbar to your site and promises to fix accessibility automatically. It won't protect you:

• Suits keep coming. UsableNet found over 1,000 businesses sued in 2024 despite having a widget, out of more than 4,000 suits. Its 2025 report says widgets "did not slow litigation", with 95 to 155 suits a month against sites that had one. In 2026, about 20% of the companies sued had one, per UsableNet.
• The code stays broken. The same 2025 report says widgets typically do not resolve code-level issues and may interfere with screen readers.
• The FTC acted. Its January 2025 complaint said accessiBe claimed its accessWidget could make any website WCAG-compliant and formatted third-party articles and reviews to look independent. In April 2025 the FTC approved a final order requiring accessiBe to pay $1 million and barring it from claiming, without evidence to back it, that its automated products can make any website WCAG-compliant.

What fixing involves and what ADA compliance costs

A fix is a project, not a plugin:

1. Scan every template. Scan each page type, not only the home page. The W3C is clear that tools cannot check all accessibility aspects automatically and human judgment is required.
2. Audit key flows by hand to WCAG 2.2 AA. Navigation, search, product page, cart, checkout, account and forms.
3. Test with a keyboard and a screen reader. Every key flow without a mouse, then with VoiceOver or NVDA.
4. Fix the design system. Contrast in color tokens, focus styles, labels in components, target sizes in buttons and links. One fix reaches every page.
5. Publish a statement and a feedback channel. The W3C's guide to accessibility statements suggests at minimum your commitment, the standard you apply and contact details, ideally with known limitations. It notes that a statement is not a declaration of conformity.
6. Monitor. A scan on every release, a manual retest after big changes, and training for whoever edits content.

Records matter. In March 2026 a federal court in New York dismissed a suit against Moscot as moot. The company filed a declaration from its director of e-commerce and an audit report from an accessibility consultant it had worked with since 2023. The one low-severity issue found had been fixed, and the plaintiff offered no evidence in reply. The city-law claim was dismissed without prejudice, so it can be refiled in state court, but documented work ended the federal case.

What the market charges

These are market figures from vendors that sell this work, not our price list. TestParty names unique templates, dynamic states, the assistive technologies tested and retesting as the main cost drivers.

Published market prices for accessibility audits and fixes. Vendor pages, not NextGenSoft rates; checked October 30, 2026.

TestParty's ranges come from published agency rates as of August 2026; Accessible.org updated its page on October 29, 2026. For the rest of a site budget, see what a website costs. If a redesign is coming anyway, fold the fixes into it and keep your rankings through the move.

What our own sites show

None of our published cases is a WCAG audit or an ADA remediation. Google Lighthouse scores accessibility on mobile at 93 for the US store we built for Esturión and 96 for Encore's site. That score is a weighted average of automated checks; manual checks don't affect it. A high score means the basics a tool can see are in place. It is not WCAG conformance and not protection from a suit. What does carry over is the way we build, on shared components and design tokens.

Case study · Esturión de SarriónOnline store for premium caviar, truffles and wagyu45gourmet products, from caviar tins to A5 wagyu

To review usability at the same time, see what a UX audit includes and ask for the WCAG check as a separate line. Choosing a studio for the work? Our agency guide lists the accessibility questions to ask.

Checklist: next steps for ADA website compliance

• Map your rules. Mark which rows of the first table apply to you.
• Set the target. WCAG 2.2 AA, written into the brief and every build or maintenance contract.
• Scan every template. Contrast, alt text, labels, empty links and buttons.
• Audit the money flows by hand. Search, product, cart, checkout, sign-in and forms, with a keyboard and a screen reader.
• Fix the components. Tokens, focus styles, labels and target sizes, then a retest.
• Skip the overlay. It won't stop a suit.
• Publish a statement. Commitment, standard, known limitations and a contact a person answers.
• Keep records and monitor. Dated audits, fixes and retests, and a scan on every release.
• Call counsel about letters. A lawyer sees any demand letter before you reply.

Our website design and development service covers design systems, builds and redesigns. Tell us about your site and a partner will say where to start.

Questions we get asked

Is there a US law that says my website must meet WCAG?

Not for most private businesses. No ADA regulation sets a web standard for them, and the DOJ's 2022 guidance calls WCAG helpful guidance while leaving businesses flexibility in how they comply. Demand letters and courts still ask whether people with disabilities can use the site, so WCAG 2.2 AA is the practical target. Rules that do name WCAG 2.1 AA cover US state and local governments under Title II and, in the UAE, federal entities and their contractors.

I got an ADA demand letter. What should I do first?

Call a lawyer before you reply or pay anything. Then get a manual audit of the pages and flows the letter names, fix what it finds and keep dated records of the work. In March 2026 a federal court in New York dismissed a website suit against Moscot as moot after the company filed an accessibility consultant's audit report and a declaration, and the plaintiff offered nothing in reply. An overlay installed after the letter is not a fix.

Will an accessibility overlay or widget protect me from a lawsuit?

The data says no. About 20% of companies sued in 2026 had a widget or overlay installed, according to UsableNet's July 2026 update, and its 2025 report says widgets typically don't fix code-level issues and may interfere with screen readers. In April 2025 the FTC ordered accessiBe to pay $1 million and barred it from claiming, without evidence to back it, that its automated products can make any website WCAG-compliant. Fix the code and templates instead.

How much does ADA website compliance cost?

These are market figures, not our price list. Accessible.org lists a manual WCAG 2.1 or 2.2 AA audit at $1,250–$2,750 for most clients and remediation at $750–$4,500. TestParty's 2026 guide, based on published agency rates, puts a full manual audit of a mid-size online store at about $3,000–$15,000 or more. The number of unique templates and interactive states drives the price more than the page count does, and retesting after fixes adds to it.

Does the European Accessibility Act apply to a US or UAE company?

It can. Since June 28, 2025, the EAA has covered e-commerce offered to consumers in the EU, and it defines a service provider as anyone who provides such a service on the EU market or offers it to EU consumers. A store in the US or the UAE that sells to EU shoppers fits that wording. Service microenterprises, with fewer than 10 staff and turnover or a balance sheet of €2 million or less, are exempt. Each EU country sets its own penalties.

Is WCAG compliance mandatory for private websites in the UAE?

Not across the board. The TDRA's National Policy for Digital Accessibility, issued in March 2024, requires WCAG 2.1 AA for public service sites and applies to federal entities, the companies that build their sites and apps, and those that transact with them electronically. Other private firms are asked to make best efforts. In Dubai, the implementing bylaw of Law No. 3 of 2022 requires banks to make their websites, apps and ATMs accessible in line with the latest standards.

Sources

1. Guidance on Web Accessibility and the ADA · U.S. Department of Justice, Civil Rights Division, 2022
2. Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments · U.S. Department of Justice, Civil Rights Division, 2026
3. 14 CFR § 382.43: Must information and reservation services of carriers be accessible to individuals with visual, hearing, and other disabilities? · Legal Information Institute, Cornell Law School
4. 45 CFR § 84.84: Requirements for web and mobile accessibility · Legal Information Institute, Cornell Law School
5. Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025 · Seyfarth Shaw, ADA Title III News & Insights, 2026
6. 2026 Mid-Year Report: ADA Title III Federal Lawsuit Numbers Are Climbing · Seyfarth Shaw, ADA Title III News & Insights, 2026
7. DOJ Extends ADA Title II Website Accessibility Deadlines for Governmental Entities—But Litigation and Compliance Risks Remain · Seyfarth Shaw, ADA Title III News & Insights, 2026
8. National Federation of the Blind Challenges Last-Minute Deadline Extensions for Website and Mobile App Accessibility · Seyfarth Shaw, ADA Title III News & Insights, 2026
9. Missouri Passes Law to Deter "Abusive" Website Litigation · Seyfarth Shaw, ADA Title III News & Insights, 2026
10. Lawsuit Dismissed As Moot Based on (Unrebutted) Evidence that Website is Accessible · Seyfarth Shaw, ADA Title III News & Insights, 2026
11. 2024 Digital Accessibility Lawsuit Report Released: Insights for 2025 · UsableNet, 2025
12. 2025 Year-End Digital Accessibility Lawsuit Report · UsableNet
13. Digital Accessibility Lawsuits in 2026: Five Trends Companies Should Know · UsableNet, 2026
14. Outreach Newsletter, October 2021: Unruh Civil Rights Act · California Civil Rights Department (formerly DFEH), 2021
15. FTC Approves Final Order Requiring accessiBe to pay $1 Million · Federal Trade Commission, 2025
16. Directive (EU) 2019/882 on the accessibility requirements for products and services (European Accessibility Act) · EUR-Lex, 2019
17. National Policy for Digital Accessibility · UAE Telecommunications and Digital Government Regulatory Authority (TDRA), 2024
18. Law No. (3) of 2022 Concerning the Rights of Persons with Disabilities in the Emirate of Dubai · Dubai Supreme Legislation Committee, 2022
19. Executive Council Resolution No. (1) of 2022 Issuing the Implementing Bylaw of Law No. (3) of 2022 · Dubai Supreme Legislation Committee, 2022
20. What's New in WCAG 2.2 · W3C Web Accessibility Initiative, 2023
21. WCAG 2.2 Approved as an ISO Standard · W3C Web Accessibility Initiative, 2025
22. The WebAIM Million · WebAIM, 2026
23. Selecting Web Accessibility Evaluation Tools · W3C Web Accessibility Initiative, 2024
24. Developing an Accessibility Statement · W3C Web Accessibility Initiative, 2021
25. Lighthouse accessibility scoring · Chrome for Developers
26. Pricing · Accessible.org, 2026
27. Accessibility Audits in 2026: Types, Process, Cost Ranges & Deliverables · TestParty, 2026

Share this article

About the author

Artsiom Yankovich

Co-founder, Head of Design & Strategy

Leads design and strategy, from product logic to brand. 9+ years, 150+ projects.

Meet the leadership