ADA compliance documentation is the organized collection of records that shows what your organization has done, is doing, and plans to do regarding digital accessibility. When a demand letter arrives or a complaint is filed, this documentation is your first line of defense. Without it, you’re left arguing intent without evidence.
The right documentation doesn’t prevent lawsuits from being filed, but it directly shapes how they resolve. Judges and plaintiffs’ attorneys assess whether an organization has acted in good faith. Documentation is how you prove that.
| Document Type | Legal Function |
|---|---|
| WCAG Audit Report | Proves you identified accessibility issues through expert evaluation, not guesswork |
| Remediation Records | Shows a timeline of fixes applied, demonstrating ongoing effort |
| Accessibility Policy | Establishes organizational commitment and internal standards |
| Accessibility Statement | Public-facing declaration of conformance goals and contact channel |
| Scan and Monitoring Logs | Provides continuous evidence that issues are being tracked over time |
| Training Records | Demonstrates that staff are equipped to maintain accessibility standards |
Why Documentation Matters in ADA Cases
ADA website lawsuits and demand letters overwhelmingly target organizations that have done nothing. Plaintiffs’ attorneys look for easy targets: no accessibility statement, no audit history, no visible effort.
When documentation exists, it changes the calculus. A complete set of records signals that the organization is aware of its obligations and actively working toward conformance. This directly supports a good faith defense and can accelerate settlement negotiations or lead to case dismissal.
The inverse is equally true. An organization with zero documentation has no way to demonstrate awareness, effort, or timeline. That absence makes it significantly harder to negotiate favorable terms.
What Should a WCAG Audit Report Include?
The audit report is the foundation of your documentation. It identifies accessibility issues against a specific WCAG version and conformance level, typically WCAG 2.1 AA.
A legally useful audit report includes:
- The WCAG version and conformance level tested against
- Pages and components evaluated
- Each issue identified with its WCAG success criterion reference
- Severity or impact classification for each issue
- The date the audit was conducted
- The name of the auditor or organization that performed it
An audit performed by a qualified third party carries more weight than a self-assessment. Automated scans alone are insufficient because they only flag approximately 25% of issues. A thorough audit combines expert evaluation with assistive technology testing.
Accessible.org audit reports, for example, are structured to map directly to WCAG criteria with clear severity ratings. That kind of specificity matters when the report is reviewed during litigation.
Remediation Records: Proving You Acted
The audit identifies issues. Remediation records prove you fixed them. Together, they form the strongest possible evidence of good faith effort.
Effective remediation documentation includes:
- A log of each issue addressed, tied back to the original audit finding
- The date each fix was implemented
- Who performed the fix (internal developer, contractor, or third-party vendor)
- Validation confirming the issue was resolved
The Accessibility Tracker Platform is built specifically for this kind of record-keeping. It maps each audit finding to its remediation status, creating a timestamped trail that functions as compliance evidence. Organizations using the platform can export progress reports at any point, which is exactly the type of documentation attorneys reference in negotiations.
Accessibility Policy vs. Accessibility Statement
These are two distinct documents that serve different audiences.
An accessibility policy is an internal document. It defines your organization’s commitment to accessibility, the standards you follow (WCAG 2.1 AA, for example), who is responsible for maintaining conformance, and how accessibility is incorporated into development and content workflows.
An accessibility statement is public-facing. It appears on your website and communicates your conformance goals, known limitations, and a way for users to report issues. A well-written accessibility statement demonstrates transparency and provides a feedback mechanism that can help resolve complaints before they escalate to legal action.
Both documents are referenced in legal proceedings. The policy shows internal governance. The statement shows public accountability.
Do Automated Scan Logs Count as Documentation?
Yes, but only as a supplement. Scan logs from tools like WAVE, axe, or Lighthouse provide timestamped evidence that your organization is monitoring its digital properties. That ongoing attention has value in demonstrating good faith.
The limitation is that scans only flag approximately 25% of issues. Relying on scan logs alone leaves significant gaps in your documentation. A scan log paired with an expert audit report and remediation records is far more defensible than scan logs in isolation.
Training Records and Internal Communications
If your staff have received accessibility training, document it. Training records show that your organization has invested in building internal capacity to identify and prevent accessibility issues.
Useful training documentation includes:
- Training dates and duration
- Topics covered (WCAG criteria, assistive technology usage, content authoring best practices)
- Attendance records
- The provider or instructor
Internal communications also matter. Emails or project tickets that show accessibility was discussed during design reviews or sprint planning reinforce that accessibility is part of your workflow, not an afterthought.
How Often Should You Update Your Documentation?
Documentation that hasn’t been touched in two years tells a different story than documentation updated quarterly. Freshness matters.
As a baseline:
- Audit reports should be refreshed after any significant redesign, new feature launch, or platform migration
- Remediation logs should be updated as fixes are completed
- Your accessibility statement should reflect your current conformance status
- Scan logs should run at regular intervals, monthly at minimum
Documentation that sits unchanged begins to lose freshness and, with it, legal credibility. The goal is a living record that reflects your current state of accessibility.
Where Should You Store Compliance Documentation?
Scattered documentation across email threads, shared drives, and project management tools is common but problematic. When a demand letter arrives, your attorney needs organized records quickly.
A centralized location is essential. Some organizations use internal wikis or document management systems. Others use a purpose-built tool like Accessibility Tracker, which consolidates audit findings, remediation progress, compliance snapshots, and exportable reports in one place.
Whatever your method, the documentation should be exportable, date-stamped, and organized by document type. If someone outside your organization needs to review it under time pressure, clarity matters more than volume.
Frequently Asked Questions
Can ADA compliance documentation prevent a lawsuit?
It cannot prevent a lawsuit from being filed. Anyone can file. What documentation does is change how the case resolves. Organizations with thorough records are far better positioned to negotiate early dismissal or favorable settlement terms. Plaintiffs’ attorneys prefer cases where no effort has been made.
Is an accessibility statement legally required?
Under the ADA, there is no explicit federal requirement to publish an accessibility statement. However, the ADA Title II web rule references accessibility statements for government entities. For private organizations, publishing one is a best practice that demonstrates good faith and provides a complaint resolution channel.
What WCAG version should my audit reference?
WCAG 2.1 AA is the current standard referenced by the DOJ’s ADA Title II web rule and is widely accepted as the benchmark for ADA conformance. WCAG 2.2 AA is the latest published version and may become the referenced standard in future regulations. Auditing to 2.1 AA is the minimum defensible position today.
How long should I keep old audit reports?
Retain all previous audit reports indefinitely. They establish a timeline of awareness and effort. Even an older report showing issues that have since been fixed demonstrates that your organization identified problems and addressed them. That chronological narrative is exactly what attorneys use to build a good faith argument.
ADA compliance documentation is not a one-time deliverable. It’s an evolving record that reflects your organization’s real commitment to accessibility. The organizations best protected legally are the ones whose documentation tells a clear, honest story of effort over time.
Contact Accessible.org for accessibility audits, remediation support, and compliance documentation services.