tnagel@, can you PTAL? Is this a privacy bug?

That's an intriguing question. The behavior seems to be in line with audio (e.g. from a video that's currently being shown) continuing to play when the device is locked. (That may be questionable by itself, but when the website is a music player, it's probably what users expect to happen.)

Otoh, I'd consider ChromeVox output more akin to text on the page than to audio output of the page. Therefore my personal opinion is: Yes, it's a bug and we should fix it (similar as page contents rendering on the lock screen would be a bug).

I'll discuss among the privacy team and get back with a more authoritative answer.

Hi are there any updates on this bug?

I'll take a look.

Any updates on this? I'm not sure it really is a security bug at this point.

I suppose it's more privacy.

If I have my Chromebook on and locked and someone messages me confidential info over hangouts and Chromevox shouts it out to who ever happens to be near by... That's no good.

Google Chrome	72.0.3593.0 (Official Build) dev (64-bit)
Firmware Version	Google_Caroline.7820.384.0

I've discovered another part of this bug - if you have focus on any Google Doc or Sheet, that will be read on the lockscreen, too. Live regions are part of the G-Suite backend. 

Steps: 
# Enable ChromeVox screen reader with ctrl + alt + z
# Open any Doc or sheet and place focus in the document area
# Navigate to the system tray with alt + shift + s
# Navigate to the "lock" button and invoke it
Expected: focus lands on the lockscreen 
Actual: focus remains on the Google Doc or Sheet and contents is read out loud 

The problem looks similar to issue 833870 -- maybe we should aim for a unified approach. Melissa, what's your take?