AxesWeb

<p>AxesWeb Accessibility Solution adds an accessibility toolbar to your WordPress site to help users customize their reading experience, in line with WCAG 2.1 and 2.2 guidelines. The widget is lightweight, configurable from the settings page, and designed to be theme-agnostic.</p>
<h3>External services</h3>
<p>This plugin connects to the AxesWeb CDN to load the accessibility widget JavaScript. It is required to render the accessibility UI and features in the front‑end.</p>
<p>What data is sent and when:<br />
– When the widget is loaded, the browser requests the script file from the CDN. No personal data is sent by the plugin to AxesWeb. The plugin does not add cookies or tracking.<br />
– When the optional accessibility feedback form is enabled, submissions are sent to your WordPress site via admin-ajax.php using a nonce-protected action. Emails are dispatched by your site to the recipient you configure. No data is sent to AxesWeb for this feature.</p>
<p>Service provider: AxesWeb<br />
– Script URL pattern: <code>https://cdn.axesweb.com/widget/{version}/accessibility-widget.js</code><br />
– Terms of Service: https://www.axesweb.com/termini-di-servizio/<br />
– Privacy Policy: https://www.axesweb.com/privacy-policy/</p>
<p>Additionally, when you verify your API key from the plugin settings, the plugin makes a request to the AxesWeb verification API to validate your license.</p>
<p>What data is sent and when:<br />
– On verification: your site URL and the API key you enter are sent in a JSON request to the verification endpoint to confirm validity and activate features.<br />
– No periodic personal data transfers occur. A lightweight validity recheck may occur based on stored TTL to keep the activation status up to date.</p>
<p>Service provider: AxesWeb<br />
– Verification endpoint: https://www.axesweb.com/wp-json/axesweb/v1/key/verify<br />
– Terms of Service: https://www.axesweb.com/termini-di-servizio/<br />
– Privacy Policy: https://www.axesweb.com/privacy-policy/</p>
<h3>License</h3>
<p>This plugin is released under the GPL v2 or later.<br />
See <code>https://www.gnu.org/licenses/gpl-2.0.html</code>.</p>


AxesWeb Accessibility Solution


Despite the presence of many accessibility plugin, this is the real completely free plugin. And it works like charm. Thanks


the first free accessibility plugin

WCAG 2.1 and 2.2-ready accessibility toolbar for WordPress with a configurable, lightweight widget.

marioalmonte

<p>The AccessiTrans – ARIA Translator for WPML & Elementor plugin facilitates the translation of ARIA attributes in sites developed with Elementor and WPML, ensuring that accessibility information is available in all languages of your website.</p>
<h4>Key Features</h4>
<ul>
<li>Automatically detects and makes ARIA attributes available for translation</li>
<li>Fully integrated with WPML String Translation</li>
<li>Compatible with all Elementor elements and templates</li>
<li>Multiple capture methods to ensure comprehensive detection</li>
<li>Translation retry mechanism for failed translations</li>
<li>Force refresh function to clear all caches</li>
<li>Debug mode for troubleshooting</li>
<li>Performance optimization settings</li>
<li>Translation cache system for improved performance</li>
<li>Internationalization support</li>
</ul>
<h4>Compatible ARIA attributes</h4>
<p>The plugin allows you to translate the following attributes:</p>
<ul>
<li><code>aria-label</code>: To provide an accessible name for an element</li>
<li><code>aria-description</code>: To provide an accessible description</li>
<li><code>aria-roledescription</code>: To customize the role description of an element</li>
<li><code>aria-placeholder</code>: For placeholder text in input fields</li>
<li><code>aria-valuetext</code>: To provide textual representation of numeric values</li>
</ul>
<h4>Capture Methods</h4>
<p>The plugin offers several capture methods to ensure that all ARIA attributes are detected:</p>
<ol>
<li><strong>Full HTML Capture</strong>: Captures all HTML of the page (highly effective but may affect performance)</li>
<li><strong>Elementor Content Filter</strong>: Processes content generated by Elementor</li>
<li><strong>Elementor Template Processing</strong>: Processes Elementor template data</li>
<li><strong>Individual Element Processing</strong>: Processes each Elementor widget individually</li>
</ol>
<h4>Advanced Settings</h4>
<ul>
<li><strong>Retry Failed Translations</strong>: Automatically retries translations that failed on first attempt</li>
<li><strong>Debug Mode</strong>: Enables detailed event logging</li>
<li><strong>Admin-Only Capture</strong>: Limits resource-intensive capture methods to admin users</li>
<li><strong>Capture in Primary Language Only</strong>: Only captures strings when browsing in the default language</li>
</ul>
<h4>Compatibility</h4>
<p>Works with all types of Elementor content:</p>
<ul>
<li>Regular pages</li>
<li>Templates</li>
<li>Global sections</li>
<li>Headers and footers</li>
<li>Popups and other dynamic elements</li>
</ul>
<p><strong>Tested with:</strong><br />
* WordPress 6.8<br />
* Elementor 3.28.4<br />
* WPML Multilingual CMS 4.7.4<br />
* WPML String Translation 3.3.3</p>
<h4>Why this plugin matters for accessibility</h4>
<p>In multilingual websites, accessibility information should be available in all languages. ARIA attributes provide essential accessibility information that helps assistive technologies understand and navigate your website. By making these attributes translatable, you ensure that all users, regardless of language or ability, can access your content effectively.</p>
<h3>Usage Instructions</h3>
<h4>How to add ARIA attributes in Elementor</h4>
<ol>
<li>Edit any element in Elementor</li>
<li>Go to the “Advanced” tab</li>
<li>Find the “Custom Attributes” section</li>
<li>Add the ARIA attributes you want to translate</li>
</ol>
<h4>Compatible formats</h4>
<p>Elementor indicates: “Set custom attributes for the wrapper element. Each attribute in a separate line. Separate attribute key from the value using <code>|</code> character.”</p>
<p>You can add ARIA attributes in two ways:</p>
<p><strong>Basic format (one attribute per line):</strong><br />
    <code>aria-label|Text to translate</code></p>
<p><strong>Multiline format (multiple attributes):</strong><br />
    <code>aria-label|Text to translate<br />
aria-description|Another description</code></p>
<p>This will generate the corresponding HTML attributes in the frontend:<br />
    aria-label=”Text to translate” aria-description=”Another description”</p>
<h4>How to translate the attributes</h4>
<ol>
<li>Once you’ve added the attributes, save the page or template</li>
<li>Go to WPML <span aria-hidden="true" class="wp-exclude-emoji">→</span> String Translation</li>
<li>Filter by the “AccessiTrans ARIA Attributes” context</li>
<li>Translate the strings as you would with any other text in WPML</li>
</ol>
<h4>Best practices for optimal performance</h4>
<p>For the best experience and website performance, follow these recommendations:</p>
<ol>
<li>
<p><strong>Browse your site in the primary language only</strong> while generating strings for translation. This prevents registering duplicate strings.</p>
</li>
<li>
<p><strong>Use the Force Refresh function</strong> when translations aren’t appearing as expected.</p>
</li>
<li>
<p><strong>Disable capture methods after initial setup</strong>:</p>
<ul>
<li>Once you’ve captured all ARIA attributes for translation, we recommend disabling all capture methods</li>
<li>This improves site performance and prevents additional strings from being registered in WPML</li>
<li>Re-enable the capture methods temporarily when you make changes to your site that include new ARIA attributes</li>
</ul>
</li>
</ol>
<h4>Practical examples</h4>
<p><strong>For a menu button:</strong><br />
* Attribute: <code>aria-label|Open menu</code></p>
<p><strong>For a phone link:</strong><br />
* Attribute: <code>aria-label|Call customer service phone</code></p>
<p><strong>For an icon without text:</strong><br />
* Attribute: <code>aria-label|Send an email</code></p>
<p><strong>For a slider:</strong><br />
* Attribute: <code>aria-label|Image gallery</code><br />
* Attribute: <code>aria-description|Navigate through product images</code></p>
<h3>Author</h3>
<p>Developed by Mario Germán Almonte Moreno:</p>
<ul>
<li>Member of IAAP (International Association of Accessibility Professionals)</li>
<li>CPWA Certified (CPACC and WAS)</li>
<li>Professor in the Digital Accessibility Specialization Course (University of Lleida)</li>
<li>20 years of experience in digital and educational fields</li>
</ul>


AccessiTrans – ARIA Translator for WPML & Elementor

Translate ARIA attributes in Elementor using WPML, improving the accessibility of your multilingual website.

AxesWeb Accessibility Solution vs AccessiTrans – ARIA Translator for WPML & Elementor