I forgot to mention that the Chromevox strangeness persisted after a power wash as well. This was one of the first things I tried.

Saw the same issue on a samus on 54.0.2822.0. I checked on couple of samus devices, but it was observed on only one of them. When i check the chrome://inspect logs, no log data was found. The chromevox shows as its enabled but it doesn't work.

Also experienced the same behavior with an HP Chromeboook running latest
canariy... I can update with model of that one if needed. Initial bug
report was made regarding Google Samus.

I updated Samus Canary and my ChromeVOx is shot.
Are there debugging logs that could help determine root cause and resolve this P0 issue?

Samus is a silent paperweight until this is resolved and I'll need to visit Chrome/TechStop to have it updated by sighted-person when it's fixed...

If you could navigate or someone navigate) to the ChromeVox background page and provide that output, that would be very helpful.

Easiest way is to:
- open the ChromeVox options page (either via the keystroke or through chrome settings)
- substitute the options.html with background.html

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

commit 03bc1f9c36c253bfd2ef0b53cf621a52128198f3
Author: dtseng <dtseng@chromium.org>
Date: Tue Aug 09 15:50:06 2016

Revert of Move ChromeVox loading out of ComponentLoader. (patchset #3 id:40001 of https://codereview.chromium.org/2212853002/ )

Reason for revert:
BUG= 635294 

Repro:
- run Chrome OS on linux with an existing profile and with the flag --login-manager
- sign in or go through OOBE with ChromeVox on (and working)

result:
content scripts appear to be broken when logged in. I suspect user ChromeVox isn't loading.

Original issue's description:
> Move ChromeVox loading out of ComponentLoader.
>
> First, it isn't actually necessary to load ChromeVox from
> ComponentLoader. This code is probably historical. For quite some time,
> AccessibilityManager automatically loads ChromeVox on startup if the
> flag is set (and automatically loads/unloads when the flag changes).
> We should load it from only one place. Tested manually during startup
> and when logging into a session, both work fine without this call.
>
> Second, I intend to refactor AccessibilityManager so that it can support
> multiple accessibility component extensions. Rather than a separate function
> in ComponentLoader to load each one, I think it'd make more sense for
> AccessibilityManager to just call ComponentLoader with the appropriate
> parameters like the extension id and path.
>
> BUG= 634233 
>
> Committed: https://crrev.com/18f89cf0b120afff95e064f437140bdbfb33ef36
> Cr-Commit-Position: refs/heads/master@{#409916}

TBR=rdevlin.cronin@chromium.org,dmazzoni@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= 634233 

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

[modify] https://crrev.com/03bc1f9c36c253bfd2ef0b53cf621a52128198f3/chrome/browser/chromeos/accessibility/accessibility_manager.cc
[modify] https://crrev.com/03bc1f9c36c253bfd2ef0b53cf621a52128198f3/chrome/browser/extensions/component_loader.cc
[modify] https://crrev.com/03bc1f9c36c253bfd2ef0b53cf621a52128198f3/chrome/browser/extensions/component_loader.h

Looking forward to build 2825 that has this fixed. 
Thanks David!

Hello,

This issue seems to be unfixed on Chromebook Pixel 2 on chrome version
54.0.2826.0

Unable to hear any spoken feedback on the computer once logged in.

Canary seems to be broken, was this fix verified in canary?

Can you get speech with guest mode?

I had to request ChromeStop reimage me from Canary > Beta. The workaround of toggle cvox in a11y settings didn't work, nor was it possible to open ChromeVox Settings. 

Can someone help verify the fix? It sounds like anyone running the bad build may have inherited some bad state.

I auto updated to 54.0.2826.0 build on my samus and Cvox works fine for me.

Per #12 #13: Build 2826 on Samus has no ChromeVox speech. I was told visually, cvox worked, but there was no speech-output. via TTS

I do have speech here again. Cannot repro brokenness.

Hope that this issue doesn't trickle down to Dev > Beta > Stable...

@c20, this issue should be fixed and we've gotten multiple verifications from an upgrade scenario. I've also verified on a clean install. Let us know if you're still seeing it if you venture back on to Canary.