by wkh0000 1 (0 reviews)

reala11y – Accessibility Checker & Auto-Fix: WCAG 2.2 Scanner, AI Alt Text, ADA & EAA Audit

Name: reala11y – Accessibility Checker & Auto-Fix: WCAG 2.2 Scanner, AI Alt Text, ADA & EAA Audit
Author: wkh0000

Accessibility checker & auto-fix: audit posts for WCAG issues, fix them at the code level, add AI alt text. A real fix, not an overlay widget.

reala11y ranks #61,110 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 22, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7 (Current: 7.1.4)

v1.14.0 Current Version v1.14.0

Updated 1 month ago Last Update on 22 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#329 of 765 in Accessibility

View on WordPress.org

Rank

#61,110

— No change

Active Installs

— No change

KW Avg Position

89.3

0.6 worse

Downloads

896

+2 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 30%

0+ 10+

48,173

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 #61,110

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.14.0
Last Updated: Sep 22, 2026
Requires WP: 6.4+
Tested Up To: 7
PHP Version: 8.1 or higher
Author: wkh0000

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 reala11y – Accessibility Checker & Auto-Fix: WCAG 2.2 Scanner, AI Alt Text, ADA & EAA Audit

No tool can. reala11y identifies common WCAG issues and remediates a defined subset at the code level. Full conformance requires manual review and user testing.

Yes — bring your own OpenAI, Anthropic, or Google Gemini key. The AI authoring features then work in this free version at no extra charge from us; your provider bills you directly for what you use. reala11y never resells or proxies AI usage.

Overlay widgets (e.g., accessiBe, UserWay) inject a floating JavaScript layer that does not modify the underlying HTML. Screen readers continue to see the original, unfixed page. The FTC fined accessiBe $1,000,000 on April 21, 2025 for claiming automated WCAG compliance. reala11y instead applies fixes to the actual HTML that browsers, screen readers, and crawlers see.

The free plugin scans against the full WCAG 2.2 AA profile — the current W3C Recommendation (October 5, 2023). Its 26-rule library spans success criteria introduced across WCAG 2.0, 2.1, and 2.2. reala11y Pro adds version-targeted scan profiles for WCAG 2.0 AA (the level referenced by Section 508) and WCAG 2.1 AA (referenced by EN 301 549, the standard behind the European Accessibility Act), for teams that need to report against a specific version.

The EAA became enforceable on June 28, 2025, and its technical standard (EN 301 549) references WCAG 2.1 AA. reala11y detects WCAG issues on your pages, applies safe code-level fixes, and generates the documentation an EAA compliance effort typically needs — an accessibility statement template and a conformance report. Like all automated tools it detects a portion of WCAG issues; pair it with manual review, and consult a qualified accessibility professional for high-risk sites.

If you are looking for an accessiBe or UserWay alternative that fixes the underlying HTML instead of layering a JavaScript widget on top, reala11y is built for that. Overlay widgets leave the original page unchanged for screen readers; reala11y edits the actual code. As context, the FTC fined accessiBe $1,000,000 on April 21, 2025 over automated WCAG compliance claims.

Yes. The scanner flags images missing alt text (WCAG 1.1.1), and the bring-your-own-key AI tools can draft an alt-text suggestion using your own OpenAI, Anthropic, or Google Gemini key. Every suggestion is shown for your review and is never applied automatically.

Nothing changes without your say-so. Out of the box reala11y only scans: no fix is applied automatically, because the "auto-apply safe fixes" setting is off by default. When you do apply one, reala11y makes only Tier 1 ("safe") changes to your content — attribute-level edits that leave your text and markup structure alone. Examples: adding rel="noopener" to a link that opens in a new tab, removing a duplicate id, or stripping a redundant title attribute from an image. (Removing an image's title attribute also removes the tooltip some browsers show on hover. That is the intent: the tooltip usually repeated the alt text and was never available to keyboard or touch users.) The optional render-time fixes are deliberately different: a visible focus outline or a larger touch target is meant to change how the page looks. Each one is off until you switch it on. Every applied fix is logged, and one-click undo restores the exact content from before it ran. A single Safe Mode switch turns every fix off at once.

A visitor's page never waits for a scan. Scans are queued and carried out in the background by WP-Cron: the worker fetches the page over a separate request, much as a browser would, then analyses the HTML that came back. (As with all WP-Cron work on a standard install, that background request can be set off by site traffic, but it runs on its own and does not hold up the page your visitor sees.) The optional render-time fixes (skip link, visible focus outline, minimum target size, main landmark, restored pinch-zoom) stay off until you enable them individually. Once enabled they add a small amount of markup or CSS to the page, and no external requests.

reala11y scans the HTML your site actually sends to the browser, so it sees whatever your theme or page builder rendered on the server, not just the raw post content. Render-time fixes apply to that same output. What it does not see is anything added afterwards by JavaScript in the visitor's browser. Most Elementor, Divi and Beaver Builder content is rendered on the server and is checked normally, but a widget that builds itself in the browser is not. When a page looks like its content is assembled by JavaScript, the scan flags that page so a low issue count is not mistaken for a clean one.