Track and Maintain Progress
How to Document Accessibility Improvements
When accessibility work is going well, documentation feels like overhead. The team knows what was fixed and why. When the work is questioned, by an auditor, a complaint, a customer, or leadership, memory stops being enough. What matters then is the record: what was found, who was responsible, what changed, and how the result was checked.
This article covers how to keep that record. It is about the practical content of good documentation, not about producing a specific document or format.
What to record
A useful accessibility record captures the same basic facts for every issue, and it captures them as the work happens rather than afterwards.
Testing scope. Note what was checked and how: which pages or user journeys, whether the check was an automated scan, a manual review, or an assistive technology test, and when it ran. A finding means little without knowing where it came from.
Findings. Record each issue in enough detail to act on it later: the page, the element, and the problem in plain terms. "The email field on the checkout page has no visible or programmatic label" is useful. "WCAG failure" alone is not.
Assignments. Every open issue should have an owner and a priority. Record who picked it up and when. An unassigned finding is work nobody has committed to.
Changes. When a fix ships, record what actually changed: the code edit, content update, or design revision, not just "fixed." Where possible, keep the supporting material such as screenshots, the corrected page, or a commit reference.
Verification. Record who checked the fix, how they checked it, and what they found. A rescan, a keyboard walkthrough, or a checklist review are all valid methods. The important part is that a check happened and its result is written down.
Dates. Every step above carries a date. Dates are what turn a list of tasks into a history: they show how quickly issues were acknowledged, how long fixes took, and whether attention was sustained.
Unresolved work. The record should also show what is still open, what was deferred, and why. A record that only shows completed work reads as selective. Keeping open issues visible is more credible and more useful.
A simple example record
One finding, recorded end to end, might look like this:
- March 3. Scheduled scan of the checkout page reports a missing form label on the email field (WCAG 2.1 Success Criterion 1.3.1).
- March 4. Finding assigned to Dana K., marked high priority because the field sits on the main purchase path.
- March 6. Dana adds a visible label programmatically associated with the input. Change noted on the finding; screenshot of the corrected field attached.
- March 9. Priya S. verifies the fix: reruns the scan on the page, checks keyboard focus, and confirms a screen reader announces the field's purpose. Result recorded as verified.
- Status. Resolved. If the same field loses its label in a later release, the record shows it happened before and how it was fixed.
Nothing in that record is complicated. Its value comes from being complete and contemporaneous: each step was written down when it happened, by the person who did it.
Reports, scans, and certifications are inputs, not conclusions
Scan reports, audit write-ups, and vendor certificates all contribute to an accessibility record. A scan report documents that a check ran on certain pages and what it detected. An audit captures an expert review at a point in time. These are real and useful inputs.
What none of them does is establish, on its own, that a website is accessible or legally compliant. A scan only covers what it checked and what it can detect. An audit describes the moment it was performed. A certificate describes what a vendor was willing to attest, under its own terms. Each answers a narrower question than "is this site accessible?"
The distinction matters when records are examined by someone who does not assume the best. Presented alone, a report shows that a document exists. Presented alongside findings, assignments, changes, and verifications, the same report becomes part of a factual history. The artifacts contribute to the record. The record is what carries the weight.
Intent and demonstrated action are different things
Organizations under scrutiny often describe sincere effort: the team cared, the work mattered, fixes were planned. That intent is usually genuine. But independent review, whether an internal audit or a legal proceeding, evaluates conduct rather than sentiment. The questions it asks are factual: what did the organization know, when did it know it, what did it do next, and can it show that?
An organization can be entirely sincere and still unable to demonstrate what happened. The people involved may have worked diligently. If assignments, changes, and verifications were never recorded, the institution cannot reconstruct its own response. Sincerity without a record is an assertion.
Whether good faith carries legal weight in a given dispute depends on the law, the forum, and the circumstances, which is a question for counsel. What an organization can control at all times is simpler: whether the work it does is documented in a way it can later stand behind. Recording intent is optional. Recording action is what makes intent visible.
Keep the record honest
A few habits keep a record trustworthy over time:
- Write entries when work happens. Reconstructed timelines lose detail and invite doubt.
- Append, do not rewrite. If a priority changes or a finding is reassigned, record the change rather than editing the past. Corrections to the record should themselves be recorded.
- Record unfavorable facts. A scan that finds new problems, a fix that fails verification, an issue that recurs: these belong in the record alongside the successes. A history with no setbacks is not a credible history.
- Keep it where it will be found. Records scattered across inboxes and chat threads are hard to assemble later and easy to lose when people change roles.
How SiteRecord supports this
SiteRecord is built around this exact record: findings with their page captures, one current owner per finding with an append-only assignment history, recorded corrections with file attachments, verification entries that note who checked, how, and when, and reports that draw directly from that history. The free plan covers one website and includes the full workflow.
A tool cannot record work that was never done, and a record does not guarantee any particular outcome when the work is questioned. What it does is give an accurate account to stand on. Start a free account to keep the record from the next finding onward.
For what automated tools can and cannot detect, see What Accessibility Scans Can and Cannot Tell You. For a step-by-step version of this workflow, see Accessibility Remediation Checklist: Find, Assign, Fix, Verify.