Skip to main content
Should You Settle or Fix First?Laws and Regulations
4 min readFor CISOs

Should You Settle or Fix First?

When your legal team forwards a digital accessibility demand letter, two urgent questions arise: how do we make this lawsuit go away, and how do we fix the website? Most companies treat these as the same question. They're not.

The tension between legal resolution and technical remediation has intensified with the rise in repeat litigation. According to UsableNet's 2026 Midyear Report, about one-quarter of digital accessibility lawsuits now target companies that have already resolved a previous claim. This pattern suggests that the traditional approach, settle quickly and move on, isn't effective.

The question isn't whether to respond. It's which response should come first.

The Case for Settling the Claim Before Remediating

Legal counsel often advocates for quick settlement, and the reasoning is sound.

A demand letter or complaint creates immediate legal exposure. The company faces potential damages, attorney fees, and discovery costs that can exceed the settlement amount. Delaying a resolution while engineering teams audit the site and implement fixes can extend that exposure for months.

Settlement also provides certainty. Once an agreement is signed and the plaintiff dismisses the case, the company knows the cost and can move forward. Remediation timelines are harder to predict. A team may discover that fixing keyboard navigation across a checkout flow requires refactoring shared components, updating third-party scripts, and coordinating with vendors who control parts of the experience.

Counsel may also argue that starting remediation before settlement can complicate negotiations. If the company acknowledges specific barriers during the legal process, those admissions could strengthen the plaintiff's position or surface in future claims.

For companies with limited resources, settling first allows them to resolve the legal matter without diverting engineering capacity during active litigation. The accessibility work can happen afterward, on a timeline the company controls.

The Case for Fixing the Site Before Settling

Accessibility practitioners and technical leaders often push in the opposite direction: start remediation immediately, even if settlement talks are underway.

Their reasoning starts with the fact that settlement doesn't prevent the next lawsuit. The midyear report found that the 10 most active plaintiff firms account for approximately 84 percent of filings. These firms don't coordinate. A settlement with one plaintiff doesn't bind another.

If the barriers that triggered the first claim remain on the site, the company is simply waiting for the next letter. Fixing the underlying issues, unlabeled form fields, inaccessible modals, keyboard traps in checkout, reduces the likelihood that another plaintiff can make the same allegations.

Remediation also strengthens the legal response. Defense counsel can demonstrate to the court or opposing counsel that identified barriers have been corrected, that the company is actively testing, and that meaningful progress is underway. That evidence may narrow the scope of the claim, reduce settlement demands, or provide grounds for dismissal if the plaintiff's allegations no longer reflect the current experience.

Starting remediation early also prevents the problem from spreading. E-commerce sites change constantly. New product pages, seasonal promotions, updated templates, and third-party integrations can replicate the same accessibility defects across dozens of pages while the legal team negotiates. Waiting to fix the site until after settlement means the company may be remediating a larger problem than the one described in the original complaint.

Finally, remediation sends a signal internally. It tells product, engineering, and content teams that accessibility is an operational priority, not just a legal problem to be managed by outside counsel.

Where Practitioners Actually Land

Most experienced teams don't choose one approach or the other. They run both tracks in parallel.

Legal counsel handles the lawsuit. Accessibility teams handle the website. The two workstreams share information but operate independently.

This approach recognizes that settlement resolves one plaintiff's claim, while remediation addresses the barrier that led to it. Both are necessary. Neither is sufficient alone.

The practical question is how much remediation to complete before settlement closes. Some companies prioritize the specific pages and interactions named in the complaint, ensuring those barriers are corrected before the agreement is signed. Others use the claim as a trigger to audit the entire customer journey and fix systemic issues across templates, components, and third-party tools.

The scope depends on the company's risk tolerance, resources, and litigation history. A first-time defendant may focus narrowly on the alleged barriers. A company facing its third claim in two years may conclude that partial fixes aren't working and commit to broader remediation.

Geography also matters. Approximately 80 percent of digital accessibility lawsuits involve e-commerce companies, and claims are concentrated in New York, California, Florida, and Illinois. Companies selling into those markets should assume they're visible to plaintiff firms and plan accordingly.

Our Take

Settle the lawsuit. Fix the website. Don't confuse the two.

Settlement resolves legal exposure with one plaintiff Assistive Technology a defined cost. It doesn't make your site accessible, and it doesn't prevent the next claim. Remediation addresses the barriers that created the risk in the first place.

The mistake isn't settling too quickly. It's treating settlement as the end of the accessibility work rather than the beginning.

If your team is debating whether to prioritize legal resolution or technical fixes, the answer is both, but with clear ownership. Counsel should manage the claim. Your accessibility lead should manage the remediation. The two efforts should inform each other without blocking each other.

And if your site still has unlabeled buttons, inaccessible checkout flows, or keyboard traps three months after the settlement check clears, you haven't reduced your risk. You've just paid for the privilege of being sued again.

WCAG 2.1 Guidelines

You Might Also Like