New issue
Advanced search Search tips

Issue 916766 link

Starred by 2 users
Status: Assigned
Owner:
dmazz...@chromium.org
Cc:
phanindra.mandapaka@chromium.org
dtseng@chromium.org
lpalmaro@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

ChromeVox verbalizes entire keyboard when exploring by touch

Project Member Reported by akihiroota@chromium.org, Dec 19 
Chrome Version: 73.0.3644.0 (Developer Build)
OS: ChromeOS
Device: Acer tablet

What steps will reproduce the problem?
(1) Turn on ChromeVox, either by holding down both volume keys or via the accessibility settings.
(2) Open Chrome.
(3) Navigate to and select the omnibox.
(4) Explore virtual keyboard by touch.

Expected behavior:
ChromeVox should only verbalize keys on the keyboard.

Observed behavior:
When passing between keys, ChromeVox selects the entire virtual keyboard and verbalizes it: "1 q 2 w 3 e ... a s d f ... ".
Attached is a screenshot of the ChromeVox output.
Screenshot 2018-12-19 at 2.13.45 PM.png
206 KB View Download

Comment 1 by swarnasree.mukkala@chromium.org, Dec 20

Labels: Needs-Triage-M73

Comment 2 by phanindra.mandapaka@chromium.org, Dec 21

Cc: phanindra.mandapaka@chromium.org
Labels: Needs-Feedback Triaged-ET
Thanks for filing the issue...

Unable to reproduce the issue on reported chrome version 73.0.3644.0 using SurfacePro Windows 10. Attaching screen-cast for reference.
Steps: 
------
1. Launched reported chrome 
2. Enabled ChromeVox and opened chrome and selected the omnibox
3. Explored the virtual keyboard by touch.
As we have observed that the ChromeVox verbalizes the keys on the keyboard while touching

@Reporter: Could you please check the attached screen-cast and let us know if we missed anything from our end. Also confirm the issue is specific to Acer tablet.

Thanks.!
916766.mp4
3.2 MB View Download

Comment 3 by lprazdnik@chromium.org, Dec 27

Labels: OS-Chrome

Comment 4 by akihiroota@chromium.org, Jan 8 

Thank you for responding! 

I think this issue is touch-specific. On tablet devices, you can "explore by touch" by holding and dragging your finger around the screen; ChromeVox will announce whatever element is beneath your finger at that time. I took a look at the above screen-cast and it didn't look like the tester was exploring by touch. 

Also, the issue applies across all devices, as far as I can tell. I built ChromeVox on a Linux machine and got the same behavior. 

I hope this helps and please let me know if you still can't reproduce the incorrect behavior.

Thank you!
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 8

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by dtseng@chromium.org, Jan 14

Owner: dmazz...@chromium.org
Status: Assigned (was: Unconfirmed)
@dmazzoni, is this possibly due to your change to re-target hover events?
►

Sign in to add a comment