ABLEWIDGET
AbleWidget — Accessibility Toolbar compatibility with REEID Translate
AbleWidget — Accessibility Toolbar compatibility with REEID Translate is being reviewed using official plugin documentation. Injects a WCAG 2.1 AA accessibility toolbar into the front-end via the standard wp_footer hook, ensuring compatibility with major themes and page builders like Elementor and Divi. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What AbleWidget — Accessibility Toolbar does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
AbleWidget — Accessibility Toolbar is documented in the Other category with 5 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How AbleWidget — Accessibility Toolbar compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Injects a WCAG 2.1 AA accessibility toolbar into the front-end via the standard wp_footer hook, ensuring compatibility with major themes and page builders like Elementor and Divi.
- Requires an active external AbleWidget subscription for functionality, verifying licenses automatically by domain name without requiring manual API key entry.
- Loads JavaScript asynchronously from ablewidget.com on every front-end page load when enabled, transmitting only the site domain for license verification and no visitor PII.
- Provides visitor-facing customization options including text size adjustment, high contrast/dark/light modes, dyslexia-friendly fonts, enlarged cursors, focus highlighting, and screen reader guidance.
- Offers administrative settings to toggle widget visibility, choose button positioning (bottom-right or bottom-left), and optionally display 'Powered by AbleWidget' attribution.
TRANSLATION BOUNDARY
AbleWidget — Accessibility Toolbar capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
AbleWidget — Accessibility Toolbar and REEID Translate FAQ.
What does AbleWidget — Accessibility Toolbar do?
AbleWidget — Accessibility Toolbar has 5 documented features listed in its official documentation. See the Plugin Information section for details.
Does AbleWidget — Accessibility Toolbar have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from AbleWidget — Accessibility Toolbar?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate AbleWidget — Accessibility Toolbar in a multilingual WordPress workflow.
REEID documents AbleWidget — Accessibility Toolbar functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.