marioalmonte

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.
<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>
The plugin allows you to translate the following attributes:
<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>
The plugin offers several capture methods to ensure that all ARIA attributes are detected:
<ol>
<li>Full HTML Capture: Captures all HTML of the page (highly effective but may affect performance)</li>
<li>Elementor Content Filter: Processes content generated by Elementor</li>
<li>Elementor Template Processing: Processes Elementor template data</li>
<li>Individual Element Processing: Processes each Elementor widget individually</li>
</ol>
<h4>Advanced Settings</h4>
<ul>
<li>Retry Failed Translations: Automatically retries translations that failed on first attempt</li>
<li>Debug Mode: Enables detailed event logging</li>
<li>Admin-Only Capture: Limits resource-intensive capture methods to admin users</li>
<li>Capture in Primary Language Only: Only captures strings when browsing in the default language</li>
</ul>
<h4>Compatibility</h4>
Works with all types of Elementor content:
<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>
Tested with: 
* WordPress 6.8 
* Elementor 3.28.4 
* WPML Multilingual CMS 4.7.4 
* WPML String Translation 3.3.3
<h4>Why this plugin matters for accessibility</h4>
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.
<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>
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.”
You can add ARIA attributes in two ways:
Basic format (one attribute per line): 
 <code>aria-label|Text to translate</code>
Multiline format (multiple attributes): 
 <code>aria-label|Text to translate 
aria-description|Another description</code>
This will generate the corresponding HTML attributes in the frontend: 
 aria-label=”Text to translate” aria-description=”Another description”
<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 → 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>
For the best experience and website performance, follow these recommendations:
<ol>
<li>
Browse your site in the primary language only while generating strings for translation. This prevents registering duplicate strings.
</li>
<li>
Use the Force Refresh function when translations aren’t appearing as expected.
</li>
<li>
Disable capture methods after initial setup:
<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>
For a menu button: 
* Attribute: <code>aria-label|Open menu</code>
For a phone link: 
* Attribute: <code>aria-label|Call customer service phone</code>
For an icon without text: 
* Attribute: <code>aria-label|Send an email</code>
For a slider: 
* Attribute: <code>aria-label|Image gallery</code> 
* Attribute: <code>aria-description|Navigate through product images</code>
<h3>Author</h3>
Developed by Mario Germán Almonte Moreno:
<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.

neilgee

This plugin adds SlickNav Responsive Mobile Menu functionality to WordPress.
SlickNav Responsive Menu has multi level menu support.
Cross browser Compatible.
Keyboard Accessible.
Degrades gracefully without JavaScript.
Creates ARIA compliant menu.
Option to add a search field.
Option to add a logo.
Internationalized.
Advanced Filter.
Combine multiple menus.
<h3>Usage</h3>
The settings are found via the dashboard Settings > SlickNav Menu
<ul>
<li>
Here you choose your Menu to be used as Mobile Menu – original has to already be on page
</li>
<li>
Maximum width for the menu to appear, default is 600px
</li>
<li>
Menu Label, MENU is default
</li>
<li>
Parent links, true or false, whether a parent link that has a submenu is clickable to a page
</li>
<li>
Show Child Links, false by default
</li>
<li>
Open/close Menu speed option
</li>
<li>
Fix Menu to Head, using position fixed to body tag
</li>
<li>
Option for branding logo opposite menu label – smaller works better such as 40px in height and up to 140px in width
</li>
<li>
Option to hide header with a ‘.site-header’ class when Slicknav Menu is visible
</li>
<li>
Option to add in a search field at the bottom of the menu
</li>
<li>
Search icon background color
</li>
<li>
Options to change the opening and closing symbols
</li>
<li>
Advanced filter to adjust Slicknav values – https://wpbeaches.com/slicknav-wordpress-filter-to-adjust-values/
Demo – http://wpbeaches.com (resize browser window to below 600px)
Please note that SlickNav jQuery plugin is the work of Josh Cope, he is not responsible for the working or support of this plugin.
</li>
</ul>

SlickNav Mobile Menu

Why is this not part of the Word press core.
Sure it is just JS and css, but it is so useful!

Menus should often be better built from the page structure, not created manually.
I see people asking for this kind of menu all the time. Good luck finding one that works as good as this one.

Thank you, thank you thank you.

Best of the best

This plugin adds the option to use the SlickNav Responsive Mobile Menu in place of a regular menu at a designated size.

AccessiTrans – ARIA Translator for WPML & Elementor vs SlickNav Mobile Menu