The WCAG scanner
Scan a page against WCAG 2.1 or 2.2, understand the score and work through the report.
The scanner loads a page from your own site, checks its HTML and saves a report. It finds problems a machine can detect. It cannot prove that a page is fully accessible, so use it as a first pass alongside manual checks.
Run a scan
- Open AccessIQ → WCAG Scanner.
- Enter the URL of a page or post on your site. Recent URLs are suggested as you type. A URL on another site is refused.
- Choose the WCAG version (2.1 or 2.2) and the level (A, AA or AAA). The same choices are in Settings → Scanner.
- Click Scan Now.
The score
The score starts at 100. Each error costs 10 points and each warning costs 3, down to a minimum of 0. The report says so itself: the score reflects only the automated checks that ran, not full WCAG conformance. A history chart of your last scans shows progress.
Read the report
- The report has three tabs: Overview (with a Fix these first list), Violations and History.
- Issues are grouped by impact: Critical (blocking), Serious (urgent) and Moderate (review).
- Each violation shows the WCAG criterion, the affected element and a hint on how to fix it. See Rule-by-rule fixes.
- Ignore an issue you have judged a false alarm, and restore it later if you change your mind.
- Print Report, or delete a scan from Scan Reports (you are asked to confirm).
Scheduled scans
In Settings → Scanner you can turn on the scanner, choose the WCAG level and version, set a notification email and pick daily, weekly or monthly scans. Each run scans your 10 most recent published pages and posts through WP-Cron and emails you a summary. Pro adds scans of URLs you choose. See Scheduled scans and PDF reports.
How long scans are kept
Scans are kept for 365 days. Developers can change this with the accessiq_scan_retention_days filter.