Journal · Markets and the law
ADA website lawsuits: what contractors and remodelers should know
No federal rule sets a technical standard for a private contractor's website, but the Justice Department says the ADA covers web content, and UsableNet counted 5,114 digital accessibility lawsuits in 2025. What lowers the risk is a site built to WCAG 2.2 AA in its code, not a widget: described project photos, readable contrast and a quote form that works by keyboard.
- Written by
- Abdelrahman Shalaby, founder of Fairhewn
- Last updated
- Reading time
- 10 minutes
In this guide10 sections
- What the ADA says about websites
- The 2024 government rule, and why it matters to you
- The lawsuit numbers, year by year
- Who gets sued
- California: the Unruh Act
- Why an overlay widget won’t protect you
- ADA website compliance in practice: WCAG 2.2 AA on a remodeler’s site
- An accessibility statement
- A 12-point checklist
- Sources
Website accessibility lawsuits are a volume business in the US. A small group of plaintiff firms files thousands a year, mostly in New York, Florida and now Illinois, mostly against online stores and restaurants. A remodeler, a kitchen-and-bath firm or an interior design studio is a less common target, but not an exempt one. This guide covers what the law says, the lawsuit numbers by year and state, and California’s damages. Then it covers why overlay widgets don’t help, and what WCAG 2.2 AA means on a remodeling site. It ends with a 12-point checklist.
This is information, not legal advice. If a demand letter or a complaint arrives, take it to a US lawyer who handles ADA cases before you reply. I build websites for remodeling and design firms, US firms included, working remotely.
What the ADA says about websites
Title III of the Americans with Disabilities Act covers businesses open to the public, which the law calls public accommodations. The Justice Department’s web guidance of 18 March 2022 says that “since 1996” it “has consistently taken the position that the ADA applies to web content” (ADA.gov, 18 Mar 2022).
Three points in that guidance matter to a contractor:
- There is no detailed federal rule for private websites. The Department “does not have a regulation setting out detailed standards”. Businesses “can currently choose how they will ensure” that what they offer online is accessible.
- WCAG is the reference. The guidance names the Web Content Accessibility Guidelines (WCAG) and the federal Section 508 Standards as helpful technical guidance.
- It names the usual barriers. Poor color contrast, images without alt text, videos without captions, forms without labels, and pages that only work with a mouse.
Flexibility is not an exemption. The same page says businesses “still must ensure” that what they provide online is accessible to people with disabilities.
Whether a given remodeler counts as a public accommodation, and whether its site must connect to a physical place, is where courts split. Seyfarth Shaw’s ADA Title III team reports that California’s federal and state appeals courts have held online-only businesses are not covered. Most New York district judges who have ruled on it say they are (Seyfarth Shaw, 25 Mar 2026). If clients visit your showroom, studio or office, plan as if your website is covered.
The 2024 government rule, and why it matters to you
On 24 April 2024 the Federal Register published a Justice Department rule for state and local governments under Title II. It makes WCAG 2.1 Level AA “the technical standard” for their web content and mobile apps. On 20 April 2026 an interim final rule moved the compliance dates back by a year. Governments serving 50,000 people or more now have until 26 April 2027. Smaller ones and special districts have until 26 April 2028 (ADA.gov fact sheet).
The rule does not apply to private businesses. It matters as a signal. When the Department did write a technical web standard into a rule, it chose WCAG 2.1 AA. The same fact sheet treats PDFs and other documents posted online as content that has to meet it, with narrow exceptions for some older and archived files.
WCAG 2.2 became a W3C Recommendation on 5 October 2023. W3C says content that conforms to 2.2 “also conforms to WCAG 2.0 and WCAG 2.1” (W3C, WCAG 2.2). Build to 2.2 AA and you cover the government’s bar as well.
The lawsuit numbers, year by year
Two trackers publish yearly counts. They count differently, so their figures don’t match and shouldn’t be added together.
Seyfarth Shaw counts website accessibility suits in federal court only:
| Year | Federal website accessibility suits | Change |
|---|---|---|
| 2018 | 2,258 | |
| 2019 | 2,256 | flat |
| 2020 | 2,523 | +14% |
| 2021 | 2,895 | +12% |
| 2022 | 3,255 | +12% |
| 2023 | 2,794 | −14% |
| 2024 | 2,452 | −13% |
| 2025 | 3,117 | +27% |
Source: Seyfarth Shaw, 25 Mar 2026. Website cases were 36% of all 8,667 ADA Title III suits filed in federal court in 2025. Seyfarth points to new plaintiff firms, and notes the cases are easy to file because plaintiffs “don’t even need to leave their homes”.
UsableNet counts websites, mobile apps and video, in federal court and in key state courts:
- 2024: “over 4,000” suits (UsableNet, 3 Jan 2025).
- 2025: 5,114 suits: 3,195 in federal courts and 1,919 in New York and California state courts (UsableNet, 2025 year-end).
- 2026: about 6,176 projected from filings to 14 June, which UsableNet calls a record (UsableNet, 2026 midyear).
Where the suits are filed
In federal court in 2025, New York had 1,021 website suits, Florida 961, Illinois 585, Minnesota 162, Pennsylvania 137 and California 4 (Seyfarth). Adding up UsableNet’s monthly 2025 figures, across federal and state courts, gives about 2,742 for New York, 977 for Florida and 226 for California.
Two details matter if you work outside those states:
- UsableNet says a company does not need to be based in New York to be sued there. Courts accept cases against businesses whose websites New York residents can use, “even without a physical presence in the state”.
- New York federal judges now ask more of plaintiffs on standing, which Seyfarth says has pushed many filings into New York and New Jersey state courts.
In the first half of 2026, UsableNet saw Illinois climb to second place behind New York, “on the strength of a single high-volume plaintiff firm”. Florida was third.
Who gets sued
The UsableNet data describes the usual defendant:
- Smaller companies. Companies with under $25 million in yearly revenue were 64% of 2025 cases. In the first half of 2026, 68% of cases involved companies under $50 million.
- Online stores first. E-commerce was 70% of 2025 cases and food service 21%. By mid-2026 e-commerce was 79%.
- Repeat defendants. 1,427 suits in 2025 targeted companies that had been sued before. UsableNet’s advice is that a partial fix leaves a company open to the next claim.
UsableNet adds that plaintiffs “must establish a legitimate reason for using the site and the likelihood of returning”, which is why busy shopping sites draw most suits. A remodeling site sees fewer visits than a store. But a homeowner comparing kitchen remodelers has a plain reason to use yours and come back, and your quote form is a service you offer online.
California: the Unruh Act
California’s Unruh Civil Rights Act says a violation of the ADA “shall also constitute a violation” of the state act (Civil Code § 51(f)). Civil Code § 52(a) sets damages for each offense at up to three times actual damages. The floor is “in no case less than four thousand dollars ($4,000)”, plus attorney’s fees (Civil Code § 52).
California’s federal courts saw only 4 website suits in 2025. Seyfarth’s explanation is the appeals rulings on online-only businesses. It adds that demand letters and state court suits continue, “especially against businesses with physical locations”. A California remodeler with a showroom is that business.
Why an overlay widget won’t protect you
An overlay is a script that adds an accessibility button or toolbar to a site and promises compliance for a monthly fee. The evidence runs against it.
- The FTC acted against the best-known one. On 3 January 2025 the FTC announced an order requiring accessiBe to pay $1 million. The complaint said its accessWidget “did not make all user websites WCAG-compliant”, despite claims that it “can make any website compliant” (FTC, 3 Jan 2025). The Commission approved the final order 3-0 on 22 April 2025. It bars accessiBe from claiming its automated products can make any website WCAG-compliant unless it has evidence (FTC, 22 Apr 2025).
- Sites with widgets keep getting sued. UsableNet counted over 1,000 suits against businesses using widgets in 2024, more than 25% of cases (UsableNet, 3 Jan 2025). Its 2025 monthly figures add up to 1,416 (UsableNet, 2025 year-end). Its view: widgets “typically do not resolve underlying code-level accessibility issues” and may interfere with screen readers.
A widget sits on top of the code. The barriers a plaintiff’s tester finds are in the code: an unlabeled form field, a lightbox the keyboard can’t close, a photo with no description. Fix those, and a widget adds nothing.
ADA website compliance in practice: WCAG 2.2 AA on a remodeler’s site
WebAIM tested the home pages of the top 1,000,000 websites in February 2026. 95.9% had detectable WCAG 2 failures, with 56.1 errors per page on average. The most common were low-contrast text (83.9% of pages), images without alt text (53.1%) and form fields without labels (51%) (WebAIM Million 2026). Remodeling sites lean on photos, pale palettes and quote forms, so those three are where to start.
Here is what WCAG 2.2 AA asks of the parts every remodeling site has:
| On your site | What it needs | WCAG 2.2 criterion |
|---|---|---|
| Project photos | Alt text that says what the photo shows: “Walnut island with quartz top, open-plan kitchen”. Decorative images get empty alt text. | 1.1.1 (A) |
| Before-and-after slider | It works by click or keys, not only by dragging the handle | 2.5.7 Dragging Movements (AA, new in 2.2) |
| Gallery lightbox | Opens, pages and closes by keyboard; focus doesn’t get stuck inside; a visible focus ring | 2.1.1, 2.1.2 (A); 2.4.7 (AA) |
| Text on photos, beige-on-cream palettes | Contrast of at least 4.5:1 for body text and 3:1 for large text; 3:1 for buttons and field borders | 1.4.3, 1.4.11 (AA) |
| Quote form | A label on every field; errors named in words; a multi-step form doesn’t ask for the same details twice | 3.3.2, 3.3.1, 3.3.7 (A) |
| Project videos | Captions on anything spoken; audio description, or narration, where the visuals carry the information | 1.2.2 (A), 1.2.5 (AA) |
| Hero slideshow | A pause control if it moves for more than five seconds | 2.2.2 (A) |
| Arrows and buttons on a phone | At least 24 by 24 CSS pixels, or spaced apart | 2.5.8 Target Size (AA, new) |
| Sticky header or cookie banner | Doesn’t fully hide the item that has keyboard focus | 2.4.11 Focus Not Obscured (AA, new) |
| Phone number and contact link | In the same place on every page | 3.2.6 Consistent Help (A, new) |
| Client portal login | No memory test or puzzle unless there’s help, such as a password manager or paste | 3.3.8 (AA, new) |
| PDFs: brochures, warranties, price guides | Tagged, readable PDFs, or the same content as a web page | Same criteria as the page |
Sources: WCAG 2.2 and What’s New in WCAG 2.2. Of the nine criteria new in 2.2, six are Level A or AA, and all six appear in the table.
Two notes from practice. A video tour set to music with no narration still carries information: the layout, the finishes. Describe it in text beside the video. And an automated checker is a start, not a finish. WebAIM’s own report says “not all conformance failures can be automatically detected”. A person still has to tab through the quote form.
An accessibility statement
An accessibility statement is a short page that says what you aim for and how to reach you if something doesn’t work. W3C’s guidance says it should include at least your commitment, the standard you follow and contact details. It also suggests listing known limitations and the date of your last review (W3C WAI). W3C publishes a free generator.
A plain version for a remodeler:
- [Firm name] aims to meet WCAG 2.2 Level AA on this site.
- Last reviewed: [month, year], by [who], with [keyboard, screen reader, automated checker].
- Known gaps: [for example, older project PDFs, being replaced with web pages].
- If something doesn’t work for you, call [number] or email [address]. A person replies within [one working day], and can take your project details by phone.
A statement doesn’t fix a barrier. It gives a visitor another way to reach you, and it shows the work is ongoing. Keep it true: don’t claim full conformance you haven’t tested.
A 12-point checklist
- Every project photo has alt text that names the room, the work and the materials.
- Body text meets 4.5:1 contrast, including text laid over photos.
- Every page works with the Tab, Enter and Escape keys alone, with a visible focus ring.
- The gallery lightbox opens, pages and closes by keyboard, and focus returns to the photo you opened.
- The before-and-after slider has buttons or keys as well as dragging.
- Each quote form field has a visible label, and errors say what is wrong in words.
- Any slideshow or moving banner has a pause control.
- Videos have captions; music-only tours have a text description.
- PDFs are tagged, or the content also exists as a web page.
- Buttons and arrows are at least 24 by 24 CSS pixels on a phone.
- No overlay widget; fixes are made in the code.
- An accessibility statement with a phone number, an email and a review date.
When you hire someone to build or rebuild your site, ask for WCAG 2.2 AA in the contract. Ask how they test: keyboard, screen reader, automated tools. Ask for the test notes at handover. If you’re comparing a site builder with a custom build, Squarespace vs a custom website covers what each lets you control. What a remodeling website costs in the US covers the budget. For what a remodeler’s site needs beyond accessibility, see websites for remodelers.
Sources
- 01Guidance on Web Accessibility and the ADA (opens in a new tab)
ADA.gov (US Department of Justice)18 March 2022ada.gov
- 02Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments (with the 20 Apr 2026 date extension) (opens in a new tab)
ADA.gov (US Department of Justice)8 April 2024ada.gov
- 03Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025 (opens in a new tab)
Seyfarth Shaw, ADA Title III blog25 March 2026adatitleiii.com
- 042025 Year-End Digital Accessibility Lawsuit Report (plain text; data to 15 Dec 2025) (opens in a new tab)
UsableNet21 November 2026info.usablenet.com
- 052026 Midyear Report on digital accessibility lawsuits (plain text; data to 14 Jun 2026) (opens in a new tab)
UsableNet21 November 2026info.usablenet.com
- 062024 digital accessibility lawsuit report released: insights for 2025 (opens in a new tab)
UsableNet3 January 2025blog.usablenet.com
- 07Civil Code § 51 (Unruh Civil Rights Act), as amended effective 1 Jan 2025 (opens in a new tab)
California Legislative Information21 November 2026leginfo.legislature.ca.gov
- 08Civil Code § 52 (opens in a new tab)
California Legislative Information21 November 2026leginfo.legislature.ca.gov
- 09FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines (opens in a new tab)
Federal Trade Commission3 January 2025ftc.gov
- 10FTC Approves Final Order Requiring accessiBe to pay $1 Million (opens in a new tab)
Federal Trade Commission22 April 2025ftc.gov
- 11Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation (opens in a new tab)
W3C12 December 2024w3.org
- 12What's New in WCAG 2.2 (opens in a new tab)
W3C WAI5 October 2023w3.org
- 13The WebAIM Million: the 2026 report on the accessibility of the top 1,000,000 home pages (opens in a new tab)
WebAIMFebruary 2026webaim.org
- 14Developing an Accessibility Statement (opens in a new tab)
W3C WAI11 March 2021w3.org