Any plugin developers who want to help fix Elementor’s accessibility issues?

Bump…

Hi,

Thank you for your patience.

You are posing some interesting feature requests, and we really appreciate your feedback.

If you like, you can submit a Feature Request on Github, which is where we take feature requests.
You can submit them at https://github.com/elementor/elementor/issues/new/choose
which gives you the opportunity to follow the discussion about ideas you submit, and track development progress of any that get implemented.

You can learn more about how to submit requests at https://github.com/elementor/elementor/blob/master/.github/CONTRIBUTING.md”

Let us know if you need further assistance.

Regards,

Gil

I’ve already posted the issues there. Some were closed prematurely by Elementor or they never received a response.

Hi again,

If possible, please send me a link to the post you raised and I’ll look into why it was closed to the best of my abilities.

Thank you for your cooperation and patience.

Regards,

Gil

Here’s one that was closed: https://github.com/elementor/elementor/issues/11256.

Hi,

I would like to provide you with some updates regarding your query.

I’ll list these as follows.

Regarding your first two points in your original message, I can tell you that we are working on adding accessibility features in the upcoming patches. You can stay tuned for these updates on our changelog.

Regarding query number 3, you should be able to add tags on a page using our Tags Wrapper feature.

For number 4, if you can show us via a screencast how the main menus with sub-menus do not announce proper roles and values, we will take a further look at it.

Finally, I can see that in your GitHub feature request you only added a generalized version of what you described here, also not mentioning a portion of them.

Our developers suggest that you open a separate GitHub request for each of your suggestions and this way they will be properly addressed.

Regards,

Gil

As mentioned on GitHub, the Tags Wrapper Feature does not work as it should. For proper accessibility, there should only be one <main> tag for the entire page, which would basically consist of everything after <header> but before <footer>. The way the Tags Wrapper Feature currently works is that you have to set a <main> tag for each section, which isn’t the correct and accessible way of doing it.

I’ll get to you tomorrow regarding the menu part. What I can say now is that screen readers announce them as links and keyboard navigation supports that. For example, if you use the enter key on a keyboard to select the first menu item to expand it, another press of the enter key should close it, rather than engaging it as a link.

Additional information about the menu part:

The main menus with sub-menus do not announce proper role and values. These types of main menus or menu links need to announce that they have sub-menus or show more options in some manner as provided by the screen reader based on the type of coding used for menus with sub-menus (aria-haspopup and/or other methods). This covers their role and state. Currently, only their displayed label is announced.

These do use aria-expanded properly and that would be sufficient. However, the user cannot use these as toggles for showing and hiding their sub-menus. While the first use of the Enter key will expand them to show the sub-menus, the next use of the Enter key should only collapse them. Rather, it selects the main menu label as a link and loads that as a new page. These should not function as links and expand and collapse elements. The non-visual user’s expectation for expand and collapse elements is that they can be toggled and that is their only function. They will not expect them to also be a link in and of themselves.