Accessibility
-
Hey! I had a question about accessibility and was wondering if you have a github page to track issues. Couldn’t find it.
I am working with clients who are blind and/or using assistive technology (aka screen readers) and accessibility consultants. While testing out various plugin options, they said an issue with yours is that you use “role=presentation” on the frontend (either in the wrong places or too much…?). I’m working to get more clarification from them to share with you.
I suspect that your plugin is probably one of the more accessible generally since it uses simple tables and your pop-over is a nice big modal that opens on click and not some finnicky little javascript hover. I also prefer it because of your use of regular posts, two checkboxes and a regular date picker. All these things lead me to believe that the admin sidebar will remain fairly accessible (will have them test out and let you know!)
Here are two things I found via a quick search:
How one post mentions role=presentation should be used (but confusing since it would hide the entire table from aria? not sure) https://www.emailonacid.com/blog/article/email-development/why-should-i-set-my-table-role-as-presentation/
Example of it failing tests: https://www.powermapper.com/tests/screen-readers/tables/table-role-presentation-layout-table/
interesting guide: https://blog.pope.tech/2023/08/22/beginners-guide-to-accessible-tables/
More in depth (it mentions a distinction between tables for data versus layout): https://www.w3.org/WAI/tutorials/tables/
Thanks!
You must be logged in to reply to this topic.
