Find out where your site fails WCAG 2.2 — and get the European Accessibility Act statement you are required to publish. Accessibility Audit scans your published pages and posts against 25 automated checks and reports what to fix, grouped so that one theme colour failing on twelve pages reads as one fix, not twelve problems.

The scan runs in your own browser

No page content is ever sent anywhere. The scan loads each page in a frame inside your WordPress admin and reads the finished, rendered result — which is why it can measure real colour contrast, resolving inherited colours, translucent overlays and CSS variables. A server-side HTML parser cannot see any of that: it reads the source, not what a visitor sees.

That also means: no external service, no API key, no per-scan fee, no data-processing agreement to sign, and nothing added to your front end for visitors.

What it checks

25 automated checks across WCAG 2.2 levels A and AA, covering criteria 1.1.1, 1.3.1, 1.4.2, 1.4.3, 1.4.4, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 3.1.1, 3.3.2, 4.1.1 and 4.1.2 — images without alternative text, buttons and links with no accessible name, form fields with no label, insufficient contrast, skipped heading levels, duplicate ids, tables without header cells, positive tabindex, frames without a title, and more.

A report you can act on

• Grouped by rule, not by page. Each group shows impact, the WCAG criterion, and how widespread it is — “12 occurrences across 3 pages”.
• Straight to the fix. Where possible each finding links to that page’s editor or to the Media Library entry. That is the advantage of running inside WordPress instead of as an external scanner.
• A verdict in words, not just a number. A bare score invites the wrong conclusion; the report says plainly whether critical barriers are blocking people.
• Comparison between scans. Fix something, scan again, and see exactly which rules cleared — and which are new.

The European Accessibility Act statement

Since 28 June 2025 businesses selling goods or services to consumers in the EU must publish information about the accessibility of their digital services. With a licence, the generator builds that statement — prefilled from your latest scan, with the barriers and their success criteria already listed — and publishes it as a real page you can link from your footer.

Free and licensed

Without a licence the scanner is complete and genuinely usable: 20 checks, up to five pages per scan, the last three scans kept, full report and comparison.

A licence adds:

• Every page, with no five-page limit
• Five further WCAG 2.2 checks: touch target size, autocomplete on personal data fields, list structure, main landmark, and language of passages
• Unlimited scan history
• The EAA accessibility statement generator

One download either way. Entering your purchase code unlocks everything in place — nothing to re-install.

Requirements

• WordPress 6.2 or newer
• PHP 7.4 or newer
• A modern browser for the admin screen — the scan runs there

What it does not do

Being straight about this saves us both time.

• Automated testing finds roughly a third of accessibility barriers. A clean report is a good sign, not a conformance statement. Keyboard and screen reader testing by a person is still required for WCAG or EAA conformance, and no tool on the market changes that.
• It scans pages and posts. Individual WooCommerce product pages are not in the scan list. Your shop, cart and checkout pages are, because those are pages.
• Pages that refuse to be framed cannot be scanned. If a page sends X-Frame-Options: DENY or a restrictive frame-ancestors, you get a clear error rather than a false “clean” result.

Tested against

WordPress 7.0, six themes (Twenty Twenty-Five, Twenty Twenty-One, Astra, GeneratePress, OceanWP, Kadence), Elementor and SiteOrigin, multisite, a 510-item site, and a single page with 3000 paragraphs. Alongside WooCommerce, Contact Form 7, WPForms and ACF with no conflicts.

During that testing the scanner found a genuine WCAG 4.1.2 failure in WooCommerce’s own Mini Cart — a drawer marked aria-hidden="true" whose buttons stay visible and reachable by keyboard. It finds real problems in real software.