After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793616 - GtkShortcutsWindow is lacking proper accessibility support
GtkShortcutsWindow is lacking proper accessibility support
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2018-02-19 20:55 UTC by Peter Vágner
Modified: 2018-05-02 19:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Peter Vágner 2018-02-19 20:55:29 UTC
By quickly skimming the docs GtkShortcutsWindow and related widgets do implement some ATK interfaces however I find it not very usefull for accessibility purposes.
From my point of view (I am a screen reader user) list of shortcuts displayed inside the GtkShortcutsWindow should be all reachable using the keyboard similar how we can browse an icons view. The only way on how I can discover these shortcuts is by using so called flat review feature of orca.
The keyboard shortcuts display might resemble a gried i.e. the individual shortcuts might be arranged left to right up to bottom I usually have to read the screen word by word to discover what's written there. Even with this I have to repeat more times in order to really comprehend which shortcut corresponds with which action.
To put it very gently I have to say this is not very intuitive.
I would welcome some kind of focus navigation within GtkShortcutsWindow.
If you need a hint where to see this in action, then activate Keyboard shortcuts in the top pannel menu when running Evince.
Comment 1 GNOME Infrastructure Team 2018-05-02 19:52:53 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/1034.