WordPress accessibility scanner
Most WordPress accessibility problems come from themes, page builders and plugins, not WordPress itself. Paste your site URL and get a free, prioritized view of what needs fixing.
Scans up to 5 pages of your site against WCAG 2.1 A/AA and EN 301 549 — works with any theme or builder.
Where WordPress sites fail accessibility
WordPress core is a small part of what actually ends up on the page. The accessibility issues that matter usually come from the layers built on top of it:
- Themes — colour palettes, navigation menus, and heading structures set by the theme, often without accessibility in mind.
- Page builders — drag-and-drop layouts that can generate markup with missing landmarks, non-semantic headings, or controls that don't work with a keyboard.
- Plugins — sliders, forms, popups and booking widgets added over time, each with their own accessibility track record.
- Missing alt text in the media library — images uploaded by content editors without alt text ever being added, page after page.
“Accessibility-ready” themes aren't a guarantee
The WordPress theme directory has an “accessibility-ready” tag, which signals that the theme met certain accessibility criteria at review time. It's a reasonable starting point, but it doesn't guarantee a WCAG-conformant final site. Once you add a page builder, install plugins, and add your own content and images, the tag no longer covers what visitors actually experience — the final result depends on everything layered on top of the theme.
From scan to fix
- 1.Run the free scan above. It reads the rendered HTML of your site and returns a legal-risk ranked report of issues found.
- 2.Fix issues with your developer, in your page builder, or directly in your theme files — each issue includes code-level fix guidance.
- 3.Publish an accessibility statement with our statement generator to record what was tested and what you did about it.
What this scanner does — and honestly doesn't
Automated scanning, including ours, detects roughly 30% of WCAG success criteria. It reliably finds missing alt text, poor colour contrast, unlabelled form fields and structural heading problems introduced by themes and page builders. It can't judge whether your alt text is actually meaningful or whether a builder-generated layout makes sense to someone navigating by keyboard alone. For higher-risk sites, pair automated monitoring with a manual audit, which typically costs $20,000–60,000 for a full-cycle review or $100–250 per page.
Frequently asked questions
Does this work with any theme or page builder?
Yes. The scanner reads the rendered HTML your site actually outputs, so it works whether you're using a classic theme, a block theme, or a page builder plugin.
Am I in EAA scope?
If you sell products or services to customers in the EU, you're very likely in scope, regardless of where your site is hosted. Micro-enterprises — fewer than 10 employees and under €2 million annual turnover — are exempt from the services obligations. Above that threshold, EU-facing sales generally bring you into scope.
Is an accessibility overlay plugin enough?
No. The European Commission's position is that overlay widgets alone do not achieve EAA compliance, and more than 800 businesses using overlay widgets have been sued over accessibility despite having one installed. An overlay plugin adjusts your page at runtime — it doesn't change the underlying theme, builder, or plugin code that a regulator or court would examine.
Scan your site now
Free, instant, and no account required.