Skip to main content
Accessibility.build
All Posts
Legal & Compliance

The DOJ Just Opposed a Website Accessibility Class Settlement

In February 2026 the DOJ filed a Statement of Interest opposing a website accessibility class settlement, signaling scrutiny of quick-cash deals.

AT

The Accessibility.build Team

July 1, 2026·6 min read
Legal & Compliance

In February 2026, the U.S. Department of Justice filed a Statement of Interest opposing a proposed settlement of a federal class-action lawsuit over a national retailer’s inaccessible website. That is an unusual posture: the government intervened not against a defendant, but against a deal the plaintiffs themselves had agreed to. The DOJ argued the settlement would not meaningfully improve access for people with disabilities, over-compensated the plaintiffs’ attorneys, and — pointedly — ran through a claims website that was itself inaccessible to blind users. The move is a caution to plaintiffs and defendants alike that a signed settlement is not automatically the end of the story.

What happened

The underlying case was a federal class action alleging that the defendant retailer’s website was not accessible to people with vision disabilities, in violation of the Americans with Disabilities Act. The parties negotiated a proposed class settlement and brought it to the court for approval. Before the court signed off, the Department of Justice filed a Statement of Interest — a formal filing in which the government shares its view on a legal matter it is not a party to — urging the court to reject the deal as structured.

That is what makes this notable. Statements of Interest in web accessibility cases usually push back on defendants. Here, the government trained its scrutiny on a plaintiff-side settlement, effectively asking whether the class members the suit was meant to protect would actually benefit from it.

The DOJ’s three objections

  1. It would not ensure real access. The DOJ argued the proposed settlement would not actually increase access to the website for people with disabilities — the core harm the lawsuit was brought to remedy.
  2. It favored the lawyers. The government objected that the deal disproportionately compensated the plaintiffs’ attorneys relative to the class members with vision disabilities it was supposed to serve.
  3. The claims site was inaccessible. Most strikingly, the DOJ noted that the settlement’s own claims and administration website — the portal class members would use to participate — was itself not accessible to blind users.

Taken together, the objections describe a settlement that, in the government’s telling, paid the people who filed the case while leaving the barrier itself largely in place — and asked blind class members to claim their benefits through a website they could not use.

Why it matters

Web accessibility is the fastest-growing category of ADA litigation, and settlements have proliferated alongside the case volume. Our accessibility lawsuit research tracks that trend. The DOJ’s intervention signals that regulators want these settlements to produce genuine access — not just fee awards — and it puts a spotlight on “quick-cash” deals that resolve a case on paper without fixing the website at issue.

A signed settlement is not automatically the end of the story. A court still has to approve a class settlement, and the government can weigh in on whether it serves the class.

For defendants, the lesson is that resolving a lawsuit and remediating a website are not the same thing. A deal that buys peace but leaves barriers standing can draw regulatory attention and expose you to further complaints. For plaintiffs, it is a reminder that outcomes measured in attorney fees rather than access can invite scrutiny of the settlement itself.

What this means for you

The most reliable way to stay out of this dynamic is to make your digital properties accessible before a demand letter arrives — and, if you do settle, to make sure the remediation is real and the process is usable.

  • Fix the barrier, not just the case. A settlement should include a concrete remediation plan and a standard to meet. An independent accessibility audit establishes where you stand and what “done” looks like.
  • Make the process accessible too. If you administer claims, refunds, or notices online, that portal must be usable by the people the case protects — an inaccessible claims site undercuts the entire settlement.
  • Weigh the true cost. Fees, remediation, and reputational risk add up. Our guide to the cost of an ADA website lawsuit breaks down what organizations typically face.
  • Understand the law. Review the basics of ADA compliance so accessibility is a standing commitment, not a reaction to litigation.

The bottom line

The DOJ’s opposition to this settlement is a signal that the government expects web accessibility cases to deliver what they promise: access. Deals that reward attorneys while leaving barriers in place — or that route class members through inaccessible claims sites — may not survive court approval. The durable answer, for everyone involved, is to make the website work for people with disabilities in the first place.

This article is general information, not legal advice.

Sources

  • ADA Title III Blog (Seyfarth): DOJ Throws Wrench Into Proposed ADA Website Accessibility Class Settlement

Enjoyed this article?

Share it with others who care about accessibility.

Written by

AT

The Accessibility.build Team

The Accessibility.build team publishes practical guides, tools, and research on web accessibility, WCAG compliance, and inclusive design.

Essential Accessibility Resources

Comprehensive tools, checklists, and guides to help you create inclusive digital experiences

Top Pick

WCAG 2.5.7 Dragging Movements Guide

Complete guide to providing a single-pointer alternative to every drag action — accessible patterns for sliders, sortable lists, kanban boards and maps, the two exceptions, code examples, and testing
dragging movements
wcag 2.5.7
drag and drop accessibility
+11 more
View guide
Top Pick

WCAG 1.4.13 Content on Hover or Focus Guide

Complete guide to accessible tooltips and hover menus — the Dismissible, Hoverable, and Persistent conditions, why the title attribute fails, aria-describedby, copy-ready code, and testing
wcag 1.4.13
accessible tooltip
tooltip accessibility
+10 more
View guide
Top Pick

WCAG 1.4.12 Text Spacing Guide

Complete guide to the four text-spacing values users must be able to override — line height 1.5, paragraph spacing 2×, letter spacing 0.12, word spacing 0.16 — the test bookmarklet, why fixed-height containers clip text, CSS fixes, and testing
text spacing
wcag 1.4.12
line height accessibility
+12 more
View guide
accessibility.build© 2026