WordPress plugin intelligence profile

Esmo Accessibility Scanner

Check your site against WCAG 2.2 AA with axe-core, right in wp-admin. Get a score, prioritized issues, fix guidance and optional auto-fixes.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.3.1
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.4 · PHP 8.0
Directory statusactive
Last directory update29 Oct 20264d ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Esmo Accessibility Scanner version 1.3.1 as active, updated 4d ago and tested up to WordPress 7.1.

Overview

About this plugin

2 Level A and AA from the admin dashboard. It runs the widely used axe-core engine in your browser against the fully rendered front end of each page, so it sees what visitors see: computed colour contrast, ARIA, headings, landmarks, form labels, images, links and more.

js or headless browser on the server. If your site runs WordPress, it can be scanned.

What you get

  • Full-site or single-page scans. Posts, pages, public custom post types (including WooCommerce products) and, optionally, category and tag archives. Start a single-page scan from the “Scan accessibility” link in the toolbar while viewing any published page.
  • Real rendered-page analysis with axe-core 4.10 plus extra checks for generic link text (“click here”), placeholder-only form fields, links that open new windows without warning, and linked PDF documents.
  • Best-practice checks (optional, on by default) for headings, landmarks and page structure. They are reported as warnings because they are not strict WCAG failures.
  • Clear, actionable issues. Every finding has a severity (Critical, Major, Minor, Warning), the WCAG success criterion, the affected page, the element and its HTML, a recommended fix and a link to documentation.
  • An accessibility score from 0 to 100 for every scan, with Excellent, Good, Needs Improvement and Poor bands, and a progress-over-time chart.
  • Dashboard with issues by severity, WCAG category distribution, the most common problems and recent scans.
  • Optional automatic fixes you can switch on one by one: skip link, visible keyboard focus, underlined content links, a language attribute, new-window warnings, zoom-friendly viewport, removal of positive tabindex and redundant title attributes, and search-form labels.
  • CSV and JSON export of every scan for your team, agency or audit records.
  • Works on single sites and multisite networks, including network activation.

What automated testing can and cannot do

Automated tools, including this one, find a meaningful share of accessibility problems, but not all of them. Many WCAG requirements (meaningful alternative text, logical reading order, captions, keyboard-only workflows, plain language) still need a human review. Esmo Accessibility Scanner helps you find and fix issues faster; it does not certify that a site is accessible or legally compliant with the ADA, the European Accessibility Act, EN 301 549 or Section 508.

Privacy

  • Scans run on your own site and in your own browser. Page content and results are never sent to the plugin author or any third party.
  • Results are stored in your WordPress database and removed when you delete the plugin.
  • The issues list links to rule documentation on dequeuniversity.com and w3.org. Those sites are only contacted if you click a link.
  • While scanning, pages are loaded in a hidden frame as the logged-in administrator, so scripts on your pages run just as they do when you open them yourself. Analytics or ads on your site may count those page views.
  • Automatic fixes only change your site’s front end, and only the ones you enable.

Third-party library

0, which is compatible with the GPL. js.

For developers

Filters and actions let you change the scan queue, the axe-core options, the capabilities needed for reports and for settings, and more. See the developer documentation on GitHub.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • accessibility checker
  • a11y
  • audit
  • wcag
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.4 · PHP 8.0
Update activity29 Oct 20264d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.