GNOME Bugzilla – Bug 745393
World clocks buttons seem not accessible in the calendar/notication area
Last modified: 2021-07-05 14:29:55 UTC
Navigating the new notication area with the screen reader on, the world clock buttons are not read correctly, they are read simply as "Push Button"
That's basically because there was no obvious choice for what the accessible name should be - "World Clocks" isn't overly helpful, while reading the full list gets exhaustive as locations are added. Any guidance here would be greatly appreciated ...
(In reply to Florian Müllner from comment #1) > That's basically because there was no obvious choice for what the accessible > name should be - "World Clocks" isn't overly helpful, while reading the full > list gets exhaustive as locations are added. > Any guidance here would be greatly appreciated ... Just tested, thanks for pointing the bug. The problem here is that there is just one element focusable. I guess that that makes sense from the action-user pov, as there is just one action possible: open gnome-clocks. But from the accessible/keyboard navigation pov, I think that it would be better each row of the list being navigable. In that scenario "World Clocks" would be the accessible name of the container area, and the accessible name for each row would be the city+hour. PS: doing this tests I also found several keyboard navigation bugs on gnome-clocks (bug 745444, bug 745445, bug 745446, bug 745447), and just doing a skimming. So even if this bug get solved, the user would be redirected to a non-accessible application.
(In reply to Alejandro Piñeiro Iglesias (IRC: infapi00) from comment #2) > The problem here is that there is just one element focusable. I guess that > that makes sense from the action-user pov, as there is just one action > possible: open gnome-clocks. But from the accessible/keyboard navigation > pov, I think that it would be better each row of the list being navigable. IMHO it's even trickier, and the current behavior is correct for a11y/keynav as well except for the screen reader/orca case. It also doesn't help that we don't actually have rows we could focus, but cells in a grid :-( So not sure what to do - short-term it doesn't look too urgent, given the Clocks issues you pointed out. So maybe just set the button's label_actor to the section title ("World Clocks" if some clocks have been configured, "Add world clock ..." otherwise) and leave the bug open for a better long-term option?
Created attachment 298488 [details] [review] dateMenu: Set label_actor for WorldClock button Ideally we would allow navigating into the button in the screen reader case, so the configured clocks are read out properly. However we can still do better than nothing short-term by pointing to the section header as the button's label_actor.
(In reply to Florian Müllner from comment #3) > (In reply to Alejandro Piñeiro Iglesias (IRC: infapi00) from comment #2) > > The problem here is that there is just one element focusable. I guess that > > that makes sense from the action-user pov, as there is just one action > > possible: open gnome-clocks. But from the accessible/keyboard navigation > > pov, I think that it would be better each row of the list being navigable. > > IMHO it's even trickier, and the current behavior is correct for a11y/keynav > as well except for the screen reader/orca case. It also doesn't help that we > don't actually have rows we could focus, but cells in a grid :-( Just a question, are those cells focusable? > So not sure what to do - short-term it doesn't look too urgent, given the > Clocks issues you pointed out. So maybe just set the button's label_actor to > the section title ("World Clocks" if some clocks have been configured, "Add > world clock ..." otherwise) and leave the bug open for a better long-term > option? As the lesser, and if those cells are not focusable, yes, probably this is the lesser short-term evil.
(In reply to Alejandro Piñeiro Iglesias (IRC: infapi00) from comment #5) > Just a question, are those cells focusable? No, and even if they were, they were still inaccessible by keynav as the button they are in would take the focus itself. > As the lesser, and if those cells are not focusable, yes, probably this is > the lesser short-term evil. OK, doing that for now - if we don't want to break pointer use, we'll have to do something custom there to keep the button, but allow navigating inside when insisting hard enough ...
Comment on attachment 298488 [details] [review] dateMenu: Set label_actor for WorldClock button Attachment 298488 [details] pushed as bb2d7f7 - dateMenu: Set label_actor for WorldClock button
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.