GNOME Bugzilla – Bug 731953
a11y: Lack of good keyboard shortcuts
Last modified: 2016-09-20 08:15:55 UTC
Hello, I had the following issues when I just unplugged my mouse: * F1 for help does not work * I don't know any way to access the about dialog * Selecting a VM is painful. Only way I found: 1. Navigate to the button which activates the selection mode via TAB key 2. Navigate through the VMs via TAB key 3. Select the ones you want with space * Making favorites is only possible via TAB key because there's only a symbol Note on that: the new design by jimmac (https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/boxes/wires/multi-window.png) already solves this since there's a text there. * Starting a VM is painful. Only possible via TAB key. In addition sometimes you don't even see where your tab focus is, seems a bit heisenbuggish. * I found no possibility to exit a running VM, fullscreen it or go to the settings (as long as it running) * Opening the search bar in the collections view seems only possible via TAB navigation. * "Enter URL" and "Select a file" in the wizard should have mnemonics, at the moment you need arrow keys or TAB * Properties is bad: no mnemonics at all! We should have mnemonics for the force shutdown button, the page titles and for all labels for options so the user can access options fast * Somehow it's not possible to escape the properties with Alt+Left. This was theoretically introduced by [0] but does not work on git master anymore for me. For more info about a11y things read [1], its a good article. A bug report about some orca experience may follow. [0] https://git.gnome.org/browse/gnome-boxes/commit/?id=750851147f96d2b9ebc716cf12667cbc35b3bbd9 [1] http://mairin.wordpress.com/2010/02/23/painless-accessibility-tips-for-gnome-designers-and-developers/
Sounds like a bunch of (some unrelated even) bugs put into one. Can we divide this please? One bug for each issue?
(In reply to comment #1) > Sounds like a bunch of (some unrelated even) bugs put into one. Can we divide > this please? One bug for each issue? Actually none of them is unrelated to the main issue so feel free to keep this open as a meta-bug for all individual bugs. Thanks for doing this testing btw!
Removing the already fixed one from 'See also' and moving the two this depends on to dependency list.
(In reply to comment #2) > (In reply to comment #1) > > Sounds like a bunch of (some unrelated even) bugs put into one. Can we divide > > this please? One bug for each issue? > > Actually none of them is unrelated to the main issue so feel free to keep this > open as a meta-bug for all individual bugs. > > Thanks for doing this testing btw! Yes, that was my intention. I'll file the single bugs soon blocking this.
Opening the search mode via Ctrl+F could be interesting too.
(In reply to comment #5) > Opening the search mode via Ctrl+F could be interesting too. I don't see how that easier than just starting to type.
(In reply to comment #6) > (In reply to comment #5) > > Opening the search mode via Ctrl+F could be interesting too. > > I don't see how that easier than just starting to type. Its not easier. But Ctrl + F ist just the default shortcut for searching. And if I'm a new user I am accustomed to this shortcut and I'm irritated if the searchbar doesnt show up and I'll throw Boxes away not knowing that I can just type. You could argue we don't need the search button at all because you can just type, which is easier.
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > Opening the search mode via Ctrl+F could be interesting too. > > > > I don't see how that easier than just starting to type. > > Its not easier. But Ctrl + F ist just the default shortcut for searching. And > if I'm a new user I am accustomed to this shortcut and I'm irritated if the > searchbar doesnt show up and I'll throw Boxes away not knowing that I can just > type. > > You could argue we don't need the search button at all because you can just > type, which is easier. Yes, the button is there already so nobody is throwing away Boxes just cause its missing a shortcut that is not essential. Also 'start typing to search' seems to be the new way in all apps. Having said all that, I didn't mean that we shouldn't add CTRL+F but was just pointing out that we already have an easier way.
(In reply to comment #8) > Yes, the button is there already so nobody is throwing away Boxes just cause > its missing a shortcut that is not essential. Also 'start typing to search' > seems to be the new way in all apps. It was rather an rhetorical exagerration. > Having said all that, I didn't mean that we shouldn't add CTRL+F but was just > pointing out that we already have an easier way. Good. But it goes into an own bug, you have to be patient for a few minutes longer.
All dependent bugs fixed!!!
Awesome! :) /me goes searching for more a11y bugs ... ehm improvement options in Boxes. Filing a few bugs :)