When ChromeVox (which provides spoken feedback on Chrome OS), gets used on a touch screen, Chrome provides touch exploration. Touch exploration changes touch events on the screen to hover rather than to press thereby allowing a blind user to explore the screen. This means a user won't accidentally trigger UI elements as they explore. As objects are touched, ChromeVox describes them via speech or braille.
This behavior is undesirable in very specific cases. One of them is when typing on a virtual keyboard. Chrome skips the above behavior when within the bounds of the vk and simply lets the touch event through as a touch press/release at an anchor point set by ChromeVox.
To further re-enforce this behavior, ChromeVox, in this change, will play a "earcon" (sound icon) when the user releases over the vk.
Bug: None Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I3e4c09fcafda2f418dcdd8f04a987de62be79e44 Reviewed-on: https://chromium-review.googlesource.com/630196 Commit-Queue: David Tseng
580f050 Add a earcon for touch typing.
ash/ash_touch_exploration_manager_chromeos.cc | 5 +++++
ash/ash_touch_exploration_manager_chromeos.h | 1 +
chrome/browser/browser_resources.grd | 1 +
.../chromeos/accessibility/accessibility_manager.cc | 2 ++
.../browser/resources/chromeos/sounds/touch_type.wav | Bin 0 -> 192668 bytes
chromeos/audio/chromeos_sounds.h | 1 +
ui/chromeos/touch_exploration_controller.cc | 1 +
ui/chromeos/touch_exploration_controller.h | 4 ++++
ui/chromeos/touch_exploration_controller_unittest.cc | 10 ++++++++++
9 files changed, 25 insertions(+)