d2itechnology

D2i Accessibility Toolkit injects a floating accessibility panel into the front-end of any WordPress site. Visitors can activate assistive adjustments in a single click without needing to change their browser or operating system settings.
<blockquote>
Important notice: This plugin helps users customise their browsing experience. It does not automatically make your website fully compliant with WCAG, ADA, Section 508, or EN 301 549. Website owners remain responsible for ensuring their content (semantic HTML, image alt text, captions, heading structure, and color contrast in their own designs) meets applicable standards.
</blockquote>
<h4>Features</h4>
<ul>
<li>Contrast modes — Dark, Light, High Contrast (cycle through)</li>
<li>Highlight Links — high-visibility outlines and backgrounds on all links</li>
<li>Bigger Text — 100 % → 120 % → 140 % → 160 % → 180 % → 200 % (rem-based, reflows correctly)</li>
<li>Text Spacing — applies WCAG 1.4.12 exact values (line-height 1.5, letter-spacing 0.12 em, word-spacing 0.16 em, paragraph spacing 2 em)</li>
<li>Pause Animations — stops CSS animations/transitions; pauses <code><video autoplay></code>; respects <code>prefers-reduced-motion</code> automatically</li>
<li>Hide Images — hides img/picture/SVG; injects alt text as visible text nodes</li>
<li>Dyslexia Friendly — applies OpenDyslexic font (bundled locally, no CDN), increases line-height and letter-spacing</li>
<li>Big Cursor — 64 px white or black cursor SVG, locally bundled</li>
<li>Line Height — Default → 1.5 → 1.75 → 2.0 → 2.5</li>
<li>Text Alignment — Default → Left → Centre → Right (justify excluded per WCAG 1.4.8)</li>
<li>Reset All — one click restores defaults, clears LocalStorage</li>
</ul>
<h4>Compliance support</h4>
The widget provides user-facing adjustments that support meeting:
<ul>
<li>WCAG 2.1 Level AA (all applicable SCs)</li>
<li>WCAG 2.2 new SCs (2.4.11 Focus Not Obscured, 2.5.8 Target Size ≥ 44 × 44 px, 3.2.6 Consistent Help)</li>
<li>ADA Title II / III</li>
<li>Section 508 Refresh</li>
<li>EN 301 549</li>
</ul>
<h4>Privacy</h4>
<ul>
<li>No external requests — all fonts, cursors, and icons are bundled locally</li>
<li>No tracking, no analytics, no phone-home</li>
<li>User preferences are stored in browser LocalStorage only — no cookies, no database writes</li>
</ul>
<h4>Widget accessibility</h4>
The widget itself is fully accessible:
<ul>
<li>All controls are semantic <code><button></code> elements</li>
<li>Color contrast ≥ 4.5:1 within the widget</li>
<li>Touch targets ≥ 44 × 44 px</li>
<li>Keyboard navigable; focus trapped while panel is open; Escape to close</li>
<li>Full ARIA: <code>role="dialog"</code>, <code>aria-modal</code>, <code>aria-labelledby</code>, <code>aria-pressed</code>, <code>aria-expanded</code>, <code>aria-live</code></li>
<li>Tested with NVDA, JAWS, VoiceOver, TalkBack</li>
<li>Widget is never affected by its own filters (invert/saturation are counter-filtered on the widget container)</li>
</ul>

D2i Accessibility Toolkit

Floating accessibility widget with one-click WCAG 2.1/2.2, ADA, Section 508 & EN 301 549 adjustments. Free, no upsells, no external requests..

netopsae

AudioEye’s patented technology tests for over 400 accessibility and compliance issues, and fixes many of them automatically, reducing the time to make content accessible.
You will get your first AudioEye Accessibility Score the moment you install AudioEye on your site. From then on, AudioEye monitors your site for new issues with every site visitor, detecting and fixing hundreds of errors, while also providing you with a reporting dashboard that identifies what we cannot fix and needs your attention.
Technology can’t do it alone. With advanced plans, AudioEye has a team of certified accessibility experts who can help you throughout your accessibility journey. For those issues that we cannot fix automatically, we show you what the issue is, and how to address it on your site. If a lawsuit occurs, AudioEye is here to support you every step of the way.
Note: Use of the AudioEye plugin requires an active subscription to an AudioEye Plan. See pricing <a href="https://www.audioeye.com/plans-and-pricing" rel="nofollow ugc">here</a>. A link to sign up for a new account is presented during the plugin activation process. To log into an existing AudioEye account, you will need to provide your AudioEye Site ID.
Script delivery (CDN): AudioEye loads the storefront script (<code>aem.js</code>) from <code>wsmcdn.audioeye.com</code> by default today. We are migrating to <code>wsv3cdn.audioeye-services.com</code>. New setups without a saved Site ID use the new host by default; sites that already had a Site ID saved before the CDN preference existed keep the legacy host until an administrator enables the new host under AudioEye → Script CDN (Advanced) after allowlisting the new URL in any Content Security Policy (<code>script-src</code>, etc.). On first run, the plugin includes an optional onboarding step that explains how to allowlist the new host in your CSP.
Features included in all AudioEye base plans:
<ul>
<li>Path to compliance with ADA, Sec 508, AODA & more, using WCAG 2.1 AA</li>
<li>AudioEye Trusted Certification​</li>
<li>Usability toolbar with 24/7 Helpdesk​</li>
<li>Suite of AI-Powered Tests & Fixes​</li>
<li>Access to Certified Accessibility Experts</li>
<li>Basic Legal Support & Warranty​</li>
</ul>
Features available in AudioEye custom plans:
<ul>
<li>Advanced Legal Support</li>
<li>Manual Remediations</li>
<li>Premium Support</li>
<li>Custom Training</li>
</ul>

Accessibility by AudioEye


Kind reminder that accessibility can't take shortcuts. It's like telling an online shop owner there is a widget that fixes all their UX issue. As a UX Designer, I can tell it's impossible. As an accessibility expert, I can tell this kind of solution only bring more complexity to the disable folks' experience.



In January 2025, the US Federal Trade Commission ordered [similar solution name] to pay $1 million (subject to a thirty day finalisation period) due to misrepresentation that its software could make any website compliant with WCAG.



Also, WCAG isn't necessarily what's needed in your country. (France is RGAA, Luxembourg is RAWeb, Europe is EN 301 549)Best is to stay informed, and don't install a magic wand that is more of a black box.


Missleading - Risks of lawsuits (says European Council)

AudioEye automatically finds and fixes common accessibility issues on your site. This plugin provides an easy way to install AudioEye’s accessibility  …

D2i Accessibility Toolkit vs Accessibility by AudioEye