wkh0000

<p>reala11y is a WordPress accessibility checker and scanner that helps your site move toward WCAG 2.2 AA conformance by scanning for common issues and applying safe, code-level fixes — skip links, focus outlines, language attributes, form labels, target-size, link purpose, and more. Unlike accessibility overlay widgets, reala11y modifies the underlying HTML so screen readers and keyboard users encounter the corrected page.</p>
<h4>What reala11y does</h4>
<ul>
<li>Scans posts and pages against a WCAG 2.2 rule library.</li>
<li>Applies safe, automated fixes at render time (per-rule on/off, one-click rollback).</li>
<li>Generates a customizable accessibility statement.</li>
<li>Suggests image alt text with your own AI key (OpenAI, Anthropic, or Google Gemini) — you review every suggestion before it is applied.</li>
</ul>
<h4>What reala11y does NOT do</h4>
<ul>
<li>It does not guarantee WCAG, ADA, EAA, or Section 508 compliance. Automated tools detect approximately 30–40% of WCAG failures by criteria. Full conformance requires human review.</li>
<li>It is not an overlay widget. The Federal Trade Commission’s April 21, 2025 order against accessiBe affirmed that overlay claims of automatic WCAG conformance are not supportable.</li>
</ul>
<h4>External services</h4>
<p>reala11y is self-contained and contacts third-party services only as described below, and only when the relevant feature is used.</p>
<ul>
<li>
<p>WordPress.org — used for plugin update checks, as for any plugin hosted here. No personal data is sent beyond the standard update request.</p>
</li>
<li>
<p>AI providers — OpenAI, Anthropic, and Google Gemini (optional, bring-your-own-key). The AI authoring features (for example, alt-text suggestions) stay off until you enter your own API key for a provider and run a feature. When you run a feature, reala11y uses your key to send that provider the input you selected — for example, the URL of an image or a block of your post’s text — together with a short instruction prompt. The response is shown to you for review and is never applied automatically. reala11y does not proxy or resell AI usage; the provider bills you directly. Remove a provider’s key to disable it.</p>
<ul>
<li>OpenAI — Terms: https://openai.com/policies/terms-of-use/ — Privacy: https://openai.com/policies/privacy-policy/</li>
<li>Anthropic — Terms: https://www.anthropic.com/legal/commercial-terms — Privacy: https://www.anthropic.com/legal/privacy</li>
<li>Google Gemini — Terms: https://ai.google.dev/gemini-api/terms — Privacy: https://policies.google.com/privacy</li>
</ul>
</li>
</ul>
<p>This free build does not bundle Freemius or any licensing or analytics service. See our privacy policy at https://reala11y.com/legal/privacy.</p>
<h4>Source code</h4>
<p>reala11y is open source (GPLv2 or later). The admin interface is written in React and TypeScript and bundled with Vite. The human-readable source for the compiled files in build/admin/ ships with the plugin under admin/src/. To rebuild it, run “npm install” and then “npm run build” in the plugin’s admin/ directory.</p>
<h4>Why reala11y</h4>
<ul>
<li>Code-level remediation, not an overlay widget.</li>
<li>WCAG 2.2 (including 2.5.8 Target Size and the focus criteria).</li>
<li>Bring-your-own AI key — no surprise quotas, no resold tokens.</li>
<li>Honest claims. We never tell you you’re “fully compliant.”</li>
</ul>
<h4>Links</h4>
<ul>
<li>Website and documentation: https://reala11y.com</li>
<li>How reala11y compares to overlay widgets: https://reala11y.com/vs/accessibe and https://reala11y.com/vs/userway</li>
<li>Our own accessibility statement: https://reala11y.com/accessibility-statement</li>
</ul>


reala11y — Accessibility Checker & WCAG Scanner

Accessibility checker for WordPress: scan for WCAG 2.2 issues, auto-fix them in the code, and add AI alt text. A real fix, not an overlay widget.

WebTechee

<p><strong>WebTechee AccessScan</strong> helps WordPress site owners and developers quickly identify common accessibility issues on their site.</p>
<p>The plugin performs an automated scan of your published content and highlights issues such as:</p>
<ul>
<li>Images missing <code>alt</code> attributes</li>
<li>Empty anchor links without accessible text</li>
</ul>
<p>The scan runs on demand from the WordPress admin and displays results instantly — no configuration required.</p>
<p>This lightweight, stateless scanner is designed for quick checks during development or content review.</p>
<p>⚠️ This plugin does not store scan data in the database and does not modify your content.</p>
<h3>How It Works</h3>
<ol>
<li>Go to <strong>AccessScan</strong> in the WordPress admin menu</li>
<li>Click <strong>Run Scan</strong></li>
<li>Review detected accessibility issues and affected HTML elements</li>
<li>Fix issues directly in your content or theme</li>
</ol>
<h3>Features</h3>
<ul>
<li>One-click accessibility scan</li>
<li>Detects common WCAG-related issues</li>
<li>Displays affected HTML elements for easier fixes</li>
<li>Lightweight and fast</li>
<li>No database tables</li>
<li>No scheduled tasks</li>
<li>No front-end scripts added</li>
</ul>
<h3>Free vs Pro</h3>
<p>This is the <strong>free version</strong> of WebTechee AccessScan.</p>
<p>The free version focuses on:<br />
* Instant scanning<br />
* Common accessibility checks<br />
* No data storage</p>
<p>A <strong>Pro version</strong> is planned with advanced features such as:<br />
* Scan history<br />
* Scheduled scans<br />
* Accessibility scoring<br />
* Exportable reports<br />
* Advanced issue detection</p>


WebTechee AccessScan

Run automated accessibility scans to detect common accessibility issues on your WordPress site.

reala11y — Accessibility Checker & WCAG Scanner vs WebTechee AccessScan