Ignore with intention.
Some findings need context. Keep deliberate exceptions scoped to what you’ve reviewed, so an irrelevant result doesn’t bury the issues that still matter.
A clearer path to
accessible
WordPress.
Find the barriers. Understand the evidence.
Make your next fix count.
Free for agencies & developers. Version 1.6.1 release candidate.
Inside WordPressPowered by axe-coreWCAG-informed findingsBuilt to stay useful. Built to be free.
From “there’s an issue”
to “here’s where to start.”
A finding should help you do the work. Explore how clear evidence, meaningful context, and a focused next step come together.
Select a finding to explore the exampleIssue explorerIllustrative report
Findings 3
Element evidenceFinding 1 of 3
Image missing alternative text
WCAG 1.1.1 · Non-text Content
.team-photo
<img class="team-photo" src="team.jpg">Why it matters
This image has no text alternative. People using a screen reader may miss the information it conveys.
A practical next step
Describe the image’s purpose with useful alt text. If it is purely decorative, use an empty alt attribute.
Context you can take into your next fix.
Sample content, not a live scan. This preview illustrates the kind of evidence ClearA11y surfaces.
Your workflow.
With more clarity.
From the first audit to the next content update, keep accessibility work close to the site you’re building.
- 01
Scan the site you actually ship.
Check published WordPress content and surface issues in the place your team already works.
- 02
Get the evidence behind the issue.
Review severity, WCAG references, affected elements, and page context to decide what needs attention.
- 03
Fix, review, and keep going.
Make changes, run another scan, and use carefully scoped exceptions for findings you’ve deliberately reviewed.
Built for the details
that make a difference.
See the page. Find the element.
Move from an issue to its evidence, selectors, and affected content. Give developers a concrete starting point.
Keep recurring checks on the calendar.
Queue recurring scans with WordPress cron. Browser processing runs while an authorized admin page is active.
Work where the content lives.
Review page reports and explore findings in WordPress, without adding another dashboard to your daily handoff.
A useful tool.
An honest starting point.
Accessibility is ongoing work.
Your tools should help you do it.
ClearA11y is a free WordPress accessibility plugin. Useful local scanning is the foundation, not a teaser for a paid plan.
Automated checks are one part of the process. Bring your judgment, test with people, and keep improving the experience.
A few things
worth knowing.
Is ClearA11y free?
The local WordPress plugin is free. A future paid service may offer deeper external scanning and richer reporting, but the plugin is intended to remain useful on its own.
Does a clean scan mean my site is accessible?
No. Automated checks find some accessibility issues, but they cannot assess every interaction or experience. Pair the findings with keyboard testing, assistive technology testing, and human review. ClearA11y does not certify WCAG conformance.
What does it scan?
ClearA11y scans published WordPress content. It uses axe-core in the browser and PHP checks on the server to find issues and attach useful evidence. The checks available depend on how the scan runs; browser checks can inspect rendered content that server checks cannot.
Can I schedule scans?
Yes. Scheduled scans use WordPress cron to queue work. Their timing depends on site traffic or a server cron configuration. Browser processing requires an active authorized admin page; scheduling does not provide a standalone headless browser service.
How do ignored findings work?
Exception rules let you suppress findings that have been deliberately reviewed. Scope matters: use the narrowest rule that matches your decision so unrelated issues remain visible. Review exceptions as the site changes.
What do I need to run it?
A WordPress site running WordPress 6.0 or later and PHP 8.0 or later. Download the ZIP, then go to Plugins → Add New → Upload Plugin in WordPress. Choose the ZIP, install it, and activate ClearA11y. The current download is the 1.6.1 release candidate.
Make the next fix
a little clearer.
Free WordPress accessibility scanning.
Built with agency work in mind.
Version 1.6.1 · Release candidate
Your next audit starts here.
Download the plugin ZIP and install it from Plugins → Add New → Upload Plugin in WordPress.
Download plugin Download SHA-256 checksumWordPress 6.0+ · PHP 8.0+