New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 693449 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

Regression: Unnecessarily ChromeVox (Spoken Feedback) is reading all the Accessibility options name twice in OOBE screen.

Project Member Reported by jbanavatu@chromium.org, Feb 17 2017

Issue description

Chrome Version: 58.0.3011.0/9287.0.0 dev channel Samus, Link, Butterfly
OS: Chrome

What steps will reproduce the problem?
(1)Recover build via USB>>Go to Accessibility settings screen by clicking Accessibility button in welcome screen.
(2)Enable Chrome Vox (Spoken Feedback) option >> Now hit tab to cycle through the Accessibility settings options and observe.

Expected: ChromeVox spoken feedback should output accessibility option name  followed by Button pressed/not pressed depending on the state of the row.
Actual: Instead the spoken feedback is reading all the accessibility options name twice (i.e; it is reading as Accessibility option name followed by Button pressed/not pressed and again followed by accessibility option name)

This is regression issue as it working fine in 57.0.2987.54/9202.28.0 beta channel quawks.

Attaching screenshots for reference.
 
Actual .jpg
3.8 MB View Download
Expected.jpg
3.6 MB View Download
Labels: NewComponent-Accessibility-ChromeVox
Status: Fixed (was: Assigned)
This has been fixed in https://codereview.chromium.org/2718133004/ .
Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-58; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-58 label, otherwise remove Merge-TBD label. Thanks.
Labels: -Merge-TBD -NewComponent-Accessibility-ChromeVox
Removing merge tags as the fix is already in branch.
Status: Verified (was: Fixed)
verified on 58.0.3029.51

Sign in to add a comment