TET ACCESSIBILITY FOR WOOCOMMERCE
TET Accessibility for WooCommerce translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what TET Accessibility for WooCommerce 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
- Automated accessibility scanning focused on WooCommerce buying-flow pages (shop archive, product, cart, checkout, account) by fetching server-rendered HTML as a visitor would.
- Issue detection for accessibility markup problems in those pages, including missing/invalid alt text for product images, unlabeled form fields (including placeholder-only labels), missing autocomplete attributes on checkout fields, missing/incorrect heading structure (including missing h1), missing page language, duplicate element ids, and table header omissions in cart/order tables.
- Detection of accessibility issues related to interactive elements and navigation, including icon-only links/buttons without accessible names, link text that is not meaningful out of context (e.g., “read more”), and add-to-cart buttons/controls that do not announce appropriately.
- Severity breakdown and issue management workflow, including a dismissal log that records who dismissed what, when, and why, with persistence across rescans.
- Export capability: CSV export of open and dismissed issues with WCAG references for evidence handover or internal review.
Distinctive features
Automated accessibility scanning focused on WooCommerce buying-flow pages (shop archive, product, cart, checkout, account) by fetching server-rendered HTML as a visitor would. Issue detection for accessibility markup problems in those pages, including missing/invalid alt text for product images, unlabeled form fields (including placeholder-only labels), missing autocomplete attributes on checkout fields, missing/incorrect heading structure (including missing h1), missing page language, duplicate element ids, and table header omissions in cart/order tables. Detection of accessibility issues related to interactive elements and navigation, including icon-only links/buttons without accessible names, link text that is not meaningful out of context (e.g., “read more”), and add-to-cart buttons/controls that do not announce appropriately. Severity breakdown and issue management workflow, including a dismissal log that records who dismissed what, when, and why, with persistence across rescans. Export capability: CSV export of open and dismissed issues with WCAG references for evidence handover or internal review. Optional AI “Suggest a fix” capability that connects to the TET Accessibility API only when the user presses the button, sending the rule/WCAG reference, issue description, HTML snippet, page type, site locale, site address, and an API key; the plugin states it does not send customer/order/post/user data or issue/page content unless that button is used.
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 TET Accessibility for WooCommerce 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
TET Accessibility for WooCommerce and REEID Translate FAQ.
Does the current evidence establish translation scope for TET Accessibility for WooCommerce?
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.