AuditWand Accessibility
by auditwand 0 (0 reviews)

AuditWand Accessibility

WCAG accessibility checker for WordPress. Check pages as you write, fix 16 common issues in one click, audit alt text, and scan every page on Pro.

AuditWand Accessibility ranks #61,919 among WordPress.org plugins with 0+ active installations, is #515 of 622 in the Accessibility category, and was last updated Sep 6, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v1.0.1 Current Version v1.0.1
Updated 1 week ago Last Update on 06 Sep, 2026
Refreshed 12 hours ago Last Refreshed on
#515 of 622 in Accessibility Downloads -77.6% this week Actively maintained
View on WordPress.org
Rank
#61,919
+6348 this week
Active Installs
0+
No change
KW Avg Position
88.3
No change
Downloads
94
+1 today
Support Resolved
0%
No change
Rating
0%
Review 0 out of 5
0 (0 reviews)

Next Milestone 10

Total Progress 10%
0+ 10+
34,116
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

49,860 55,062 60,264 65,466 70,668 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026
46,662 52,768 58,874 64,979 71,085 01-09-2026 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026
Current #61,919
Change
Best #

Upgrade to Pro

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

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026
0 10 20 30 40 50 60 01-09-2026 02-09-2026 03-09-2026 04-09-2026 05-09-2026 06-09-2026 07-09-2026 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026
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%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about AuditWand Accessibility

No, and be wary of any tool that says yes. No automated tool can. AuditWand finds a substantial subset of accessibility issues automatically, explains how to fix them, fixes the mechanical ones, and documents your ongoing effort. Fixing what it finds improves accessibility. Full conformance also requires human review: judging whether alt text describes an image, whether captions are accurate, whether content is understandable. Those are the parts no engine can test, and AuditWand says so on every clean result.
No account is needed for the local layer: unlimited page checks (they run locally in the editor), all 16 one-click fixes, auto-check on save, the Media Library Audit, and dismiss-with-reason with the complete Ignore Log all work on a fresh install with no connection. A free account connects your site for the cloud service and adds the badge and public status page; paid plans add site scans of every page, scheduled scans, history and trends, regression alerts, hosted statements, and PDF reports.
Before you connect: nothing. The plugin makes no outbound request of any kind, and an automated test suite proves it on every release. After you connect: your server sends your site address and page URLs to the AuditWand API, authenticated with your connect key, and site scans store findings with short HTML snippets from your public pages. Editor page checks run in your browser; the content you are editing is never sent. After a check completes, the plugin reports a bare counter (a check happened, and when) so your public status page can show activity. Everything is stored in the EU (Frankfurt). Deleting a site or your account removes it.
Small, safe corrections to the HTML your site sends to visitors: a skip link, visible keyboard focus, underlined content links, labels on the search box, comment fields, and placeholder-only form fields, the page language attribute, zoom allowed on phones, forced tab order removed, redundant tooltips removed, a note on links that open new tabs (or those links kept in the same tab), a fallback page title, file type and size on document links, PDF uploads blocked, and a footer link to your accessibility statement. Nothing changes in your database or your content. Each fix shows a before-and-after preview, can be turned off with one click, and is logged with a timestamp. With every fix off, your site's output is byte-for-byte what it was without the plugin.
No. Overlays inject a script into the visitor's browser that tries to patch the page after it loads. They are widely criticized by the accessibility community, regulators have acted against vendors who claimed such tools deliver compliance, and sites using them continue to receive complaints and claims. AuditWand ships zero visitor-side JavaScript. Its fixes are real server-side corrections to your site's HTML, and everything else it does is detection, guidance, and record-keeping.
No. With every fix off, the plugin adds nothing to your site's front end: no scripts, no styles, no requests. Each fix you enable adds only its own HTML change and, for a few fixes, a few hundred bytes of inline CSS. Site scans run on AuditWand's servers, which visit your public pages the way an ordinary visitor does, with a small number of parallel page workers and a polite pace. The whole plugin is 283 KB.
Every feature works from the AuditWand admin menu regardless of editor. The in-editor "Accessibility" box with the instant "Check this page" button appears in the block editor and the Classic Editor. Page-builder edit screens (Elementor, Divi, Beaver Builder, and others) cannot host the box; use the Pages tab in the AuditWand menu to see per-page findings, then open the page in your builder to fix them. Site scans and issue tracking behave identically for every editor.
Every combination of WordPress 6.5, 6.8, 7.0, and 7.1 with PHP 7.4, 8.1, 8.3, and 8.4: sixteen combinations, each booted with debugging on, every admin screen and the editor walked, and zero PHP notices. Also a classic-widgets theme (Twenty Twenty-One), a block theme (Twenty Twenty-Five), Astra, and multisite with network-wide activation. Builders: pages built in Elementor and Beaver Builder Lite, scanned, fixed, and marked by View on page. AuditWand works with any theme or builder that outputs standard HTML, because scans and fixes operate on the final rendered output. Issue tracking survives builder re-saves because issue fingerprints ignore builder-generated markup noise, and themes that declare the accessibility-ready tag never get the skip-link and focus fixes applied twice.
Email support@auditwand.com or post in the plugin forum at https://wordpress.org/support/plugin/auditwand-accessibility. Replies typically arrive within 1 to 2 business days. There is no phone line and no 24/7 desk; AuditWand is a one-person company with automated systems as the team, and we say so wherever support is mentioned. If you are facing litigation or need a formal audit, engage an accessibility professional: AuditWand is automated tooling for finding, fixing, monitoring, and documenting accessibility work, not an audit service and not legal advice.
EU accessibility rules generally expect an accessibility statement, a way for visitors to report problems, and evidence of ongoing effort. On the free plan, AuditWand generates an accessibility statement template pre-filled with your site's known limitations, and the public status page carries a visitor feedback form. The fix log and the Ignore Log with reasons are your dated evidence trail. Pro adds a hosted statement that updates itself from scan data and dated PDF reports mapped to EN 301 549 clauses. None of these documents claims compliance on your behalf; they describe what was checked, what was found, and what was done.

Sign In / Register

You need to sign in or register to use this feature.