Accessibility Is a Lawsuit: ADA Website Compliance 2026 — Mantlr

DOJ extended the Title II deadline by a year on April 20, 2026. The lawsuits haven't paused. What's actually happening in accessibility litigation — and what designers need to know.

Four days before this post was written, on April 20, 2026, the Department of Justice published an Interim Final Rule in the Federal Register extending ADA Title II web accessibility compliance deadlines by one year — from April 24, 2026 to April 26, 2027 for large public entities, and April 26, 2028 for smaller ones. The extension is real. The private-sector ADA lawsuits aimed at businesses are not pausing. Accessibility lawsuit activity is continuing to grow — Seyfarth Shaw tracked 3,117 federal website accessibility lawsuits in 2025, up from 2,452 in 2024. UsableNet's count, which includes state court filings, reached over 5,000 in 2025. The FTC has taken enforcement action against overlay vendors. Web developers are now being named in complaints as potentially liable parties.

If you're a designer, product manager, or founder reading this thinking "we'll deal with accessibility later" — the "later" compliance deadline moved a year, but the real legal risk never waited for the DOJ deadline. This post is the honest state of ADA accessibility litigation in 2026, the specific facts you need to know, and the design decisions that prevent most lawsuit-worthy issues.

This is not legal advice. If you're dealing with an actual accessibility complaint or demand letter, consult a qualified attorney. This post is educational context for designers and product teams.

TL;DR — Key Takeaways

DOJ extended Title II deadlines on April 20, 2026. Large public entities now have until April 26, 2027. Smaller entities until April 26, 2028. The extension is via Interim Final Rule (FR Doc. 2026-07663) with a comment period through June 22, 2026.
The extension applies to public entities, not private businesses. Private businesses remain subject to ADA Title III and ongoing litigation. Existing ADA obligations continue regardless of the Title II extension.
HHS Section 504 May 11, 2026 deadline was NOT extended. Healthcare organizations still face a compressed timeline.
Private-sector lawsuit volume is still growing. Seyfarth Shaw: 3,117 federal website accessibility lawsuits in 2025 (+27% year over year). UsableNet: over 5,000 including state filings. Approximately 75% of filings come from California, Florida, and New York combined.
Pro se (self-represented) filings are surging, reportedly AI-assisted. Seyfarth tracked a 40% year-over-year increase in pro se filings in 2025.
The FTC settled with accessiBe for $1 million (final order April 22, 2025) over deceptive claims about overlay widgets making sites WCAG-compliant.
Fashion Nova settled a California class action for $5.15 million in late 2025 — the DOJ filed a Statement of Interest opposing the settlement in February 2026.
Most lawsuit-triggering issues are basic: missing alt text, unlabeled forms, keyboard traps, color-contrast failures, missing focus indicators. Designers can prevent ~80% of these at the design stage.

What Just Changed: The April 20, 2026 DOJ Interim Final Rule

On April 20, 2026, the Department of Justice published an Interim Final Rule in the Federal Register (FR Doc. 2026-07663) extending compliance dates for the 2024 Title II web accessibility rule.

What the rule does:

Public entities with populations of 50,000 or more: original deadline April 24, 2026 → new deadline April 26, 2027
Smaller public entities (populations under 50,000) and special district governments: original deadline April 26, 2027 → new deadline April 26, 2028
Technical standard unchanged: WCAG 2.1 Level AA remains the required standard
Comment period runs through June 22, 2026

What the rule does not do:

It does not apply to private businesses. Private-sector sites remain subject to ADA Title III and the ongoing case law.
It does not pause active lawsuits. Existing complaints continue.
It does not change HHS Section 504 (healthcare) requirements. The May 11, 2026 HHS deadline remains in effect.
It does not withdraw the Title II rule. The rule still exists; only the compliance date moved.

Public response. The American Association of People with Disabilities (AAPD) and the American Council of the Blind (ACB) have publicly opposed the extension. The DOJ's own statement accompanying the rule says the agency "fully anticipates implementing the regulation at the new deadline." The rule could in theory be withdrawn during the comment period, but most legal analysts expect it to stand.

What to do if you're a public entity. Keep remediating. A year of extra time is real, but WCAG 2.1 AA conformance for a large public-entity site is typically a 12-18 month project. Slowing down now means missing the new deadline too.

What to do if you're a private business. Your deadline never existed in the first place — ADA Title III liability is immediate and based on whether your site is accessible, not whether you've hit an administrative compliance date. See the next section.

The Private-Sector Landscape: The Lawsuits Keep Coming

For private businesses, the legally relevant fact is not the DOJ Title II deadline (which didn't apply to you anyway). It's that ADA Title III lawsuits targeting private-sector websites are continuing to grow.

2025 filing numbers, cross-referenced.

Seyfarth Shaw, the primary legal-industry tracker, reports 3,117 federal website accessibility lawsuits in 2025, up from 2,452 in 2024 — a 27% year-over-year increase. Total ADA Title III federal filings (all types, not just website) reached 8,667 in 2025.

UsableNet, which tracks both federal and state cases, reported over 5,000 digital accessibility lawsuits in 2025 (up from about 4,187 in 2024). The UsableNet count is higher because it includes state court filings, especially California Unruh Act cases.

When you see "4,600+ lawsuits in 2024" or "5,100+ in 2025" cited in accessibility articles, those numbers are UsableNet's combined federal-plus-state counts. The Seyfarth number (federal only, website-specific) is more conservative. Both are growing.

Geographic concentration. California, Florida, and New York combined account for approximately 75% of all federal website accessibility lawsuits. Illinois is now the rising fourth state — 659 filings in 2025, up 65% year over year.

Target industries. Ecommerce sites remain the dominant target — estimates range from 69% (UsableNet 2025) to 77% (earlier years). Food service, hospitality, and retail are the next most-targeted. B2B SaaS is targeted less frequently but not zero.

The pro se surge. Seyfarth's October 2025 post reported a 40% year-over-year increase in pro se (self-represented plaintiff) filings. The widely-cited theory is that AI tools — ChatGPT, Claude, Copilot — now let individuals draft passable complaints without legal representation. Pro se litigants aren't bound by the professional ethics rules attorneys are, which has produced some quality issues (fabricated case citations, fast-filed frivolous motions), but also a higher overall volume.

Major 2025-2026 Cases and Enforcement Actions

Several specific cases shape the 2026 legal environment.

FTC vs accessiBe (final order April 22, 2025)

The Federal Trade Commission finalized a $1 million settlement with accessiBe, an accessibility overlay widget vendor, over deceptive claims that the product could make websites WCAG-compliant. The Commission voted 5-0. The order bars the company from making overlay compliance claims without evidence. FTC press release.

The practical takeaway: accessibility overlays and widgets are not a legal defense. They don't fix underlying code issues, and in some cases may increase lawsuit risk by signaling bad-faith compliance effort. If you have an overlay installed, replace it with real source-code remediation.

Fashion Nova Class Action ($5.15M settlement, late 2025)

A California class action against Fashion Nova alleging website accessibility violations settled for $5.15 million. Notably, the Department of Justice filed a Statement of Interest in February 2026 opposing aspects of the settlement — signaling DOJ scrutiny of serial-plaintiff class actions and the standards they're setting. Coverage via Lainey Feingold's law office.

The practical takeaway: class actions are a growing risk category, not just individual demand letters. Settlements at this scale change the economics of accessibility compliance.

Bashin v. Conduent — Web Developer Liability

The Bashin case (approximately $2M settlement) is notable because it held that web developers, not just the site owner, can be named as potentially liable parties in ADA complaints. Previously, lawsuits almost always targeted the site owner only. Naming developers expands who can be pulled into accessibility litigation.

The practical takeaway for design and development agencies: your contracts need to address who's responsible for accessibility. Be explicit about what level of WCAG conformance you're delivering, what's out of scope, and how liability is allocated if an issue later results in a complaint.

The overlay-vendor enforcement trend

Beyond accessiBe, other overlay vendors — UserWay, AudioEye, and similar products — are under increased scrutiny. California courts have been particularly aggressive in rejecting overlay-based compliance defenses.

What Designers Can Actually Prevent

Most lawsuit-triggering issues fall into a short list of categories that designers control. Getting these right prevents the majority of complaints.

Color contrast

Insufficient contrast between text and background is one of the most commonly cited issues. WCAG 2.1 AA requires 4.5:1 contrast for normal text, 3:1 for large text (24px+, or 18.66px+ bold). WCAG 2.2 keeps the same thresholds but adds non-text contrast requirements (3:1 for UI components and graphics).

Practical: test every color combination in your design system with WCAG contrast math (and APCA as a forward-looking check). Don't ship gray-on-gray at 3:1 for body text. Tools: WebAIM Contrast Checker, Stark, APCA Contrast Calculator.

Connects to Color Systems That Scale — automated contrast testing in CI is the only way to maintain this at 50+ components.

Alt text and image descriptions

Every meaningful image needs alt text. Decorative images need alt="" to mark them as decorative. Missing alt text is one of the single most cited violations in complaints.

Practical: no image component should ship without an alt prop. Design handoff should specify alt text per image. In AI-generated images, the alt text should describe the specific image, not generic placeholder text.

Keyboard navigation and focus indicators

Every interactive element must be reachable by keyboard (Tab to navigate, Enter/Space to activate). Focus must be visible — a custom focus ring that's designed, not the browser default removed with outline: none and nothing in its place.

Practical: design focus states explicitly. Include them in your design system. Never remove focus indication without replacing it. Test every interactive flow keyboard-only.

Connects to The Premium UI Post — well-designed focus rings are also a premium-UI signal, not just accessibility.

Form labels and error messaging

Every form input needs a programmatic label (an associated <label> or aria-label). Error messages must be connected to the input via aria-describedby. Required fields must be marked both visually and programmatically.

Practical: no input should ship without a label. Placeholder text is not a label. Error states should announce to screen readers, not just turn red.

Heading hierarchy

Pages should have a logical heading structure (h1, h2, h3) that screen reader users can navigate. Skipping levels (h1 directly to h4) breaks this navigation.

Practical: one h1 per page, then nested h2s and h3s logically. Design treatments (a big bold word at the top of a section) should use the right semantic heading level, not a styled div.

Touch targets

WCAG 2.2 added Success Criterion 2.5.8: minimum target size 24×24 CSS pixels (at AA). Earlier guidance recommended 44×44. Targets below this size are accessibility failures and, separately, are frustrating for anyone using touch.

Video captions and transcripts

Video content needs captions. Auto-generated captions aren't sufficient if inaccurate. Audio content needs transcripts. Live video needs live captions.

Animation and motion

Animations that auto-play or flash can trigger seizures in users with photosensitive epilepsy. WCAG requires respecting prefers-reduced-motion system preference. Motion that's decorative should be suppressible.

Practical: test with prefers-reduced-motion enabled. Any animation longer than a few seconds should be pausable. Nothing should flash more than three times per second.

These categories — contrast, alt text, keyboard, labels, headings, touch targets, captions, motion — cover most complaints. Designers controlling these prevent most legal exposure before engineering ever touches the code.

WCAG 2.1 AA vs WCAG 2.2 AA — What to Target

Quick clarity on the standard.

WCAG 2.1 AA (published June 2018) is the de facto standard referenced in most US litigation and in the DOJ Title II rule. Courts apply it as the benchmark in ADA complaints.

WCAG 2.2 AA (published October 5, 2023) is the current W3C recommendation. It adds 9 new success criteria to 2.1, covering focus indication, target sizes, cognitive accessibility, and other improvements. It's backwards-compatible with 2.1 — meeting 2.2 means meeting 2.1 automatically.

What to target in 2026. For new work, target WCAG 2.2 AA. You'll meet 2.1 automatically and be positioned for future updates. For remediation, 2.1 AA is the minimum defensible position.

WCAG 3.0. In draft. Candidate recommendation is targeted for Q4 2027. Not worth optimizing against yet. Structured very differently from 2.x (including APCA-based contrast math).

The European Accessibility Act

Outside the US, the European Accessibility Act (EAA) entered enforcement in June 2025, with country-level deadlines throughout 2025-2026. France took enforcement action against four grocery retailers in November 2025. Netherlands had an ACM reporting deadline in October 2025. If your company sells into the EU, EAA compliance is a separate obligation from US ADA compliance.

What to Do If You Receive a Demand Letter

Brief, non-legal overview of the standard response pattern. Consult a qualified attorney for your specific situation.

1. Don't ignore it. Demand letters typically have 30-60 day response windows. Ignoring them accelerates escalation.

2. Forward to an employment or ADA-experienced attorney immediately. The letter itself will usually name the alleged violations and demand remediation plus monetary settlement.

3. Preserve documentation. Screenshots of your site, any accessibility testing you've done, vendor invoices, overlay widget installation records. These matter later.

4. Don't make rushed, undocumented changes. Panic-editing your site in the first 72 hours without documentation can hurt your position.

5. Get an independent accessibility audit. Not from your current vendor; from an independent accessibility consultant. This gives you an objective picture of actual compliance status.

6. Evaluate remediation plus settlement. Most cases settle. Settlements typically include monetary payment to the plaintiff, remediation commitment to WCAG 2.1 or 2.2 AA within 90-180 days, and ongoing monitoring.

Cost estimates: demand-letter response and settlement typically $3,000-$15,000. Active litigation runs much higher. Proactive compliance typically costs $5,000-$30,000 for most mid-sized sites, which is usually cheaper than reactive compliance after a lawsuit.

The Broader Framing

Accessibility is not primarily a legal topic. It's a design and engineering topic that has serious legal consequences when done poorly. The designers and teams who take accessibility seriously as a quality practice aren't defensively hedging against lawsuits — they're shipping products that serve more users, rank better in search, work better with voice interfaces and assistive tech, and scale more reliably. The lawsuits are the floor for what bad accessibility costs. The ceiling for what good accessibility creates is much higher.

The April 20 DOJ Title II extension gives some public entities a year of breathing room. It gives private-sector designers and teams exactly nothing — the lawsuits, settlements, and enforcement actions continue. Design accordingly.

Frequently Asked Questions

Do I need to make my website WCAG 2.2 AA compliant?

For private businesses operating in the US, there's no federal regulation naming a specific WCAG version. But courts consistently apply WCAG 2.1 AA as the benchmark in ADA Title III lawsuits. Targeting WCAG 2.2 AA gives you the current W3C-recommended standard and is backwards-compatible with 2.1. For US state and local government entities, the DOJ Title II rule (as amended April 20, 2026) requires WCAG 2.1 Level AA conformance by April 2027 or April 2028 depending on entity size.

What did DOJ change on April 20, 2026?

The DOJ published an Interim Final Rule extending ADA Title II compliance deadlines for state and local government websites and mobile apps. Large public entities now have until April 26, 2027; smaller entities until April 26, 2028. The technical standard (WCAG 2.1 Level AA) is unchanged. The rule does not apply to private businesses. HHS Section 504 deadlines for healthcare are not affected by this extension.

Are accessibility overlays (widgets) enough?

No. The FTC finalized a $1 million settlement with accessiBe on April 22, 2025 over deceptive claims that overlay widgets make sites WCAG-compliant. Overlays don't fix underlying code accessibility issues. Courts — especially in California — have increasingly rejected overlay-based compliance defenses. In some cases, having an overlay installed may increase lawsuit risk by signaling bad-faith remediation.

How many accessibility lawsuits are filed per year?

In 2025, Seyfarth Shaw tracked 3,117 federal website accessibility lawsuits (up from 2,452 in 2024). UsableNet, which includes state court filings, tracked over 5,000 digital accessibility lawsuits in 2025. California, Florida, and New York account for roughly 75% of federal filings. Pro se (self-represented) filings grew approximately 40% year over year in 2025.

What industries get sued most for accessibility?

Ecommerce sites remain the dominant target, with estimates ranging from 69-77% of filings. Food service, hospitality, retail, and travel are next most-targeted. B2B SaaS is targeted less frequently but is not immune. Healthcare is a growing category especially given the HHS Section 504 deadline.

What's the difference between ADA, WCAG, and Section 508?

The ADA (Americans with Disabilities Act) is US civil rights law that's been applied by courts to websites of businesses open to the public. WCAG (Web Content Accessibility Guidelines) is the technical standard developed by W3C that courts use as the benchmark for ADA compliance. Section 508 is a separate federal law requiring US federal agencies (and federal contractors) to make IT accessible — it references WCAG as its technical basis. Section 504 of the Rehabilitation Act is a related statute; HHS has applied it to healthcare providers receiving federal funds, with a May 11, 2026 deadline.

Can web developers or design agencies be sued for accessibility issues?

Yes. The Bashin v. Conduent case expanded the pool of potentially liable parties to include web developers, not just the site owner. Design and development agencies should address accessibility explicitly in their contracts — what level of WCAG conformance is being delivered, what's out of scope, and how liability is allocated if an issue later results in a complaint.

Where can I learn more?

The most authoritative free resources are the W3C WAI site, WebAIM, Adrian Roselli's blog for technical depth, and Lainey Feingold's blog for legal analysis. For lawsuit tracking and statistics, Seyfarth Shaw's ADA Title III blog is the industry standard.

For related topics, read [Color Systems That Scale](https://mantlr.com/blog/color-systems-that-scale) (automated contrast testing at the system level) and [Dark Mode Is Harder Than You Think](https://mantlr.com/blog/dark-mode-harder) (dark-mode accessibility specifically).

For the broader design-craft context that produces accessible interfaces by default, see [How Stripe, Linear, and Vercel Ship Premium UI](https://mantlr.com/blog/stripe-linear-vercel-premium-ui) and [Microinteractions That Convert](https://mantlr.com/blog/microinteractions-convert).

Browse Mantlr's curated [accessibility tools](https://mantlr.com/categories), [contrast checkers](https://mantlr.com/categories), and [WCAG resources](https://mantlr.com/categories) to build your accessibility toolkit.

External references:

Legal disclaimer: This post is educational content for designers, product managers, and founders. It is not legal advice. Statistics and case information are current as of the date of writing (April 24, 2026) and may change. If you are dealing with an actual ADA complaint, demand letter, or lawsuit, consult a qualified attorney licensed in your jurisdiction.

Accessibility Is Not a Feature — It's a Lawsuit