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 531596 - Should provide keybindings for launching AT programs
Should provide keybindings for launching AT programs
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.23.x
Other All
: Normal enhancement
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 387973 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-05-05 18:11 UTC by Brian Cameron
Modified: 2021-06-09 16:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Brian Cameron 2008-05-05 18:11:03 UTC
GNOME should provide default keybindings for launching AT programs so that users
who need to run text-to-speech, or an on-screen-keyboard can easily launch such programs.  Users who need such programs cannot navigate the GUI, so providing a keybinding that launches AT programs would allow users to start needed AT programs so they can then navigate the GUI.

The following keybindings should be supported:

- Launch on-screen keyboard in normal mode
- Launch on-screen keyboard in dwell mode
- Launch text-to-speech
Comment 1 Jens Granseuer 2008-05-05 18:49:04 UTC
I view this more or less as a duplicate of bug 114796. While we could add some additional hard-coded bindings for this, I'd rather not do that.
Comment 2 Brian Cameron 2008-05-05 18:55:08 UTC
The difference between this bug and bug 114796 is that many users with disabilities simply cannot use the desktop without being able to first launch AT programs.  This need, I think, puts this class of keybindings in a unique category.  

Most other "arbitrary" keybindings are used to make life easier for the user, to quickly launch a program that they might want to launch frequently, for example. 
Such keybindings are nice-to-have, but not really needed to be able to use the desktop. 

It would be best if the keybindings used to launch AT programs were standardized across all GNOME desktops, rather than being arbitrary keybindings that each distro could configure differently.  Users with a11y needs should know that a specific keybinding will work regardless of which GNOME distro they are using.  Otherwise users with a11y needs will have difficulty switching between distros.
Especially users like blind users, who obviously can't get any hints from the GUI about what the differences might be.

Comment 3 Brian Cameron 2008-05-06 22:00:24 UTC
Note similar bug #387973, which George Kraft just made me aware of.  I'm not sure if it makes more sense to implement this in metacity as that bug suggests or in the keybinding prefernces, but wanted to highlight this similar bug.
Comment 4 Brian Cameron 2009-11-30 21:17:31 UTC
See related bug #599093.
Comment 5 Willie Walker 2009-11-30 21:25:34 UTC
See also http://live.gnome.org/Accessibility/PreferencesRework.  The approach outlined there builds upon the Universal Access Preferences dialog and focuses on the methods the user needs to interact with the machine (e.g., speech, magnification, braille, etc.) versus the actual technology (e.g., a screen reader).
Comment 6 Bastien Nocera 2011-02-09 15:30:26 UTC
Mass move to new component "Keyboard" where the keyboard shortcuts live in GNOME 3.
Comment 7 Bastien Nocera 2011-02-19 03:22:32 UTC
Most of those features are supported in GNOME 3. The only thing missing is a list of default keybindings.

What do other OSes use for those?
Comment 8 Bastien Nocera 2011-02-19 03:25:39 UTC
*** Bug 387973 has been marked as a duplicate of this bug. ***
Comment 9 Allan Day 2013-04-19 13:42:15 UTC
Agree that we should have shortcuts for a11y features. I'm pretty sure there has been some discussion about this already.

This page has some relevant information: https://live.gnome.org/GnomeOS/Design/Whiteboards/KeyboardShortcuts
Comment 10 André Klapper 2021-06-09 16:01:27 UTC
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 enhancement request ticket at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.