ESMO ACCESSIBILITY SCANNER
Esmo Accessibility Scanner compatibility with REEID Translate
Esmo Accessibility Scanner compatibility with REEID Translate is being reviewed using official plugin documentation. Runs WCAG 2.0/2.1/2.2 Level A and AA checks using the bundled axe-core engine directly in the browser against rendered front-end pages. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Esmo Accessibility Scanner 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
Esmo Accessibility Scanner is documented in the Other category with 7 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 Esmo Accessibility Scanner 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
- Runs WCAG 2.0/2.1/2.2 Level A and AA checks using the bundled axe-core engine directly in the browser against rendered front-end pages.
- Supports full-site scans of posts, pages, public custom post types (including WooCommerce products), and optional archives via a hidden iframe loading as the logged-in administrator.
- Provides detailed issue reporting with severity levels, WCAG success criteria references, affected element HTML, and recommended fixes for each finding.
- Generates an accessibility score from 0 to 100 per scan and tracks progress over time with dashboard visualizations of issues by severity and category.
- Offers optional automatic frontend fixes applied via WordPress hooks, including skip links, keyboard focus visibility, underlined links, language attributes, and viewport adjustments.
- Enables export of scan results in CSV and JSON formats for external audit records or team collaboration.
- Operates without server-side dependencies such as Node.js or headless browsers, requiring only standard WordPress hosting and browser execution.
TRANSLATION BOUNDARY
Esmo Accessibility Scanner 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
Esmo Accessibility Scanner and REEID Translate FAQ.
What does Esmo Accessibility Scanner do?
Esmo Accessibility Scanner has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Esmo Accessibility Scanner 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 Esmo Accessibility Scanner?
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 Esmo Accessibility Scanner in a multilingual WordPress workflow.
REEID documents Esmo Accessibility Scanner 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.