Issue metadata
Sign in to add a comment
|
Chromevox: some text in the sign in screen is spoken more than once. |
||||||||||||||||||||||
Issue descriptionVersion:56.0.2915.0 What steps will reproduce the problem? (1)Sign out of existing account of Chromebook (2)Enable Chromevox next (3)Click on 'Add Person" What is the expected result? Cvox should not read any element more than once What happens instead? The spoken feedback reads " sign in, press the tab key to interact with input elements Please wait...Please wait... Please wait... Close Button Email or phone number edit text ,email or phone number edit text" In specific 'Please wait...' is spoken 3 times and 'Email or phone number edit text' is read 2 times Please use labels and text to provide additional information.
,
Mar 27 2017
,
Apr 13 2017
On some login screens, the problem is much worse than reported. For example, on the offline sign in screen, CV reads visible and invisible page contents, repeatedly, for 55 seconds. I made a recording of my Pixel on 59.0.3055.0 (canary): https://drive.google.com/a/google.com/file/d/0B2eQSuURIGXxMk9HSWNvMUdtVGM/view?usp=sharing And here's the same problem on the "Network not available" screen: https://drive.google.com/a/google.com/file/d/0B2eQSuURIGXxb1l6YWp6YmJHcG8/view?usp=sharing (this page is getting replaced soon, so don't bother fixing anything on it - Issue 689198 ). To access offline sign in: 1. Settings > Manage other users > turn off "Show usernames and photos on the sign-in screen" 2. Disable wifi 3. Log out, then the "Network not available" page should appear 4. Click "sign in as an existing user".
,
Apr 13 2017
This is a bug on the oobe side. The div containing the aria label "sign in, press tab to interact with input elements", is marked up as a live region (e.g. aria-live="plite"). So on load, ChromeVox reads the entire div. glevin@, want to fix this one? Basically, just remove the aria-live attribute.
,
Apr 13 2017
,
Apr 13 2017
Thanks for the info! I'll take a look at it.
,
Apr 21 2017
,
Apr 21 2017
,
Aug 7 2017
Still a problem as of 62.0.3166 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dmazz...@chromium.org
, Mar 6 2017