TEXT TO SPEECH TTS ACCESSIBILITY
Text To Speech TTS Accessibility translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Text To Speech TTS Accessibility does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Adds a text-to-speech audio player to selected WordPress post types automatically after installation/activation (free version).
- Free version generates speech using the browser’s built-in `speechSynthesis`/SpeechSynthesis API (no account/API key/registration claimed for free).
- Provides a shortcode-based integration (`[atlasvoice]` and related attributes) to place/configure the audio player and optionally specify language/voice and custom button labels/text to read.
- Includes an analytics dashboard that tracks visitor interactions with the audio content (e.g., play/pause/engagement metrics are claimed for the free version; advanced analytics are claimed for Pro).
- Supports optional opt-in telemetry (“AtlasAiDev Tracker”) that sends plugin/WordPress/PHP versions, site language, enabled features, site name/URL, admin email, and the site’s outbound public IP; explicitly states no visitor/listener data is sent and that it is off by default and revocable via an option.
- Optionally performs listener geolocation lookups for analytics when enabled (requires Analytics on), resolving a listener’s public IP to location via `icanhazip.com`, `ip-api.com`, and `ipinfo.io`; explicitly states only the listener’s IP is sent and that it is opt-in/off by default.
- On activation and when the site language changes, downloads translation `.mo` files on demand from a GitHub repository (sends only the WordPress locale code such as `es_ES`), skipping downloads if the `.mo` already exists.
- Pro supports server-side TTS via third-party providers (Google Cloud TTS, OpenAI/ChatGPT TTS, ElevenLabs) and can generate downloadable MP3 files; also claims REST API support (`tta_pro/v1`) and bulk MP3 generation from the WordPress posts list.
Distinctive features
Adds a text-to-speech audio player to selected WordPress post types automatically after installation/activation (free version). Free version generates speech using the browser’s built-in `speechSynthesis`/SpeechSynthesis API (no account/API key/registration claimed for free). Provides a shortcode-based integration (`[atlasvoice]` and related attributes) to place/configure the audio player and optionally specify language/voice and custom button labels/text to read. Includes an analytics dashboard that tracks visitor interactions with the audio content (e.g., play/pause/engagement metrics are claimed for the free version; advanced analytics are claimed for Pro). Supports optional opt-in telemetry (“AtlasAiDev Tracker”) that sends plugin/WordPress/PHP versions, site language, enabled features, site name/URL, admin email, and the site’s outbound public IP; explicitly states no visitor/listener data is sent and that it is off by default and revocable via an option. Optionally performs listener geolocation lookups for analytics when enabled (requires Analytics on), resolving a listener’s public IP to location via `icanhazip.com`, `ip-api.com`, and `ipinfo.io`; explicitly states only the listener’s IP is sent and that it is opt-in/off by default. On activation and when the site language changes, downloads translation `.mo` files on demand from a GitHub repository (sends only the WordPress locale code such as `es_ES`), skipping downloads if the `.mo` already exists. Pro supports server-side TTS via third-party providers (Google Cloud TTS, OpenAI/ChatGPT TTS, ElevenLabs) and can generate downloadable MP3 files; also claims REST API support (`tta_pro/v1`) and bulk MP3 generation from the WordPress posts list.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Text To Speech TTS Accessibility does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Text To Speech TTS Accessibility and REEID Translate FAQ.
Does the current evidence establish translation scope for Text To Speech TTS Accessibility?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.