Title: Cleara11y
Author: cleara11y
Published: <strong>September 24, 2026</strong>
Last modified: September 24, 2026

---

Search plugins

![](https://ps.w.org/cleara11y/assets/banner-772x250.png?rev=3711306)

![](https://ps.w.org/cleara11y/assets/icon-256x256.png?rev=3711306)

# Cleara11y

 By [cleara11y](https://profiles.wordpress.org/cleara11y/)

[Download](https://downloads.wordpress.org/plugin/cleara11y.1.6.2.zip)

 * [Details](https://wordpress.org/plugins/cleara11y/#description)
 * [Reviews](https://wordpress.org/plugins/cleara11y/#reviews)
 *  [Installation](https://wordpress.org/plugins/cleara11y/#installation)
 * [Development](https://wordpress.org/plugins/cleara11y/#developers)

 [Support](https://wordpress.org/support/plugin/cleara11y/)

## Description

Cleara11y helps agencies, developers, and content teams audit published WordPress
pages and posts from the WordPress dashboard.

 * Run browser-based accessibility checks using the bundled axe-core engine.
 * Review findings by page, rule, severity, and scan.
 * Inspect element selectors and evidence to help locate issues.
 * Distinguish detected violations from findings that need manual review.
 * Track recurring findings and manage exceptions with review history.
 * Highlight findings on the front end for authorized users.
 * Queue scans and configure recurring scan schedules.

The plugin runs locally within WordPress and your browser. No Cleara11y account,
paid subscription, or external scanning service is required.

#### Scanning and manual review

Automated checks cover only part of accessibility testing. Cleara11y does not certify
WCAG compliance or automatically repair your site. Combine results with keyboard,
screen reader, and other manual testing.

Browser scans require an authorized WordPress admin page to remain open while queued
pages are processed. Scheduled scans queue work using WP-Cron; browser processing
still needs an active authorized admin session. Site traffic and hosting configuration
affect WP-Cron timing. Server-side checks have different coverage from the rendered-
page browser engine.

#### Privacy and stored data

Scan records, page URLs and titles, element selectors, HTML evidence, and exception
history are stored in your WordPress database. Evidence can contain content from
scanned pages. Restrict access to reports and database backups accordingly. Scanning
loads your site’s pages, including resources and third-party services already used
by your theme and content.

Cleara11y does not send scan results to an external Cleara11y service and does not
require a remote axe-core CDN. Links to accessibility guidance open external websites
only when followed.

Deactivation retains scan data. Deleting the plugin removes its scan and exception
tables and settings for the current site. Back up reports before deleting it. Network-
wide multisite deployment has not been verified.

#### Third-party code

This plugin includes axe-core 4.10.2 by Deque Systems, Inc., licensed under the 
Mozilla Public License 2.0. The distributed file is assets/js/axe.min.js. The corresponding
human-readable source is available at https://github.com/dequelabs/axe-core/tree/
v4.10.2 and https://unpkg.com/axe-core@4.10.2/axe.js . License text is included 
in licenses/axe-core-MPL-2.0.txt.

## Screenshots

[⌊Dashboard with scan progress and page accessibility findings on a demonstration
site.⌉⌊Dashboard with scan progress and page accessibility findings on a demonstration
site.⌉[

Dashboard with scan progress and page accessibility findings on a demonstration 
site.

[⌊Issues explorer for reviewing findings by page, rule, and severity.⌉⌊Issues explorer
for reviewing findings by page, rule, and severity.⌉[

Issues explorer for reviewing findings by page, rule, and severity.

[⌊Exception management for reviewed findings.⌉⌊Exception management for reviewed
findings.⌉[

Exception management for reviewed findings.

## Installation

 1. Upload the cleara11y folder to /wp-content/plugins/, or install the ZIP through
    Plugins > Add New Plugin > Upload Plugin.
 2. Activate Cleara11y in the Plugins screen.
 3. Open Cleara11y in the WordPress dashboard.
 4. Select published content and start a scan. Keep an authorized admin page open until
    browser scanning finishes.
 5. Review findings, verify them manually, and rescan after making changes.

Your site must allow the WordPress REST API and same-site page loading for browser
scans. Security plugins, restrictive framing policies, password protection, and 
caching can affect scanning.

## FAQ

### Does Cleara11y make my site accessible?

No. It identifies potential issues and provides evidence for review. Fixes must 
be made in your content, theme, or other plugins, and manual testing remains necessary.

### Is a subscription required?

No. The local plugin works without a subscription or Cleara11y account.

### Can I ignore an irrelevant finding?

Yes. Use exceptions after reviewing the finding and its scope. Broad exceptions 
can hide relevant findings, so review them periodically.

### Why has my scheduled scan not finished?

WP-Cron queues scheduled work. Browser scans are processed while an authorized admin
page is open. Check the queue, REST API availability, and browser console if progress
stops.

### Will uninstalling remove my data?

Deleting the plugin removes its current-site scan and exception tables and settings.
Deactivation retains them. Back up any data you need before deletion.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Cleara11y” is open source software. The following people have contributed to this
plugin.

Contributors

 *   [ cleara11y ](https://profiles.wordpress.org/cleara11y/)

[Translate “Cleara11y” into your language.](https://translate.wordpress.org/projects/wp-plugins/cleara11y)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/cleara11y/), check 
out the [SVN repository](https://plugins.svn.wordpress.org/cleara11y/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/cleara11y/) by [RSS](https://plugins.trac.wordpress.org/log/cleara11y/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.6.2

 * Harden request validation and stored-data rendering across admin and frontend
   views.
 * Scope maintenance behavior and restore shared XML parser state after scans.
 * Enqueue admin and highlighting assets through WordPress.
 * Validate and sanitize browser results before storing scan jobs.
 * Limit cache bypass to validated, page-bound scan requests.
 * Escape attribution metadata while preserving the audited page markup.

#### 1.6.1

 * Initial WordPress.org submission candidate.
 * Browser scanning, page reports, finding evidence, and exception management.
 * Hardened scan queue permissions, scan-token expiry, output escaping, and uninstall
   cleanup.

## Meta

 *  Version **1.6.2**
 *  Last updated **14 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.0 or higher **
 *  Tested up to **7.1.2**
 *  PHP version ** 8.0 or higher **
 * Tags
 * [a11y](https://wordpress.org/plugins/tags/a11y/)[accessibility](https://wordpress.org/plugins/tags/accessibility/)
   [accessibility audit](https://wordpress.org/plugins/tags/accessibility-audit/)
   [wcag](https://wordpress.org/plugins/tags/wcag/)
 *  [Advanced View](https://wordpress.org/plugins/cleara11y/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/cleara11y/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/cleara11y/reviews/)

## Contributors

 *   [ cleara11y ](https://profiles.wordpress.org/cleara11y/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/cleara11y/)