New issue
Advanced search Search tips

Issue 819917 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature
STS
Team-Accessibility



Sign in to add a comment

Select To Speak/ChromeVox - present warning when both enabled

Project Member Reported by leberly@chromium.org, Mar 8 2018

Issue description

Google Chrome	67.0.3363.0 (Official Build) canary (64-bit)
Firmware Version	Google_Samus.6300.276.0

Since it's not recommended to use both Select to Speak and ChromeVox together at the same time, if both are enabled for use, a warning should be presented in a dialog. popover, etc. to indicate that this is not recommended. 

Possible cases for a warning:

- In Accessibility Settings page, one is toggled on and the other becomes toggled on at the same time

- STS is enabled in Accessibility Settings and the ctrl + alt + s hotkey is pressed to start ChromeVox

- Administrator is configuring ChromeVox installation, recommend that both not be turned on by default 

Since there is not currently a key shortcut to turn on the STS feature itself, there wouldn't need to be a warning for ChromeVox being in use and keyboard shortcut for STS being invoked 
 
Components: -UI>Accessibility UI>Accessibility>ChromeVox

Comment 2 by katie@chromium.org, Mar 8 2018

Labels: STS

Comment 3 by katie@chromium.org, Mar 8 2018

Cc: lpalmaro@chromium.org
Another option is to automatically turn Chromevox off when STS is on, and vice versa -- similar to the way the fullscreen magnifier and docked magnifier interact in settings.

+lpalmaro, what do you think of only allowing one of STS or Chromevox to be on at a time?

Comment 4 by katie@chromium.org, Mar 9 2018

Cc: dtseng@chromium.org
Chromevox should announce a notice that STS is on when Chromevox is enabled.
"Consider disabling for better chromevox experience"
Chromevox should announce a notice that STS is on when Chromevox is

We should toggle off the other service. We definitely don't support running both as they both attempt to use Search.

Comment 6 by katydek@google.com, Mar 9 2018

The search key is more overloaded than I assumed. Chromevox and STS will fight over who gets the search events, leading to bad state.

What if:

Turning on Chromevox turns off STS and either:
1. disables the STS button, OR
2. when the user tries to enable STS, shows a dialog, "Are you sure you want to turn on STS"

Comment 7 by katie@chromium.org, Mar 9 2018

Plan:

Turning Chromevox on turns off STS, makes it impossible for the user to turn on STS, and pops up a notification letting the user know that STS has been disabled.

Turning Chromevox off re-enables the option for the user to turn on STS but doesn't restore state (restoring state is a P4)

Comment 8 by katie@chromium.org, Mar 19 2018

Components: UI>Accessibility>SelectToSpeak
Labels: MagnifierCrOS

Sign in to add a comment