What Counts as Proof of ADA Compliance in a Lawsuit

An ADA demand letter doesn’t ask whether your website is accessible today. It asks whether you can prove it’s accessible, and for how long.

That’s the part most businesses get wrong. When the letter shows up, the instinct is to open the site, click through a few pages, and confirm nothing looks broken. But a website that looks accessible right now isn’t the same thing as a website you can prove has been accessible, or that you’ve been actively fixing when it wasn’t. 

Courts don’t grade effort in the abstract. They look for a paper trail: audit findings, a record of what got fixed and when, and proof that the work didn’t stop after one audit. Here’s what actually counts as proof, and why a one-time scan or an installed tool isn’t enough.

What Do Courts Look for in an ADA Accessibility Lawsuit?

The ADA is a strict-liability statute. That means a plaintiff does not have to prove you intended to discriminate, or that you were careless. If your website is not accessible to them, the barrier itself is the violation.

So the question in most of these cases is not “did you mean well?” It’s closer to “what did you actually do, and can you show it?”

Courts and plaintiffs tend to look for evidence of sustained, good-faith effort rather than a single certificate or a one-time scan. In practice, that means being able to answer a few concrete questions:

• What standard were you working toward, and when did you adopt it?

• What testing did you run, how often, and who did it?

• When you found problems, how quickly did you fix them, and can you prove the timeline?

• Do you have a documented, ongoing process, or just a snapshot from one moment in time?

The distinction that matters here is between a claim and a record. Saying your site is accessible is a claim. Dated testing results, fix logs, and a repeatable process are a record. 

This is also why “commercially reasonable steps” comes up. The idea is that you took the kinds of measures a reasonable organization would take to identify and fix barriers, and you can demonstrate it. Effort you can’t document is, for evidentiary purposes, effort that’s hard to prove happened at all.

Does an Accessibility Scan Count as Proof of ADA Compliance?

No. A scan tells you what was true on one page, on one day, run by one tool. That’s useful, but not proof.

Automated scanners only catch a portion of accessibility issues. The rest, things like whether a screen reader can actually complete a checkout or whether focus order makes sense, require human judgment to evaluate. So a clean scan can coexist with real barriers that a user hits the moment they try to do something. 

But the deeper problem is time. A scan is a snapshot. Your site isn’t. New content ships, templates change, a third-party widget updates, and the page that passed last quarter breaks this quarter. A single scan says nothing about the state of your site the day someone actually encountered a barrier, which is the day that matters in a complaint.

What separates the two is simple:

• A scan shows one moment. It answers “Was this page okay when we scanned it?”

• A record shows a pattern of effort over time. It answers, “Do we have an ongoing, documented process for finding and fixing barriers?”

The second shows that you took accessibility seriously, because it has dates attached. Dated testing results, fix tickets showing when an issue was found and when it was closed, a testing cadence you can point to, a standard you committed to, and when. Each of those is an artifact with a timestamp, and timestamps are what turn “we care about accessibility” into something you can actually show.

Open envelope with a letter coming out. 'ADA' is at the top of the letter. An accessibility symbol is to the left of the envelope and the image is set against a green background.

What Documents Prove ADA Compliance in a Lawsuit?

ADA documentation that proves compliance includes Expert Audit reports, a dated fix log, monitoring records, a published accessibility statement, and a VPAT. Each one demonstrates a different part of the record that a court of opposing counsel will want to see.

• Expert audit reports: A documented Expert Audit shows that a qualified team tested your site against a recognized standard, typically WCAG 2.2 Level AA, and identified specific issues by page and severity. This is the baseline: proof someone actually looked, and looked correctly.

• A dated fix log. This is the record of what was found and what was actually corrected, with dates attached. A fix log is what makes the paper trail real: dates, pages, and what got fixed.

• Monitoring records. Ongoing monitoring shows your site was checked continuously, not just once. This is what proves the effort didn’t stop after the first scan. 

• An accessibility statement: A public, dated commitment to a specific standard that also gives users a way to report issues directly to you. On its own, an accessibility statement is weak evidence, but paired with the records above, it shows intent that matches action.

• A VPAT. A Voluntary Product Accessibility Template documents your specific conformance claims against WCAG and Section 508 criteria. A VPAT is not legally required, but it adds a formal, standardized layer to your ADA compliance evidence.

The patterns across all five are the same: each one has a date, each one names a standard, and each one can be produced on request. Individually, they’re useful. Together they tell a continuous story: here’s the standard we committed to, here’s how we tested against it, here’s what we found, here’s when we fixed it, and here’s how we keep checking.

That continuity is the thing a single scan can never provide.

Is an Installed Accessibility Tool Enough to Defend an ADA Lawsuit?

No. Having an accessibility tool installed is not the same as having documented proof of ongoing fixes.

An installed tool tells you a product is present, but doesn’t tell you what issues were found, what was fixed, when, or by whom. No dated audit, no fix log, no monitoring history, none of the artifacts from above. Presence does not equal documentation.

The data bears this out: according to AudioEye’s 2026 Litigation Report, 38.5% of companies facing an ADA lawsuit already had an accessibility solution installed. A tool being present didn’t resolve the high-impact issues a user hit, and presence alone didn’t function as a defense. 

This is the same gap that shows up with standalone tools, like overlays, on a frequent basis. An overlay is designed to be the whole answer on its own. A platform takes a different approach, combining automation and expert testing so experts and assistive technology users verify accessibility rather than assume it. Automation handles the scale, and human experts handle the issues that require judgment. It’s that second half, the human verification, that generates the dated record that actually functions as evidence.

How AudioEye Assurance Helps You Prove ADA Compliance

Knowing what proof looks like is one thing. Producing it, continuously, across a site that keeps changing, is another. That’s the part most teams can’t sustain by hand: the testing cadence, the fix logs, the monitoring that doesn’t lapse the moment things get busy.

This is where AudioEye comes in. AudioEye helps you prove ADA compliance by generating that documented record automatically: monitoring runs continuously, Experts Audits puts human testers on the issues automation can’t judge, and Custom Fixes close them, each step leaving a dated artifact.

With AudioEye Assurance, that record is put to work. If a claim still happens, AudioEye provides legal support and can cover resulting settlements or judgments tied to WCAG violations, backed by the documentation the platform already produced. Our approach has held up under real legal pressure: AudioEye successfully defended Babylon Marine and the case was dismissed with no settlement paid.

Want to see what that kind of protection looks like for you? Talk to an expert today.

Curious how accessible your current site is? Use our free accessibility checker to scan for issues in seconds.