Back to BlogAccessibility Litigation

Why Businesses Get Sued Again: A Post-Lawsuit Accessibility Review

Why accessibility barriers can persist or return after a lawsuit, and how businesses can review prior fixes, retest and document progress.

14 sections · 5 min read · 1,065 words

Written by Edward Sm

Digital Accessibility Specialist, ADA Access Group LLC

Updated 5 min read

Woman using a laptop and headphones at a home office desk.

A business resolves a website accessibility complaint, fixes reported problems, and moves forward. Months later, another claim arrives. How can that happen?

The answer depends on the parties, the earlier agreement, the new allegations, and applicable law. Technically, an earlier review may have covered only part of a site, and websites change after fixes are made. The practical question is whether customers can use the current site and whether accessibility keeps pace with future releases.

According to UsableNet’s October 2026 tracker, 97 defendants among 431 tracked digital accessibility lawsuits had faced a previous ADA digital accessibility lawsuit. The tracker covers federal courts and state courts in New York and California, including claims involving websites, mobile apps, and video. It is not a complete count of all U.S. filings. The figures do not establish why a particular business was sued again, whether the cases involved the same barriers, or whether allegations were proven.

Can a business face another claim after a settlement?

Hands typing on a laptop beside business documents.
Photo: Mikhail Nilov / Pexels.

It may. An earlier agreement’s effect depends on its terms, the parties, the claims, and applicable law. A later case may involve different allegations or individuals. Qualified counsel should review the actual documents before concluding whether a new claim is barred or likely to succeed.

A settlement and a technical accessibility program address related but distinct questions. Resolving a claim does not automatically verify that every part of a changing site works today. If a new complaint or demand arrives, contact counsel promptly and preserve relevant records under counsel’s guidance. For initial steps, see what to do after receiving an accessibility lawsuit or demand letter.

Why can accessibility barriers remain or return?

The earlier work had a limited scope

An audit or remediation project may have focused on particular pages and issues. Mobile layouts, logged-in areas, different product templates, and interactive states may not have been included. Review the original assessment and tickets before assuming that all customer journeys were tested.

For example, a product page may work with a keyboard until a shopper opens a size selector or cart drawer. Check the whole flow, including the states revealed by a user’s actions.

A new release introduced a regression

A theme update, redesigned menu, promotional popup, or new checkout can introduce a barrier after the previous review. Regression testing checks whether functionality that previously worked still works after changes. A dialog that leaves focus behind it or a selection that is shown visually but not exposed to a screen reader are examples of issues to investigate.

A third-party tool changed

Booking systems, payment tools, store locators, and ordering platforms may come from vendors, but customers experience them as part of one journey. Include critical integrations in the assessment, document reproducible findings, and agree on who will fix and retest them.

Automation did not cover the full experience

Automated checks can flag certain detectable issues, but a clean report cannot establish that someone can understand an error or complete an order with assistive technology. The Department of Justice’s web accessibility guidance recommends combining manual checks with automated tools. Our automated versus manual testing guide explains the difference.

How to review a website after an earlier case

Woman wearing a headset and working on a laptop in an office.
Photo: MART PRODUCTION / Pexels.

Compare the complaint, prior audit scope, remediation tickets, and retest results with the website today. Identify what was fixed, what was deferred, what was not assessed, and what changed after the last review. Select representative templates and complete customer tasks based on the site’s functionality and the advice of counsel.

  • Navigation: menus, search, results, filters, and visible keyboard focus.
  • Selection: item names, prices, availability, labels, and selected states.
  • Transactions: cart, checkout, appointments, payment controls, errors, and confirmation.
  • Interactive states: dialogs, popups, expanded content, dynamic feedback, and focus.
  • Mobile and vendors: relevant mobile flows and essential third-party integrations.

Use keyboard-only checks and representative screen reader and browser combinations appropriate to the audience. Record pages, device and software versions, test dates, interaction states, and reproducible steps. Include people with disabilities in usability testing where possible. Read our screen reader testing guide for more detail.

Keep accurate records of what changed

Businesswoman holding a document during a meeting with a laptop.
Photo: MART PRODUCTION / Pexels.

With counsel’s guidance on preservation, privilege, and applicable obligations, organize the original audit scope, findings, remediation tickets, implementation dates, vendor communications, and retest results. Record unresolved issues and their owners. Keep track of major releases and integration changes.

Records help teams coordinate and help counsel understand what was done. They do not prove compliance or guarantee an outcome. Describe the actual scope and results; do not report testing as complete when it was not performed.

Build accessibility into future releases

Assign an owner, include accessibility acceptance criteria in design and development work, and test shared components before deployment. Check important customer journeys after significant changes and retest fixes using the interaction methods that revealed the issue. Provide a clear way for customers to report barriers and ensure someone monitors the feedback.

The right review schedule depends on the site’s complexity and rate of change. A redesign, new checkout, or replacement of a critical vendor tool is a useful trigger for retesting. Accessibility work should reduce barriers for customers as well as help the business understand its current position.

How a current-state assessment helps

An assessment can compare prior findings with the current site, examine representative customer journeys, and provide reproducible issues for developers. Retesting can verify changes within the agreed scope. Learn what an accessibility audit includes and what affects its cost.

Already made changes after an accessibility complaint? Contact ADA Access Group to discuss a current-state review and retesting of the customer journeys that matter to your business.

Frequently asked questions

Can a company be sued again after an ADA website settlement?

It may be possible. The terms, parties, claims, and applicable law matter. Ask counsel to review the relevant documents.

Does an accessibility widget prevent another lawsuit?

No tool guarantees a business will not face a claim. Test the underlying site with keyboard and assistive technology. Read our article about accessibility widgets and lawsuits.

When should a business retest?

Retest after remediation and assess important journeys after significant changes. Set an ongoing schedule suited to the site and its rate of change.

This article is general information, not legal advice. Allegations are not findings of liability, and no audit guarantees a company will avoid a claim.

Featured photo: Artem Podrez / Pexels.

Article Tags

ADA lawsuitsaccessibility retestingdigital accessibilityremediationscreen reader testing

Need a website accessibility audit?

This article explains the topic. The audit is a manual WCAG 2.2 AA review by default (WCAG 2.1 AA when a contract or regulation requires it) with a prioritized report — not another automated scan.