At the moment the visually hidden label for drop buttons is List additional actions. If you get it announced while going through a page it is fine and the context is apparent for a screen reader user. But if you navigate and assess a page via the rotor, for example in Voiceover for MacOS, it is a problem:
The problem is if the user is relying completely onto a functionality like the rotor in MacOS for navigating the page and making sense of things it is impossible to understand the context and purpose of the link. The user only gets List additional action button announced seven times in a row. Impossible to make an informed decision which List additional action button to pick. I suppose the according success criterion might be WCAG SC 2.4.4
For Voiceover on MacOS (the only screenreader i was able to test on and where i've noticed the issue in the first place)
1. Go to /admin/structure/types/manage/article/fields, /admin/structure/views/view/content, or /admin/content
2. active the screen reader cmd F5
3. activate the rotor ctrl option u
4. navigate with the left or right arrow button to the form controls menu
For NVDA there is a blog with a quick primer how to each the rotor functionality
I've brought the topic to yesterdays a11y office hour (2022-09-15). The attendees were Corbb O'Conner, Laura Flannery, @mgifford, @mherchel, @shaal and me. There was a consensus that the current state poses a problem to screen reader users. Corbb O'Conner who is the chair of the webmasters group for the National Federation of the Blind ( the NFB is using Drupal for all their affiliates) and also a screenreader user, recommended for one if possible to shorten List additional actionand then provide the context afterwards. Having List additional actions repeated each time is ok in that case. But it is important and mandatory to provide the context. So the content of the visually hidden span changes from
List additional actions
to something like either:
Additional actions, CKEditor 4 field
or even shorter
Actions, CKEditor 4 field
Active
11.0 🔥
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.