GNOME Bugzilla – Bug 706622
Button for "selection mode" in the interface have no accessibility name
Last modified: 2016-03-31 13:22:07 UTC
Hi, I m blind. If i Tab in the interface of boxes to the button with selection mode the button have no accessibility name. orca can only say button here. reproduce: enable orca open boxes and tab to the button "select mode" to select virtal machines. orca only announce "button" in german "druckknopf" what i exept in gnome-documents it says if i tab to the button "objekte auswählen" in german, i think "select objects" in english i exapt that in boxes the button have this name for orca.
its also not possible to press the select "object button" with space
I believe this is a symptom of clutter-gtk breaking accessibility support (i-e bug#686622). I think it should actually be duplicate instead. I'm really sorry that Boxes is unusable for you but a11y is far from my area of expertise so unless someone tells me exactly what needs to be done to fix bug#686622, I can't help much. :( BTW, Can you do other stuff through a11y: create and launch boxes, going back to collection/main view from a box display view and editing properties of a box etc? *** This bug has been marked as a duplicate of bug 686622 ***
So its realy hard to navigate in boxes with keyboard, because not all elements can navigate with Tab. (In reply to comment #2) > I believe this is a symptom of clutter-gtk breaking accessibility support (i-e > bug#686622). I think it should actually be duplicate instead. > > I'm really sorry that Boxes is unusable for you but a11y is far from my area of > expertise so unless someone tells me exactly what needs to be done to fix > bug#686622, I can't help much. :( > > BTW, Can you do other stuff through a11y: create and launch boxes, going back > to collection/main view from a box display view and editing properties of a box > etc? Yes i can. But its realy hard to navigate in boxes with keyboard overall, because not all elements can navigate with Tab (sometimes i have to arrow arround, but this is hard to blind users because they dont know where to arrow arround and in what directions). I gnome-documents you can navigate with tab on every button/element. in boxes not. I played a little arround wiht it, i found more places with no accessibility labels.(for example the propperys of the virtal machine). I dont think this is an duplicate of bug#686622.
so what i mean are rather 3 different bugs. (sorry, previously it wasnt clear by myself what the different problems are). but now i see 3 problems in accessiblity: 1. keyboardnavigation is hard (here i nave no bug reported for) 2. the lag of accessible names of many controls (not only the "select mode" button. So this bug should be renamed to "give controls in GUI an accessibility name" 3. you cant select items (boxes) in selection mode with keyboad bug#706623. this in refer to 1. in most case are checkboxes can selected with space. if i press space (to mark an virtual machine) in boxes the search window opens. anyway boxes is an really cool app :). it would be cool if it would be more accessible.
(In reply to comment #4) > so what i mean are rather 3 different bugs. (sorry, previously it wasnt clear > by myself what the different problems are). > but now i see 3 problems in accessiblity: > 1. keyboardnavigation is hard (here i nave no bug reported for) > 2. the lag of accessible names of many controls (not only the "select mode" > button. So this bug should be renamed to "give controls in GUI an accessibility > name" Thing is that we don't set any a11y names on any controls but since you see names for some controls and for some you don't, I'm believe that at least this one is symptom of bug#686622. Hence a duplicate. For separate issues, lets have separate bugs. You already filed two, if you can file one for issue#1 above as well with some details, I'll do my best to fix these (bug#706623 and the new one) as soon as possible for me. bug#686622 is unfortunately not really easily fixable for me. :( > 3. you cant select items (boxes) in selection mode with keyboad bug#706623. > this in refer to 1. in most case are checkboxes can selected with space. if i > press space (to mark an virtual machine) in boxes the search window opens. > > anyway boxes is an really cool app :). it would be cool if it would be more > accessible. Thanks and I'd really love to make it as accessible as possible, just wish there was some a11y expert that could help us out. Also thanks for informing that you can already use many of the essentials as I was under the impression that Boxes is a complete failure in a11y support due to bug#686622.
Ah i understand. thanks alot for you ears :). The "New" "cancel" and "continue" buttons are spoken too. this buttons are in the same area/headerbar like the "select mode" button. why does it work hiere?
(In reply to comment #6) > Ah i understand. thanks alot for you ears :). > The "New" "cancel" and "continue" buttons are spoken too. this buttons are in > the same area/headerbar like the "select mode" button. why does it work hiere? Oh my, it seems that I totally misunderstood you even though you wrote it pretty clearly. :( You are talking about the button to enter the selection mode and I thought you are talking about controls presented when you enter the selection mode. While I look at the actual issue now, could you please tell me if buttons presented during the selection-mode are correctly spoken? Sorry, orca doesn't seem to be working on my machine.
Created attachment 253172 [details] [review] topbar: Set labels on topbar buttons These labels are not visible but they are needed for screen readers so blind people are able to tell what these buttons are.
(In reply to comment #8) > Created an attachment (id=253172) [details] [review] > topbar: Set labels on topbar buttons > > These labels are not visible but they are needed for screen readers so > blind people are able to tell what these buttons are. As I said, Orca is not working here so if somebody can test this patch, that would be very nice.
Created attachment 253196 [details] [review] topbar: Set a11y labels on topbar buttons Turns out that for buttons w/o labels, we need to explicitly set the a11y labels. Thanks to Joanmarie Diggs for helping with this.
Just tried this with Orca. Orca is presenting the newly-named buttons as I arrow to them. Thanks Zeeshan!!
Attachment 253196 [details] pushed as 2a76776 - topbar: Set a11y labels on topbar buttons
Yay :) thx alot!