New issue
Advanced search Search tips

Issue 869880 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Aug 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

ChromeVox does not announce "is editing" after navigating to edit fields

Project Member Reported by leberly@chromium.org, Aug 1

Issue description

Google Chrome 69.0.3494.0 (Official Build) dev (64-bit), Firmware Version	Google_Eve. 9584.160.0

Steps to reproduce: 
# Flip convertible ChromeVox into tablet mode
# Turn on ChromeVox by holding both hardware volume keys for 5 seconds 
# Use linear navigation or explore by touch to put focus on the Omnibox
Expected: make clear to user that you must double tap to enter editing mode
Actual: no indication

# Double tab to enter editing mode
Expected: announces "is editing"
Actual: no announcement 

This can cause confusion around entering text. This does not reproduce if focus was placed into the edit field by default. For example, turning on ChromeVox on the login screen will place focus on the password field and will say is editing. However, if you linear navigate to other areas of the screen and back to the password field and double tap, it does not say is editing. 
 
Summary: ChromeVox does not announce "is editing" after navigating to edit fields (was: ChromeVox does not announce "is editing" in edit fields)
Description: Show this description
Labels: CVoxTouchTyping
Project Member

Comment 4 by bugdroid1@chromium.org, Aug 3

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3b0a1eddc750df9b14eb2fd2c99d613e4761b59b

commit 3b0a1eddc750df9b14eb2fd2c99d613e4761b59b
Author: David Tseng <dtseng@chromium.org>
Date: Fri Aug 03 23:19:41 2018

Refine editing hints in ChromeVox

During touch, we want to either announce 'is editing' is a text field is focused, or 'double tap to start editing' when a text field is in ChromeVox range, but not focused.

We want to do this only for touch because keyboard commands,e .g. search+right, will automatically try to focus the text field. Since ChromeVox preemptively reads the new element (and doesn't wait for the focus event on the text field), the output here would be incomplete until the focus event.

Fortunately, we only really need this announcement for touch.

Bug:  869880 
Test: manual
Change-Id: I0d25cb28ece2b1a95658108fb5d032a91b705064
Reviewed-on: https://chromium-review.googlesource.com/1162627
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#580696}
[modify] https://crrev.com/3b0a1eddc750df9b14eb2fd2c99d613e4761b59b/ash/accessibility/touch_exploration_controller.cc
[modify] https://crrev.com/3b0a1eddc750df9b14eb2fd2c99d613e4761b59b/chrome/browser/resources/chromeos/chromevox/cvox2/background/command_handler.js
[modify] https://crrev.com/3b0a1eddc750df9b14eb2fd2c99d613e4761b59b/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
[modify] https://crrev.com/3b0a1eddc750df9b14eb2fd2c99d613e4761b59b/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js
[modify] https://crrev.com/3b0a1eddc750df9b14eb2fd2c99d613e4761b59b/chrome/browser/resources/chromeos/chromevox/strings/chromevox_strings.grd

Labels: M69A11yTests
Status: Fixed (was: Available)
Labels: CVoxTouch

Sign in to add a comment