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 735700 - Automatically start the screen reader when opening the accessibility panel
Automatically start the screen reader when opening the accessibility panel
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Universal Access
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks: 735761
 
 
Reported: 2014-08-29 23:37 UTC by Elad Alfassa
Modified: 2021-06-09 16:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Elad Alfassa 2014-08-29 23:37:13 UTC
Windows starts the screen reader automatically when opening the accessibility panel in their "control panel". We should do it too.

This will allow us to remove the Orca desktop launcher easily, because people searching for "Screen Reader" (or "orca", after we add that keyword) would be presented with the universal access panel and an easy way to enable the screen reader.

This is related to bug #735671
Comment 1 Peter Vágner 2014-10-21 10:18:43 UTC
By expanding this philosophy should large font and / or zoom also be started when this is activated?
Screen reader users will not be able to navigate to this pannel without screen reader active so the most natural way for screen reader users to activate screen reader is by using its toggle shortcut key. By default this is alt+super+s .
On windows there is a single shortcut to start the settings along with the screen reader why it's is most likelly coupled there.
Comment 2 André Klapper 2021-06-09 16:10:22 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 bug report at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.