What Is a Defensible Accessibility Record?
Documentation that holds up when examined by someone who assumes you are wrong.
A defensible accessibility record is a structured body of documentation that demonstrates an organization's ongoing effort to identify, track, remediate, and govern web accessibility issues. It is called "defensible" because it gives an examiner; opposing counsel, a regulator, or an auditor; a factual, contemporaneous record to work from.
Unlike a scan report or a compliance certificate, a defensible record shows the process, not just the outcome.
What It Includes
- A complete issue lifecycle for every finding: detection, acknowledgment, assignment, remediation, review, and closure
- Attribution at every step; who did what, and when
- Separation of duties between the person submitting evidence and the person reviewing it
- A durable history that preserves what was recorded and when
- Continuity; evidence of ongoing monitoring, not a one-time project
What It Does Not Include
A defensible record is not a compliance certificate. It is not an accessibility statement. It is not a vendor report asserting that your site "passed."
These are assertions. A defensible record is the underlying evidence that makes assertions credible. Without the record, assertions are unsupported claims.
Why It Matters
Most organizations that do accessibility work have no defensible record of it. The work lives in Jira tickets, email threads, Slack messages, and spreadsheets that no one can reassemble into a coherent narrative under pressure.
When a demand letter arrives or a regulator asks questions, the organization discovers that years of genuine effort left behind nothing a third party will credit. The work happened. The evidence does not exist.
Common Misconceptions
"Our Jira board is our record." Project management tools track tasks. They do not enforce separation of duties or preserve an attributed history of the work. Tickets get edited, reassigned, and deleted. That is not the same thing as a record kept for the purpose.
"We had an audit, so we have documentation." An audit is a snapshot. It tells you what an auditor found on a given date. It does not document what you did next, who was responsible, or whether the same issues recurred. A defensible record includes the response to the audit, not just the audit itself.
"We'll compile the record if we ever need it." Records reconstructed after the fact are easier to challenge. A record is more credible when it was created at the time the work happened, not months or years later when a dispute forced the question.
What This Means in Practice
A defensible record is built incrementally, as a byproduct of doing the work. Each time an issue is found, someone acknowledges it. Each time a fix is made, evidence is submitted. Each time evidence is reviewed, a decision is recorded.
Over time, this produces a body of documentation that answers the hard questions: What was found? Who was responsible? What was done? The distinction between testing and governance is the distinction between detecting problems and building this kind of record.
SiteRecord keeps this record as part of the work: actions attributed, timestamped, and preserved in an append-only history.