About this plugin
Scanoria Accessibility Audit checks your WordPress site against the Web Content Accessibility Guidelines and shows you what to fix, in your own dashboard.
It scans the page your visitors actually get.
The audit opens each published URL, waits for the page to finish rendering, and inspects the result. Whatever your theme, your page builder or your JavaScript puts on the page is part of what gets checked, because the audit reads the finished page in the browser instead of parsing stored post content.
Your decisions survive the next scan.
When you mark an issue as resolved, or decide that a particular one does not apply to you, that judgement sticks. Add a paragraph, reorder a section, let your page builder regenerate its element ids — the issue is still recognised as the same issue and your decision is still attached to it. Each finding is identified by several properties of the element itself rather than by its position in the document, which is what lets a decision survive an edit.
If the same finding appears in your footer on every page, you can dismiss it once for the whole site.
Nothing leaves your server.
No account. No sign-up. No API key.
No external CDN, no fonts loaded from elsewhere, no telemetry, no usage limits, no per-page or per-visit metering. The rules engine is bundled with the plugin, the audit runs in your own browser, and the results are stored in your own database. Install it on as many sites as you like.
What it checks
The audit is powered by axe-core, the open source rules engine used by accessibility professionals. Findings are reported with the WCAG success criterion they relate to, the offending markup, and a link explaining how to fix it.
1 AA is not buried in AAA findings it has no obligation to address.
How to use it
- Open Accessibility in the admin menu.
- Press Scan published content and leave the tab open while it works. Progress is announced as each page is checked.
- The results table lists every scanned page with its number of open findings. Press View issues on a page to see them, worst impact first.
- Each finding shows the WCAG criterion, the markup that failed, and a link explaining the fix. Use Ignore for something that genuinely does not apply, or Resolved once you have fixed it, and add a note if you want to remember why. Tick everywhere to apply that judgement to the same element across the whole site.
- Re-scan whenever you like. Findings are recalculated from scratch and your recorded judgements are re-attached.
Three filters cover configuration, so there is no settings page to fill in: scanoria_capability (who may scan; administrators only by default), scanoria_rule_tags (which conformance level to report) and scanoria_preload_stylesheets (whether to allow reading externally hosted CSS). See the FAQ for details.
What it does not do
It does not add a toolbar, widget, or overlay to the front end of your website. It reports what needs fixing in the markup, and the fixing is done by you or your developer.
It also cannot make your site accessible by itself. Automated checks find a meaningful share of the common failures — missing alternative text, insufficient contrast, unlabelled fields, broken heading order — while judgements like whether your alternative text is actually meaningful still need a person.
Scanoria Pro (optional, paid)
Everything above is free and stays free. Scanoria Pro is a separate add-on for people who hand results to a client: a CSV export, a printable report you can save as PDF, and a record of what appeared and cleared since the previous scan. It works through this plugin’s public hooks and makes no external requests either.
Third-party libraries
0. txt. 1.
axe-core is used locally and makes no network requests.