An ADA website settlement is an agreement that ends an accessibility claim, usually in exchange for a commitment to fix the site to a named standard by named dates. It comes in two forms. A private settlement agreement is a contract between the parties, and the case is then dismissed. A consent decree is the same kind of deal entered by a judge as a court order, so the court keeps jurisdiction and can enforce it. The public examples, such as the Department of Justice's 2014 agreements with H&R Block and Peapod, share a recognizable shape: conform to WCAG 2.0 Level AA by a deadline, appoint an accessibility coordinator, train staff, test on a schedule (automated and with disabled users), report to the other side, and keep doing it for three to five years.
This post walks through how that process works and what the documents actually say, using agreements that are public. I am an engineer, not a lawyer, and nothing here is legal advice. If you are negotiating one, the terms are your lawyer's job. Building what they require is yours.
What is the difference between a settlement agreement and a consent decree?
The difference is who enforces it.
A settlement agreement is a contract. In a private federal case, the parties typically sign it and then file "a stipulation of dismissal signed by all parties who have appeared," which ends the case without a court order (Fed. R. Civ. P. 41(a)(1)(A), Cornell LII). If someone breaks the agreement later, the remedy is a claim for breach or a new lawsuit. DOJ's agreement with Peapod shows the government version: if the United States believes the agreement has been breached, it gives Peapod 30 days to cure and may then file a civil action to enforce the agreement or Title III (U.S. v. Ahold and Peapod, Settlement Agreement, 2014).
A consent decree is signed by the judge. The H&R Block decree was entered on March 25, 2014 in the U.S. District Court for the District of Massachusetts, in a case brought by the National Federation of the Blind and joined by the United States as plaintiff-intervenor. Any change to its terms needs the court's approval (NFB and U.S. v. HRB Digital LLC, Consent Decree). A missed deadline under a decree is a problem you explain to the court that ordered it, not just to the other party.
Most private website cases never produce either document publicly. Robles v. Domino's, the case that reached the Ninth Circuit and drew a Supreme Court cert denial, ended in June 2022 with a notice of settlement after six years of litigation. As Seyfarth's Minh Vu wrote, "We do not know, and may never know, the terms of that resolution" (Seyfarth ADA Title III blog, June 2022). That is why the public DOJ documents are the best template we have.
How does an ADA website case get to a settlement?
The usual path looks like this, though your lawyer may see a different one:
- A claim arrives. Often a demand letter, sometimes a complaint filed in court without warning. Federal Title III has no notice requirement before a suit.
- Both sides assess the barriers. The plaintiff's side has its list. You need your own, page by page, with evidence of what is real and what is already fixed.
- Negotiation. Mostly about three things: the standard, the deadlines, and fees.
- Signature and closure. For a private agreement, a stipulated dismissal. For a decree, the judge reviews and enters it.
- The compliance period. The years of reporting and testing that follow, which is where the real cost lives.
Class actions add a step. Under Rule 23(e), a certified class's claims "may be settled, voluntarily dismissed, or compromised only with the court's approval," and the judge may approve only after a hearing and a finding that the deal is "fair, reasonable, and adequate" (Fed. R. Civ. P. 23(e), Cornell LII). The 2008 Target settlement went that route. Target set up a $6 million fund for members of the California settlement class, and the National Federation of the Blind would test Target.com over a three-year relationship and certify it once agreed improvements were finished in early 2009 (Disability Rights Advocates, August 27, 2008).
What does an ADA website settlement actually require?
Here are the two public DOJ documents side by side. Both are from 2014, so the WCAG version is older than what you would see today, but the structure has held up.
| Term | H&R Block consent decree | Peapod settlement agreement |
|---|---|---|
| Standard | WCAG 2.0 Level A and AA | WCAG 2.0 Level AA |
| Deadlines | Website and online tax product by Jan 1, 2015; mobile apps by Jan 1, 2016 | Mobile apps by Mar 31, 2015; website by Sep 30, 2015 |
| Coordinator | Designated by June 15, 2014, reporting to the CIO | Designated within 90 days, reporting to a Peapod executive |
| Training | By Aug 15, 2014, then at least yearly | At least yearly, first by Mar 31, 2015 |
| Automated testing | Website at least every three months | At least every six months |
| User testing | At least yearly, with blind, deaf and dexterity-impaired testers | At least yearly, with users with disabilities |
| Independent review | Annual consultant evaluation | Annual consultant evaluation |
| Reports | Every six months to plaintiffs and DOJ | Every twelve months to DOJ |
| Term | Five years | Three years |
Sources: H&R Block decree, Peapod agreement.
A few details are worth reading closely.
Third-party content gets its own clause. H&R Block's office-map plug-in got a later deadline of three years after the effective date. Peapod had to seek commitments from vendors that their content conforms or can be made to conform. If your checkout runs on a vendor's payment iframe, expect this conversation. The EU version of the same question is in third-party content under the EAA.
Testing goes beyond scanning. Both documents require automated testing and testing by people with disabilities. H&R Block also had to share automated test results within 10 business days of each test.
Admissions are usually absent. Peapod's agreement says the company denies violating Title III and does not admit wrongdoing (Peapod agreement). Read your own document on this point; don't assume.
If you were drafting today, the standard would likely be newer. DOJ's 2024 Title II rule for state and local governments names WCAG 2.1 Level AA (ADA.gov). That rule doesn't govern private businesses, but it is the most recent federal choice of standard, which makes it a natural reference point in a negotiation. See WCAG 2.1 vs 2.2 for what changes between versions.
Does an ADA website settlement involve money?
Usually some, but federal law limits what a private plaintiff can get. Under Title III, a private plaintiff's remedy is "preventive relief, including an application for a permanent or temporary injunction" (42 U.S.C. § 2000a-3(a), Cornell LII), plus a possible award of "a reasonable attorney's fee, including litigation expenses, and costs" to the prevailing party (42 U.S.C. § 12205, Cornell LII).
Damages and civil penalties enter when the government is a party or state law applies. In the H&R Block decree, the company paid $22,500 to each of two named individuals and a $55,000 civil penalty to the United States (H&R Block decree). Those were available because DOJ was in the case. State statutes such as California's Unruh Act add statutory damages of their own; I covered that in the demand letter guide.
How long does a settlement last, and what happens during it?
The two public examples ran three and five years. During that time the coordinator's reports are the heartbeat of the agreement. H&R Block's coordinator reported at least quarterly inside the company, and compliance reports went to the plaintiffs and DOJ every six months. Disputes had a notice-and-cure step first: written notice, 30 days to respond, good-faith negotiation before anyone went back to court (H&R Block decree).
In engineering terms, a decree turns accessibility into a recurring deliverable with an external reader. Every report needs evidence: what was tested, when, against which criteria, what failed, what was fixed. If that evidence lives in someone's inbox, the reporting period becomes a scramble. See what accessibility evidence to keep.
What can engineering teams do to be ready for these terms?
My opinion, stated plainly: read a consent decree as a process spec and build it before anyone asks you to. Every item in that table is something a competent team could run voluntarily. A named owner. A standard. Training. A testing cadence. A report. The settlement doesn't invent the work; it puts a court date next to it.
Concretely:
- Pick the standard and write it down. WCAG 2.1 AA is the defensible default today; the WCAG checklist lists the criteria.
- Automate the recurring test. A quarterly automated test of named pages is the easiest clause to meet. Scheduled scans cover it, with the failing selector, such as
button.cart-removewith no accessible name, for each finding. - Don't confuse that with conformance. Automated testing catches roughly 30 to 57% of issues; Deque's own rule analysis landed at 57% (Deque). Our scanner won't tell you whether a screen reader user can finish your tax return. The user-testing clause exists for that reason, and it needs people.
- Publish an accessibility statement with a way to report problems. It documents your effort. It is not a guarantee, and it should not read like one.
If you are in the public sector, the ADA Title II guide covers the rule-based deadlines, which work differently from a settlement. The ADA pillar page has the broader picture, and Section 508 covers federal agencies.
FAQ
Is a consent decree an admission that the ADA was violated?
Not necessarily. Whether a document admits liability depends on its text. The Peapod settlement agreement explicitly says the company denies violating Title III and does not admit wrongdoing. Read the specific clause in yours with your lawyer.
What WCAG version do ADA website settlements use?
The public 2014 DOJ documents used WCAG 2.0 Level AA. DOJ's more recent 2024 Title II rule for public entities uses WCAG 2.1 Level AA. The version is a negotiated term, so check your own document.
How long does an ADA website consent decree last?
The H&R Block consent decree ran five years from entry, and the Peapod settlement agreement ran three years. Term length is a negotiated term, so read yours.
Does a court have to approve an ADA website settlement?
Only in some cases. A consent decree is entered by a judge, and a class action settlement needs court approval under Rule 23(e). An individual private case can usually end with a stipulation of dismissal signed by the parties, with no court review of the terms.
Can an automated scanner satisfy the testing terms of a settlement?
It can cover the automated testing clause, not the whole agreement. Both public DOJ documents also require annual testing by people with disabilities and an independent evaluation. Automated tools find a portion of issues; the rest needs manual review.
See where your site stands before anyone asks
Every settlement starts with a list of barriers. You can build yours first. Run a free accessibility scan of your checkout, signup and contact pages and you get the machine-checkable findings with the selector for each one. Then put a keyboard and a screen reader on the same flows for the part a scanner can't see.
Written by Pavel Charkasau, founder of wcagc.com. I am an engineer, not a lawyer, and this post is not legal advice. I read the public decrees because they are the most honest spec of what "ongoing accessibility" means in practice.
Last updated: November 11, 2026
Sources
- ADA.gov archive, Consent Decree, National Federation of the Blind and United States v. HRB Digital LLC and HRB Tax Group, Inc., No. 1:13-cv-10799-GAO (D. Mass., March 25, 2014) (accessed November 11, 2026).
- ADA.gov archive, Settlement Agreement between the United States, Ahold U.S.A., Inc. and Peapod, LLC (November 2014) (accessed November 11, 2026).
- ADA.gov, Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments (accessed November 11, 2026).
- Cornell Legal Information Institute, Federal Rule of Civil Procedure 23 and Rule 41 (accessed November 11, 2026).
- Cornell Legal Information Institute, 42 U.S.C. § 2000a-3 and 42 U.S.C. § 12205 (accessed November 11, 2026).
- Disability Rights Advocates, National Federation of the Blind and Target Agree to Class Action Settlement (August 27, 2008; accessed November 11, 2026).
- Seyfarth Shaw, Minh N. Vu, Robles v. Domino's Settles After Six Years of Litigation (June 2022; accessed November 11, 2026).
- Deque Systems, Automated Testing Study Identifies 57 Percent of Digital Accessibility Issues (accessed November 11, 2026).