Setting up disclosures and warnings once is only half the job – content changes, gets forgotten, and quietly goes stale. The Compliance Audit runs a scan across every published post and page and gives you a single report of what needs attention, so you’re not relying on memory to catch it.
This guide walks through what each number on the report actually means and what to do about it.
What You’ll Learn
- Where to find the Compliance Audit report and how often it updates
- What “scanned,” “open accessibility issues,” and “stale content” actually count
- How to run a fresh audit on demand
- Where to see your compliance health score and how it trends over time
Finding the Report
Go to Compliance Copilot > Compliance Audit in your WordPress dashboard. You’ll see a table with four rows:
- Posts & pages scanned – the number of published posts and pages checked in the last run
- With open accessibility issues – how many of those have unresolved accessibility issues flagged on them
- Stale content – how many haven’t been updated within your configured freshness threshold
- Last checked – when the report you’re looking at was generated
An audit runs automatically once a week, so “Last checked” should never be more than seven days old on an active license. If it’s stuck, running one manually (below) will confirm whether the scheduled check is working.
Running an Audit On Demand
You don’t have to wait for the weekly schedule. On the Compliance Audit page, click Run Audit Now. The scan runs immediately and the table above updates with the fresh numbers – useful right after you’ve published a batch of new content or fixed a round of issues and want to confirm the count actually dropped.
Understanding What Gets Counted
Open accessibility issues reflects posts that already have accessibility issues flagged on them by the plugin’s per-post checker – the audit doesn’t run a separate accessibility test of its own, it’s tallying what’s already been flagged. Fix the underlying issue on the post itself and the count drops on the next scan.
Stale content is based on your freshness threshold, set on the Settings tab under Content Freshness Warnings. Lowering the threshold will surface more posts as stale; raising it will surface fewer. There’s no universally “correct” number here – it depends on how often your content type actually needs revisiting.
Health Score and History
The Compliance Audit page shows a single point-in-time snapshot. For the bigger picture, go to Compliance Copilot > Dashboard to see the same data expressed as a 0-100 compliance health score, weighted toward accessibility issues over stale content, plus a history table showing how that score has moved across previous audit runs. A site with nothing scanned yet starts at 100 by default – there’s nothing to be penalized for.
Use the Dashboard when you want a trend at a glance; use the Compliance Audit page when you want the raw counts and the “Run Audit Now” button.
Related Resources
- WCAG 2.1 Quick Reference (W3C Web Accessibility Initiative)
- ADA.gov – Americans with Disabilities Act information and technical assistance
Automated auditing and the compliance health score are part of the full Compliance Copilot Pro feature set.