by Lodestone 1 (0 reviews)

Lodestone Accessibility Audit - Accessibility Checker

Name: Lodestone Accessibility Audit - Accessibility Checker
Author: Lodestone

WCAG 2.2 accessibility checker: scan any page, get plain-English detail on every issue, publish a dated accessibility statement. Not an overlay.

Lodestone Accessibility Audit ranks #60,522 among WordPress.org plugins with 1+ active installations, is #329 of 765 in the Accessibility category, a 1/5 rating from 0 reviews, and was last updated Sep 27, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.0.13 Current Version v1.0.13

Updated 1 month ago Last Update on 27 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#329 of 765 in Accessibility

View on WordPress.org

Rank

#60,522

— No change

Active Installs

— No change

KW Avg Position

111.3

0.6 worse

Downloads

546

+3 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 30%

0+ 10+

47,585

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 7 more installs to reach 10+

Rank Changes

Current #60,522

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

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

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

Start Tracking Free

Plugin Details

Version: 1.0.13
Last Updated: Sep 27, 2026
Requires WP: 6.4+
Tested Up To: 7.1
PHP Version: 7.4 or higher
Author: Lodestone

Support & Rating

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

Keywords

EAA accessibility accessibility checker ada 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 Lodestone Accessibility Audit - Accessibility Checker

No, and be sceptical of any tool that says it does. Automated testing detects only a portion of accessibility barriers — commonly estimated at around a third. It is very good at the things machines can check: missing alternative text, insufficient colour contrast, unlabelled form fields, broken heading structure, invalid ARIA. It cannot tell you whether your alt text is meaningful, whether your page makes sense when read aloud in order, or whether a custom component actually works with a screen reader. This plugin finds the automatable third and is honest about the rest, including in the statement it generates for you.

https://madebylodestone.com/what-automated-accessibility-testing-misses

All three point at WCAG, and this tests against WCAG 2.2, which contains WCAG 2.0 and 2.1. So the

no automated tool can: the ADA has no regulation naming a version for private businesses, Section 508 incorporates WCAG 2.0 Level AA, and the European Accessibility Act works through EN 301 549.

was found, and a written reason against anything you chose not to fix.

No. It adds nothing to your front end for visitors — the only things it ever loads there are the scanner and "Show on page", and only for a signed-in editor who asked for them. Overlays inject JavaScript that alters your pages for visitors at runtime, which is a different product with a bad reputation it has earned — they frequently break the assistive technology they claim to help, and the disability community has been consistently clear that they are not a substitute for accessible markup. This plugin only reads your pages and reports on them.

The EAA is EU legislation, in force since June 2025, that requires a range of products and services — including many websites and e-commerce operations — to meet accessibility requirements. In practice conformance is assessed against EN 301 549, which incorporates WCAG. It generally expects you to be able to show what you tested, when, what you found, and what you decided about anything you did not fix. That evidence trail is what the ignore log and the audit export exist to produce.

No. axe-core is bundled with the plugin and runs in your browser, against your own site, on your own machine. Your pages, your scan results and your ignore reasons never leave your server. The only component that could is the Freemius SDK, which handles licensing, and it starts switched off. It contacts nothing on its own until you choose to opt in. The exceptions are things you do yourself: opening the upgrade page loads prices from Freemius, and the optional feedback form shown when you deactivate is sent if you fill it in. Neither carries any page or scan result. Opting in is offered rather than required, it tells you exactly what it would share first (your WordPress user's name and email address, your site address and title, your WordPress and PHP versions, and the list of plugins and themes installed), and every feature works the same either way.

Contrast ratios, computed styles and focus order only exist once a page has actually been laid out by a browser. There is no way to evaluate them by parsing HTML on the server, and any tool that claims to will give you wrong answers. So the scanner loads your page in an offscreen frame and measures the real rendered result. The frame is only ever created for a logged-in user with editing permission, and the scanning script is never loaded for ordinary visitors.

Yes. Unpublished posts are scanned through their preview link, and the result is recorded against the post itself, so its history carries over when you publish.