Issue 646144  has been merged into this issue.

Hi David,

I can't get ChromeVox to "say" anything. Under options, there are no voices listed, and there are some errors in the JavaScript debug window. Instead, it is making (what I would call) spacey sounds - bongs, swish in, swish out, etc.

When I ctrl-tab between tabs, it makes a sound, but it seems quite reasonable to me.

Can you help me duplicate this?

https://www.chromium.org/developers/accessibility/chromevox-on-desktop-linux

You'll need to follow the "Speech" section to place the binaries copied during a Chrome OS install to the expected location.
Thanks for looking into this.

Sorry, David, I'm guess I'm unable to duplicate this. I built a ChromeOS version, which does speak, but it behaves identically to my v54 install. I tried it with an assortment of security levels - none, secure, ev_secure, not secure. Feel free to be more specific if you think that will help.

A couple of comments:

- the v55 ChromeOS version sounds horrible compared to v54 Linux, but then the whole build is running slow for some reason.
- I'm still troubled by why the v55 Linux version fails to say anything. v54 works fine.

There was a recent regression caused by a change to pulse, which I reverted, that caused speech to entirely fail:
https://codereview.chromium.org/2322083003/
in case you've not synced in the past few days.

Other than that, ChromeVox can work around the issue if needed.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1f3da58367d69ec72b038fc6085ae49df0b4a496

commit 1f3da58367d69ec72b038fc6085ae49df0b4a496
Author: dtseng <dtseng@chromium.org>
Date: Fri Sep 16 19:13:57 2016

Use category flush for focus events.

At times, we receive multiple focus events. This is technically fine, but it can cause lots of queued up chatter.

In the linke to bug, we are reading a focus event from a previous tab. Ideally the focus event shouldn't be fired (as it once was not), but ChromeVox should be robust enough to not over speak in this case.

Note that in braille, this results in a "shuffling" effect where one focus event flashes briefly before the expected event comes through.

BUG= 646126 

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2331253002
Cr-Commit-Position: refs/heads/master@{#419240}

[modify] https://crrev.com/1f3da58367d69ec72b038fc6085ae49df0b4a496/chrome/browser/resources/chromeos/chromevox/cvox2/background/background.js
[modify] https://crrev.com/1f3da58367d69ec72b038fc6085ae49df0b4a496/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
[modify] https://crrev.com/1f3da58367d69ec72b038fc6085ae49df0b4a496/chrome/browser/resources/chromeos/chromevox/cvox2/background/i_search.js
[modify] https://crrev.com/1f3da58367d69ec72b038fc6085ae49df0b4a496/chrome/browser/resources/chromeos/chromevox/cvox2/background/keyboard_handler.js
[modify] https://crrev.com/1f3da58367d69ec72b038fc6085ae49df0b4a496/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js