Reviewed November 2, 2026

Remediation Timelines in Accessibility Settlements: What Drives 90 Days vs 12 Months

Remediation deadlines in website accessibility settlements typically run from about 90 days for a bounded set of templates and transaction flows to 12 months or more for large catalogs, heavy third party components, or platform migrations. The number is driven by scope, verification method, and who certifies completion: a deadline tied to an independent audit of the checkout path is a different instrument from a calendar promise covering every archived page. Defendants who propose a timeline built from an actual audit, with milestones, settle better and breach less.

Every settlement negotiation eventually arrives at the same question, how long to fix it, and the parties usually start from numbers with no engineering behind them. Plaintiffs open short. Defendants ask long. The durable settlements are the ones where the timeline came from a scope document instead of from the bargaining, because a deadline divorced from the work produces the two classic outcomes: breach, or a rushed cosmetic pass that fails the verification audit and reopens everything.

Understanding what legitimately drives the number is worth more than the number itself, for both sides of the table.

The scope variables that stretch a timeline

Page count is the least important variable; template count is the real one. A store with ten thousand product pages built on twelve templates can remediate its core barriers faster than a boutique with three hundred pages hand built across forty layouts. The transaction path, browse, product, cart, checkout, account, is where settlements concentrate first, because that is where user harm and most legal exposure live.

Third party components set the floor on any honest schedule. Payment widgets, chat tools, review platforms, cookie banners, and embedded booking engines are outside the defendant's codebase; fixing them means vendor tickets, contract pressure, or replacement, none of which respect a 90 day promise made in a conference room. A timeline that ignores the vendor inventory is fiction, and experienced plaintiff counsel know it, which is why the vendor list belongs in the negotiation, not in the excuses afterward.

Verification: the clause that gives the deadline meaning

Settlements differ most in how completion is proved. At the light end, the defendant certifies conformance itself. In the middle, an independent auditor tests the agreed scope against WCAG 2.1 AA, with assistive technology passes on the transaction path, and issues a report both sides accept. At the heavy end, monitoring periods and periodic reporting follow the business for a year or more, a structure common in consent decrees and structured negotiations with advocacy organizations.

Defendants sometimes resist audit clauses as cost, then discover the audit is their protection: it converts an open ended obligation into a defined finish line, and it produces the documentation that answers the next demand letter. The verification method should be agreed before the deadline, because a timeline is only as real as the test it has to pass.

Building a proposal that survives contact with reality

Sequence the work in the order plaintiffs and courts care about: critical transaction barriers first, global template issues, navigation, forms, media, next, then the long tail of content level fixes. Put dates on phases rather than one cliff edge at the end; phased milestones let the other side see progress and give your own team deadlines small enough to be honest about.

Then add the maintenance term, the one most settlements underweight. Sites regress: a theme update, a new marketing widget, a seasonal landing page built outside the design system. A settlement that fixes the site once and says nothing about keeping it fixed is renting its result. Training, a pre publish accessibility check, and an annual audit are cheap clauses at signing and expensive absences later.

Related reading

Related reading: Multiple Demand Letters From Different Firms: How to Triage the First Two Weeks, What an Accessibility Statement Should and Should Not Promise, and An Accessibility Demand Letter Arrived: The First 30 Days.

Frequently asked questions

What is a typical remediation deadline in a website accessibility settlement?

Ranges cluster between roughly three and twelve months depending on scope, with the transaction path usually due earliest. Small, template driven sites settle toward the short end. Large catalogs, platform work, or heavy third party dependence push toward a year, especially when phased milestones and independent audits are included.

What happens if a business misses its settlement remediation deadline?

Consequences depend on the agreement: extensions negotiated in good faith are common when milestones are being met, while a formal settlement or consent judgment can expose the business to enforcement motions, additional fees, and loss of credibility with the court and opposing counsel. Documented progress is the best protection.

Who verifies that remediation is complete?

It varies by agreement. Options include defendant certification, a mutually accepted independent accessibility auditor, or, in structured negotiations and consent decrees, a monitor with periodic reporting. Independent audit against WCAG 2.1 AA on the agreed scope is the most common middle ground.

Should a settlement cover future pages and redesigns?

Well drafted ones address it, typically by committing the business to maintain conformance and to build new templates and major redesigns to the same standard. Without a maintenance commitment, a redesign a year later can recreate the barriers the settlement just paid to remove.