WCAG-A accessibility issues

@eugenewhite Just checking in to see if the posted details makes sense – do you need anything further, or have questions regarding this issue?

There are some other WCAA issues identified by SiteImprove, that are being caused by Accordion blocks, in addition to the one noted, and are affecting our score…

One in particular being “Role with implied hidden content has keyboard focus”

Are you open to pull requests, and if so, can you please contact me with details on how to compile your code and submit changes?

We would really like to see these resolved, and it would benefit all your users.

Thanks in advance for getting in touch, one way or another, even if just to say “no, we won’t fix this.” – cheers!

Hello there! 

I’m sorry for such a delayed response. 

Please be informed that I escalated your request to our developers’ team for them to double-check everything and consider such improvement implementation in one of the next plugin releases. Thank you! 

We let you know if we receive some updates on this matter. 

Thank you very much!

We will be eagerly awaiting progress on this issue…

Hello there! 

In the meantime, we mark the topic as “Resolved”. 

But we let you know if we receive some updates on this matter from our devs. 

Hello, thanks, I eagerly await updates. This is not resolved, so marking it as such is not accurate. Changed status back to unresolved.

Hello, just checking in on this. This is in fact an accessibility issue that is still unresolved.

Have you attempted to use the Accordion block using only the keyboard?

You will find that the tab key will navigate to only the first heading, and then will move the focus to the ‘invisible’ li elements in the first tab, instead of allowing the end user to select and expand the second tab using the keyboard, which is not accessible.

• This reply was modified 9 months, 2 weeks ago by Earthman Media.
• This reply was modified 9 months, 2 weeks ago by Earthman Media.
• This reply was modified 9 months, 2 weeks ago by Earthman Media.

Hello there! 

Thank you for your response. 

First of all, I would like to inform you that we don’t position our Getwid plugin and its blocks as WCAG-compliant. So this issue that you’re referring to is not an issue but rather a feature request. As I mentioned previously, I escalated your request to our developers’ team for them to consider such an improvement implementation in one of the future plugin releases. So we let you know if we receive some updates on this matter. 

Thanks for escalating and submitting the feature request. It is a very small change that can make a huge difference, I really hope your developers can consider the less fortunate members of our society who have to access the internet using accessible technologies, and the organizations that support them in doing so, and make it a higher priority.

Hi Getwid folks, and anyone stumbling on this…

I’m not sure if this will improve our score in SiteImprove, but it at least makes the Accordions work using the keyboard:

Hopefully this helps your developers to inform a solution within the plugin, so it doesn’t need ‘patching’ after the fact:

https://gist.github.com/EarthmanWeb/db03416e2ca48769b61bfbda12e17135

Any movement here? Did the code I provided help inform some ideas?

Hello there! 

I’m sorry to disappoint you, but we haven’t received any updates from our developers on this matter yet. 

We have escalated all the information to them and will inform you as soon as we receive some news. Thank you!

Just wanted to report that the changes I implemented, *on top of* the Getwid Accordion block, in this gist here:

https://gist.githubusercontent.com/EarthmanWeb/db03416e2ca48769b61bfbda12e17135

Have successfully mitigated the Accessibility flags in SiteImprove that were affecting our overall score as a result of being able to tab through hidden content. They have also made the accordion much more user friendly to readers, in general, on both mobile and desktop, when the accordion has a lot of content in it.

Of course, it would be ideal if these changes were adopted into your plugin’s core codebase, as it’s always fragile to add-on to modify an existing component, especially in this manner

I would be happy to work with your team to help implement these changes, please feel free to contact me directly should you want some additional hands on the project.

Hello there!

Certainly! I will forward all the information to the person in charge, and we will contact you when we decide to progress in this direction. Thank you!