by salaoo36 1 (0 reviews)

Scanoria Accessibility Audit – WCAG Checker & Accessibility Scanner for ADA and EAA

Name: Scanoria Accessibility Audit – WCAG Checker & Accessibility Scanner for ADA and EAA
Author: salaoo36

Find WCAG, ADA and EAA problems on your site. Scans pages as visitors see them, keeps your decisions between scans, and never phones home.

Scanoria Accessibility Audit ranks #72,871 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 Oct 4, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v0.2.1 Current Version v0.2.1

Updated 3 weeks ago Last Update on 04 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#329 of 765 in Accessibility Actively maintained

View on WordPress.org

Rank

#72,871

— No change

Active Installs

-50%

KW Avg Position

103.3

1 worse

Downloads

376

+2 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

59,934

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 #72,871

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: 0.2.1
Last Updated: Oct 04, 2026
Requires WP: 6.0+
Tested Up To: 7.1
PHP Version: 7.4 or higher
Author: salaoo36

Support & Rating

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

Keywords

EAA a11y accessibility 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 Scanoria Accessibility Audit – WCAG Checker & Accessibility Scanner for ADA and EAA

No. Automated testing finds a portion of accessibility problems — missing alternative text, insufficient colour contrast, unlabelled form fields, broken heading structure, links with no accessible name. Keyboard traps, confusing focus order, and whether your alternative text is actually meaningful all still need a person. This plugin is there to find the machine-detectable part quickly and keep track of what you have already dealt with.

No. There is nothing to sign up for and no key to enter.

No. There is no "our servers". The rules engine ships inside the plugin, the audit runs in your browser, and results are written to your own database. Nothing about your site or your visitors is transmitted anywhere. To be precise about the one thing that could look like an exception: the underlying rules engine is able to fetch stylesheets it cannot otherwise read, which in practice means CSS hosted on a third-party domain. That behaviour is switched off by default here, so a scan issues no requests of its own. Same-origin stylesheets — your theme and your plugins — are read directly and are unaffected. If you would rather have colour contrast scored against externally hosted CSS as well, enable it with the scanoria_preload_stylesheets filter. One consequence of testing the real page is worth stating plainly. A scan opens your own published URL in your browser, so whatever that page already loads for a visitor — a Gravatar avatar, a font or a map from another domain, an embedded video — loads during the scan too, from your browser, exactly as it would if you had simply visited the page yourself. The plugin adds nothing to that list and sends nothing of its own.

Visitors are never affected. The scanning code is only loaded during a scan you started, on a request that carries a one-time token and comes from a logged-in administrator.

Because that is what makes the results trustworthy. Your browser renders the page the same way a visitor's does, including anything your page builder or JavaScript produces. A server-side scan cannot see any of that.

The scan loads each page in a hidden frame on your own domain. Some security plugins block that with an X-Frame-Options: DENY header. The plugin relaxes it to SAMEORIGIN for verified scan requests only, but a plugin that sets the header later can still win. Check your security plugin's framing settings.

Yes, with the scanoria_rule_tags filter.

By default only administrators can, which keeps it out of the way of people writing content. Widen it with the scanoria_capability filter.

Deleting the plugin removes the stored scan results, because a re-scan recreates them in seconds. Your decisions — what you chose to ignore, what you marked as fixed, and the notes you wrote — are kept. Re-scanning cannot recreate those, and deleting and reinstalling a plugin is a common way to try to fix an unrelated problem; nobody should lose months of triage to it. Reinstall, scan again, and your decisions re-attach to the same elements. If you would rather leave nothing behind at all, add this to wp-config.php before deleting the plugin: define( 'SCANORIA_DELETE_ALL_DATA', true ); Deactivating the plugin, as opposed to deleting it, never removes anything.

Yes. Nothing needs to be edited or forked. On the PHP side: scanoria_loaded fires once every class exists and is the right place to bind (binding to plugins_loaded directly can run too early). scanoria_scan_recorded fires after a page's results are written, scanoria_decision_recorded and scanoria_decision_removed when somebody ignores or resolves a finding — the issue row is passed along with the decision, because the next scan deletes it. scanoria_admin_menu, scanoria_admin_assets, scanoria_admin_toolbar and scanoria_admin_after_results are the places to add screens, scripts and buttons, and scanoria_scan_targets filters what will be scanned. On the browser side, the scan runs in the page, so PHP alone cannot tell you a page finished: the screen dispatches scanoria:page-scanned on document after each page and scanoria:scan-complete at the end. The last one is cancelable — calling preventDefault() stops the automatic reload, in which case refreshing the view is up to you.