reala11y fixes code-level WCAG 2.2 AA issues at the source — skip links,
focus, language, labels, target-size — and pairs the work with AI alt-text
you control. It is not an overlay widget.
Automated tools, including ours, typically detect 30–40% of WCAG
failures by criteria. Full conformance requires manual review.
The honest case for code-level remediation
Overlay widgets didn't work.
Real fixes go in the HTML.
On April 21, 2025, the Federal Trade Commission entered a final order
against accessiBe — a $1,000,000 penalty plus a 20-year reporting
obligation — for claiming their overlay made websites WCAG compliant.
Courts have ruled the same. Yet most "accessibility plugins" still
ship overlays.
$1M
FTC penalty against accessiBe for overlay compliance claims — April 21, 2025
8,000+
ADA web accessibility lawsuits filed in 2024 — UsableNet
~30%
of WCAG criteria that any automated tool can detect — Deque, Accessible.org
How it works
Scan. Fix. Report.
01 — Scan
WCAG 2.2 rule library
We crawl your posts, pages, and theme output and flag issues across
22 WCAG rules — language attribute, alt text, color contrast,
heading hierarchy, target size (WCAG 2.2 new), link purpose,
and more. All free.
02 — Fix
Code-level remediation
Toggle on the fixes you want. Safe, code-level changes go into the
HTML itself — a skip link, focus outlines, a main landmark, and
target-size padding at render time; noopener attributes, duplicate
ids, and positive tabindex cleaned up in your content.
One-click rollback, always.
03 — Report
Generate a statement, not a guarantee
Produce a customizable accessibility statement and a VPAT starter.
We won't tell you you're "fully compliant." We will give you the
documentation you need to take to your legal team.
Works with the WordPress you already have
Theme- and builder-agnostic.
reala11y rewrites the rendered HTML at filter time — so it works wherever
your content is published. Tested across the most-installed builders and
themes; compatible with the rest by construction.
Block editors
Gutenberg
Classic editor
Page builders
Elementor
Bricks
Beaver Builder
Divi
Oxygen
WPBakery
Themes
Astra
Kadence
GeneratePress
Blocksy
OceanWP
Hello Elementor
WCAG guides
Built for every WCAG version.
Plain-language guides to WCAG 2.0, 2.1, 2.2, and the 3.0 outlook — what
each version covers, what changed, and which of our checks map to which
success criteria. Most sites should target WCAG 2.2 AA today.
reala11y launched in June 2026, so we won’t show you a wall of five-star
reviews we don’t have yet. Here’s the real case for trusting it — held to
the same honesty as our product claims.
Born from the accessiBe ruling
We built reala11y after the FTC’s $1,000,000 order against accessiBe for marketing overlay AI as WCAG compliance. We don’t make that claim — for them, or for us.
Honest about what automation does
Automated tooling, ours included, catches roughly 30–40% of WCAG issues by criteria. reala11y fixes those in your code at the source and flags the rest for human review.
Free, open, and GPL-licensed
The scanner and safe fixes are free on WordPress.org and GPL-licensed — no overlay, no lock-in. reala11y Pro adds agency multi-site management on top.
Reviews, when they’re real.
reala11y is brand new, so there are no reviews yet. Genuine WordPress.org
and customer reviews will appear here as they come in — never fabricated.
Free on WordPress.org — the full scanner, every safe auto-fix, and all
12 bring-your-own-key AI tools, on unlimited sites. reala11y Pro adds
cross-site management for agencies; AI is BYOK, so we never resell quota.
Free
$0
unlimited installs
Everything to find and fix accessibility issues at the source — on as many sites as you like, free on WordPress.org.
No automated tool can. reala11y identifies common WCAG 2.2 issues and applies code-level fixes. By criteria, automated tools detect approximately 30–40% of WCAG failures. The remainder requires manual review by an accessibility specialist.
How is this different from accessiBe or UserWay?
accessiBe and UserWay inject a JavaScript overlay that does not modify the underlying HTML. Screen readers continue to see the original, unfixed page. The FTC ordered accessiBe to pay $1 million on April 21, 2025 for marketing claims of automatic WCAG compliance. reala11y instead applies fixes to the actual HTML that browsers, screen readers, and crawlers see.
Do I have to use AI features?
No. Every AI feature is optional and bring-your-own-key: you add your own OpenAI, Anthropic, or Google Gemini API key, and your site talks to that provider directly. All 12 AI features are included in the free plugin; with no key configured, reala11y makes no AI calls. We never resell quota or store your API responses.
Is there a free version?
Yes — and it is the full product for a single site. The free plugin on WordPress.org includes the complete 22-rule WCAG 2.2 scanner, all 10 safe code-level auto-fixes, scheduled scans with email reports, and every BYOK AI feature, on unlimited sites. The one paid product is reala11y Pro (from $10/month), which adds cross-site management for agencies running a WordPress multisite network, in a Network / Growth / Team ladder.
How do I get support?
Payments go through Freemius (our merchant of record). Support is via email and the Freemius portal — we aim to respond within one business day.