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

Issue 628505 link

Starred by 6 users

Issue metadata

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

Blocked on:
issue 629593



Sign in to add a comment

Regression: Spoken feedback doesn't work in 54.0.2796.4/8589.0.0 of spring and pit.

Project Member Reported by sc00335...@techmahindra.com, Jul 15 2016

Issue description

Version: 54.0.2796.4/8589.0.0 (Official Build) dev-channel daisy_spring,pit
OS: Chrome os

What steps will reproduce the problem?
(1) In OOBE screen click on Accessibility link and hit tab and navigate to any field to listen for spoken feedback

Expected: Should be able to hear spoken feedback.
Actual: Instead unable to hear any spoken feedback.

NOTE:
1. Even after signing in unable to listen any spoken feedback
2. Issue seen on 54.0.2796.4/8589.0.0 spring and pit. Not seen with same version on quawks.

This is a regression issue as it is working fine in 52.0.2743.75/8350.55.0 beta channel daisy_spring.

@dtseng: Please confirm the issue.
 

Comment 1 by ajha@chromium.org, Jul 15 2016

Cc: songsuk@chromium.org dhadd...@chromium.org
Reproducible on 54.0.2796.4/8589.0.0 (Official Build) dev-channel pit.
Labels: -ReleaseBlock-Beta ReleaseBlock-Dev
Issue is seen with web pages too. Unable to hear any spoken feedback on navigating to any page or section in Browser. Hence adding RB-Dev label

Comment 3 by dtseng@chromium.org, Jul 15 2016

Are you seeing the ChromeVox panel and ChromeVox indicators? Likely a tts issue if so.
Cc: pbath...@chromium.org kathrelk...@chromium.org
Looks like our autotest for this started failing on all ARM boards (daisy, peach, nyan, and veyron) between 54.0.2787.0 and 54.0.2790.0.
Hi David,

I checked on 54.0.2796.4/8589.0.0 pit device. We can see the Chromevox panel and indicator but not able to listen the spoken feedback.

PFA the logs from chrome://inspect
Cvoxlogs.txt
17.0 KB View Download
Cc: lpalmaro@chromium.org dmazz...@chromium.org

Comment 8 by dtseng@chromium.org, Jul 17 2016

Owner: dmazz...@chromium.org
Assigning to dmazzoni, who did the last tts push. Dominic can you take a look? I think we should rollback if there isn't a simple fix.
Labels: ReleaseBlock-Beta
Labels: -ReleaseBlock-Beta
I will roll back if that's the issue, but I don't understand why there'd be a regression between 54.0.2787.0 and 54.0.2790.0.

Let's look into what happened in that range.

The new TTS was merged back on June 15th (Landed in 8459.0.0), so if that was what broke it, I would have expected it to fail a while ago.

https://chromium-review.googlesource.com/#/c/346805/

Blockedon: 629593
Suspecting this is general NaCl breakage, tracking in  crbug.com/629593 

Just to confirm, was this repro on any other devices but ARM ones?
#15: no, ARM devices are the only ones with broken ChromeVox speech
Status: Fixed (was: Assigned)
 Bug 629593  has been marked as fixed, can you verify that speech works?


Status: Verified (was: Fixed)
checked on 54.0.2816.08/8667.0.0 on peach-pit and Minnie. The spoken feedback works fine.

Sign in to add a comment