Community
Participate
Working Groups
Build Identifier: 0.3 The help command list (that is brought up by pressing Ctrl+Shift+L) cannot be read by a screen reader. So a user who needs a screen reader would be unable to read the contents of the popup. Reproducible: Always
I have fixed this bug in the following repository in the accessibility branch. https://github.com/max-li/orion.client.git
Hey Max, this time I not able to find the commit in https://github.com/max-li/orion.client/commits/accessibility
Here is the commit https://github.com/max-li/orion.client/commit/dd5c754551020c5c2ab13ea059ac5445d5844a58
I'm working in commands today so I can commit this. Thanks, Max!
(changing ownership back, somehow I fumbled those "set default" checkboxes)
Hi, Max. The commit looks reasonable but I'm still not sure how to verify it fixes the problem. From the navigator, if I invoke the dialog (using '?') and start pressing the tab key to visit various things on the page, I still never get to that popup. I guess I assumed I could observe the fix by traversing to the dialog (and then assuming a screenreader would get it right). (tested from the navigator because from the editor I could never keyboard navigate out of the editor anyway so I didn't know how to verify it on that page.)
I'm guessing based on the other fixes that you need a tab order in addition to a role.
By setting the aria-live property, the screen reader should automatically start reading the contents of the help box (and it does do that from my own testing). So the popup does not need to be in the tab order. (This works fine in the editor. JAWS has its own keybinding for ? so I can't actually bring the help up outside of the editor. I figure this will be dealt with in bug 349602.)
Thanks for the explanation... Merged the commit in because I've been messing around in these files. Could you retest as a sanity check that I didn't mess it up? Thanks!
(In reply to comment #9) > Thanks for the explanation... > Merged the commit in because I've been messing around in these files. > Could you retest as a sanity check that I didn't mess it up? Thanks! I've retested and everything looks good.