by
pragadees
1 (0 reviews)
Auditwright WCAG Accessibility Scanner
Scan every page of your site against WCAG 2.2 and see exactly which element fails, where it is, and how to fix it.
Auditwright WCAG Accessibility Scanner ranks #69,228 among WordPress.org plugins with 1+ active installations, is #429 of 644 in the Accessibility category, a 1/5 rating from 0 reviews, and was last updated Aug 5, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 7 (Current: 7.1.2)
v0.6.0
Current Version v0.6.0
Updated 1 month ago
Last Update on 05 Aug, 2026
Refreshed 8 hours ago
Last Refreshed on
#429 of 644 in Accessibility
Rank
#69,228
—
No change
Active Installs
1+
—
No change
KW Avg Position
75
58 better
Downloads
151
+1 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
56,291
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
Need 9 more installs to reach 10+
Rank Changes
Current
#69,228
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.6.0
- Last Updated
- Aug 05, 2026
- Requires WP
- 6.5+
- Tested Up To
- 7
- PHP Version
- 7.4 or higher
- Author
- pragadees
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,758
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,009
Max Mega Menu
300K+ installs
#163
Embed Plus for YouTube Gallery, Livestream and Lazy Loading with Facades
100K+ installs
#356
404 to 301 - Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring
100K+ installs
#422
Auto Image Attributes From Filename With Bulk Updater (Add Alt Text, Image Title For Image SEO)
100K+ installs
#424
Accessibility by UserWay
80K+ installs
#503
WP Accessibility
60K+ installs
#672
Accessibility Widget by OneTap – Easy One-Click Accessibility Toolbar
60K+ installs
#689
AccessiYes Accessibility Widget for ADA, EAA & WCAG Readiness
20K+ installs
#1,185
Frequently Asked Questions
Common questions about Auditwright WCAG Accessibility Scanner
No. It documents what was tested, when, and what is still wrong. That is a requirement in its own right, and it is honest, but writing a statement does not fix anything. The barriers listed in it are real and still need work.
There are two ways to do it and they behave differently on purpose. "Not a real problem" removes the finding completely. It stops being counted, and it stays gone through future scans. "Real, accepted for now" also takes it out of your working list, but keeps it in the record as a known barrier, along with the reason you gave. An accessibility statement has to declare known barriers, and a document that quietly drops a real failure is worth nothing. Either way the decision is attached to the finding itself, not to one scan of it, so it survives every re-scan. You can put anything back at any time.
No. Scanning runs entirely inside your own browser and results are stored in your own WordPress database. Nothing is transmitted to us or to any third party.
No, and be sceptical of anything claiming it will. Auditwright finds and documents problems automated testing can detect. Fixing them is real work, and full conformance also needs manual testing with assistive technology.
No. Overlays inject a script that tries to patch problems at page load. They are widely criticised by disabled users and accessibility practitioners, they do not fix the underlying code, and they produce no documentation. Auditwright changes nothing on your public site.
Because that is the only way to see a page as a visitor sees it, including styles from your theme and anything JavaScript added. It also means scanning works on ordinary shared hosting with no server-side browser required.
No. Nothing runs for your visitors. Scanning happens in the WordPress admin, when you ask for it.
Auditwright scans posts and pages. WooCommerce products and other custom post types are handled by the separate Pro add-on.
