New issue
Advanced search Search tips

Issue 864401 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 19
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Missing and incorrect key descriptions for ChromeVox

Project Member Reported by tranbao...@chromium.org, Jul 17

Issue description

Chrome Version: 69.0.3480.0 (Official Build) 32-bit
Chrome OS Version: 10842.0.0 (Official Build) dev-channel gru test
IME version: repo HEAD + new UI
System UI language: US English


Steps To Reproduce:
(1) Enable ChromeVox screen reader with US English voice.
(2) Trigger US English virtual keyboard to show.
(3) Drag finger over keys on the virtual keyboard.


Expected Result:
Names of all keys can be read aloud correctly by ChromeVox.


Actual Result:

- Non-a11y normal mode of the keyboard:

+ ChromeVox just says "button" without key names for: 
Left Shift, Right Shift, Enter, Backspace, Spacebar, Hide keyboard, Emoji, Handwriting, Floating, Settings, Audio

+ ChromeVox says incorrect names for:
Symbol, read as "one hundred twenty-three button" due to "?123" label.
Language Menu, read as "U-S button" due to "US" label.


- A11y compact mode of the keyboard:

+ ChromeVox just says "button" without key names for: 
Left Shift, Right Shift, Enter, Emoji, Left Arrow, Right Arrow, Handwriting, Floating, Settings, Audio

+ ChromeVox says incorrect names for:
Caps Lock, read as "OS button" or something.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always.


 
Description: Show this description
Similar issues with Handwriting mode of the US English keyboard:

+ ChromeVox just says "button" without key names for: 
Enter, Backspace, Spacebar, Hide keyboard, Emoji, Exit-Handwriting, Floating/Dock, Settings, Audio

+ ChromeVox says incorrect names for:
Symbol, read as "one hundred twenty-three button" due to "?123" label.
Language Menu, read as "U-S button" due to "US" label.

Status: Fixed (was: Started)
This has now been fixed in the IME. As it usually takes a while for the fix to land, please verify in about a week's time. Thanks.
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 20

Sign in to add a comment