by esmobg 0 (0 reviews)

Esmo Accessibility Scanner

Name: Esmo Accessibility Scanner
Author: esmobg

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.

Esmo Accessibility Scanner ranks #67,357 among WordPress.org plugins with 0+ active installations, is #496 of 765 in the Accessibility category, and was last updated Oct 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.3.1 Current Version v1.3.1

Updated 3 days ago Last Update on 29 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#496 of 765 in Accessibility Actively maintained

View on WordPress.org

Rank

#67,357

— No change

Active Installs

— No change

KW Avg Position

108

2 worse

Downloads

121

+4 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

39,789

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 9 more installs to reach 10+

Rank Changes

Current #67,357

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.3.1
Last Updated: Oct 29, 2026
Requires WP: 6.4+
Tested Up To: 7.1.4
PHP Version: 8.0 or higher
Author: esmobg

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

a11y accessibility accessibility checker audit wcag

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Embed Plus for YouTube Gallery, Livestream and Lazy Loading with Facades

100K+ installs

#360

Auto Image Attributes From Filename With Bulk Updater (Add Alt Text, Image Title For Image SEO)

100K+ installs

#428

404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring

100K+ installs

#429

Accessibility by UserWay

80K+ installs

#509

Accessibility Widget by OneTap – Easy One-Click Accessibility Toolbar

AccessiYes Accessibility Widget for ADA, EAA & WCAG Readiness

20K+ installs

#1,116

View all Accessibility plugins

Frequently Asked Questions

Common questions about Esmo Accessibility Scanner

No tool can do that on its own. Automated checks catch many common problems quickly, but some WCAG requirements can only be verified by a person. Use the report to fix what is found, then test key pages with a keyboard and a screen reader.

No. The scan runs in the administrator's browser using a hidden frame on your own site, so standard WordPress hosting is all you need.

The axe-core engine runs in your browser, one page at a time. If you close the tab, the scan stops. A scan that has made no progress for 15 minutes is marked as failed when the next scan starts.

The scan frame must be allowed to load your own pages. Security headers such as X-Frame-Options: DENY or Content-Security-Policy: frame-ancestors 'none' block this. X-Frame-Options: SAMEORIGIN and frame-ancestors 'self' work. A very strict script-src policy can also stop the scanner from loading axe-core in the frame. Other pages in the scan continue normally.

No. Pages are scanned as the logged-in administrator, so the toolbar is present, but it is excluded from all checks.

WCAG 2.0, 2.1 and 2.2 at Level A and AA (choose A or AA in Settings), plus optional axe-core best practices. Each issue shows the related WCAG success criterion.

Each scanned page starts at 100 and loses points per issue: Critical 10, Major 5, Minor 2, Warning 1, never going below 0. "Needs review" items, which axe-core cannot decide on its own, are listed for you to check but cost nothing. The site score is the average of all scanned pages, so a few problem pages do not hide an otherwise good site.

Up to 1,000 URLs by default: the home page, then published content in ID order. Developers can raise or lower the limit with the esmoas_scan_url_limit filter.

Each fix is off by default and changes only one thing, using WordPress hooks rather than editing your theme. Turn on one fix at a time and check your site afterwards. Fixing problems in your content and theme is always the best long-term solution.

Yes. Activate it on individual sites or network-activate it. Each site keeps its own settings and results, and deleting the plugin removes the data from every site.