Add pages to scan
- On Audits, click Add path and enter a path on your site, such as
/or/checkout. - Choose Auto scan: Off, Daily, Weekly or Monthly. Weekly is the default.
- The first scan runs right away. Scan all now rescans every path at once.
Start with the pages that matter most: home, a product or service page, the contact form and checkout. Pages built from the same template usually share the same issues, so one of each is enough at first.
Each scan uses one audit from your monthly allowance: 5 on Starter, 20 on Growth and 100 on Enterprise. The allowance starts again on the first of each month. When it runs out, new scans wait until then.
Score and status
Every path gets a score out of 100 from its latest scan. The status follows from the score.
- FailingScore 0 to 69
- IssuesScore 70 to 89
- PassingScore 90 to 100
The score on the Overview is the WCAG score across your latest audits.
Errors, warnings and notices
Accessora sorts axe-core’s findings into three groups:
| Group | What goes in it | Fix first? |
|---|---|---|
| Errors | Critical and serious problems that block or badly hurt some visitors. | Yes |
| Warnings | Moderate problems that make pages harder to use. | Next |
| Notices | Minor problems, and checks axe-core couldn’t decide that need a person. | Review |
Open an issue to see:
- The WCAG criterion and level, such as 1.1.1 A or 1.4.3 AA.
- How serious it is, from critical to minor.
- The elements it affects, with a CSS selector for each so you can find them.
When you’ve fixed something, click Re-scan on the results page to check it.
Was the widget on the page?
Each scan also notes whether the Accessora widget was found on the page:
- Widget on means the widget loaded during the scan.
- No widget means the page loaded without it, which is worth checking against your install.
- Auto-fixed means automated fixes ran before the scan, with the number of changes they made. The score then reflects the page with those fixes applied, not your source code.
- Fixes not run means automated fixes are switched on but didn’t run. Check your plan and the install.
Automated tools catch only part of WCAG. They can’t judge whether alt text is accurate, whether the reading order makes sense or whether a form is easy to use with a keyboard. Use audits to clear the measurable issues, then test the key flows yourself with a keyboard and a screen reader. The WCAG guide explains what to check by hand.