Accessibility reports should show trends because conformance work happens over time, not in a single moment. A snapshot tells you what was true on one date. A trend tells you whether the team is closing issues faster than new ones appear, where regressions keep happening, and whether the product is moving toward WCAG 2.1 AA or drifting away from it. For any audit program that lasts longer than a quarter, trends carry the meaning. Snapshots carry the timestamp.
| Report Type | What It Shows |
|---|---|
| Snapshot | Issue counts and severity on a single date. Useful as a baseline or audit deliverable. |
| Trend | How issues are opened, closed, and reintroduced across weeks and months. Shows velocity, regression patterns, and remediation progress. |
| Best use | Snapshots anchor the starting point. Trends measure whether the work is paying off. |
The Problem With Snapshot-Only Reporting
An audit report delivered as a static PDF is a snapshot. It captures what the auditor identified on the day the evaluation concluded. That document has real value, especially as the starting reference for remediation.
The problem is what happens next. Developers fix issues. Designers ship new pages. Content teams publish updates. Six weeks later, the snapshot no longer describes the product. It describes the product as it existed before the work started.
Without ongoing reporting, leadership sees the audit, approves a budget, and then waits months for the next evaluation to know whether anything actually improved. That gap is where accessibility programs lose steam.
What Does a Trend-Based Accessibility Report Look Like?
A trend-based report tracks the same set of issues across time. It shows when each one was opened, when it was validated as fixed, and whether similar issues have reappeared on new pages or new releases.
The data points worth tracking: open issues by severity week over week, closed issues by week with validation status, regression count (meaning previously fixed issues that returned), new issues introduced since the last audit cycle, and time to remediation measured per issue or per severity tier.
Each of those numbers is meaningless on a single day. Across twelve weeks, they tell you whether the program is working.
Why Trends Matter for WCAG Conformance
WCAG conformance is not a state you reach and lock in. Products change. Code ships. Content gets added. An interface that conformed to WCAG 2.1 AA in March can have regressions by June if no one is watching for them.
Trend reporting catches drift early. If the same success criterion keeps generating new issues across releases, that points to a training need or a flaw in how a component library was built. A snapshot would just list the issue. A trend identifies the pattern.
This is also where leadership gains confidence. A board or compliance officer reviewing a trend chart can see remediation velocity and project a realistic timeline for full conformance. A snapshot leaves them guessing.
Where Snapshots Still Belong
Snapshots are not obsolete. The initial audit report is, and should be, a snapshot. It establishes the baseline. An ACR is also a snapshot, capturing conformance status at a specific point in time for a specific product version.
The point is not to abandon snapshots. It is to stop treating them as the full picture. A snapshot answers “where are we right now.” A trend answers “are we getting better, and how fast.”
How Trend Reporting Fits Into an Audit Program
The cleanest setup is simple. Conduct a manual accessibility audit to identify issues and establish the baseline. Load those issues into a tracking platform. Update status as remediation happens. Pull trend reports on a regular cadence; monthly works for most teams.
Scans can supplement trend data between audits, though scans only flag approximately 25% of issues, so they cannot replace the audit itself. They can, however, monitor for certain regressions and flag obvious problems on newly published pages.
For organizations using accessibility project management software, trend data should generate automatically from issue activity. If a team is still exporting spreadsheets and counting rows manually, the reporting will lag behind the work.
Frequently Asked Questions
Should we replace our audit report with trend reports?
No. The audit report identifies the issues and stays the source of truth for what needs fixing. Trend reports sit on top of that data and show how the work is progressing. Both serve different purposes.
How often should trend reports be reviewed?
Monthly is a reasonable cadence for most teams. Weekly review can be useful during active remediation pushes. Quarterly review tends to be too slow because patterns get buried before anyone notices them.
Can a single audit produce trend data?
One audit gives you a baseline, not a trend. Trends require at least two data points over time. The audit findings combined with weekly remediation tracking can produce trend data within the first month.
Do trend reports replace an ACR?
No. An ACR is a conformance document tied to a specific product version. Trend reports are internal tools that show progress between audit cycles. They serve different audiences and different purposes.
The audit is the start. The trend is the proof that the work is moving.
For help building an audit program that produces real trend data instead of one-off reports, Contact Kris.