Editing a basic document is the first thing any user will do in Docs
If that is not even accessible, the rest of the following experience will not be very good either... a user will give up

Suggestion: Since not having Braille Mode on seems to create many issues, should we automagically somehow enable it for someone who is using ChromeVox on Chrome OS. There are so many advantages of using Braille Mode and no disadvantages as far as I know.
In fact, we should automatically enable accessibility in Docs if ChromeVox is on, shouldn't we?

1. Braille mode should be default, as non-Braille mode is a non-starter with *any* screen reader
2. Is it possible for Docs to tell if cvox2 is enabled? If so, I absolutely agree that a11y should be automatically enabled. 

These live regions are not actually dropped, they're just slow. This bug requires performance profiling in the various components of Chrome accessibility starting off with the time from Blink to extension process then narrowing the scope on costly areas.

I also observe with NVDA that some characters are never echoed when 
moving the cursor such as commas and Parentheses. NVDA also doesn't seem 
to be able to determine if characters are capitalized when braille mode 
is off.


On 9/9/2016 3:41 PM, dts… via monorail wrote:

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

commit 89cf7451ed3e6091f24c641309fe057f92817cf9
Author: dtseng <dtseng@chromium.org>
Date: Tue Sep 13 21:08:10 2016

Define a minimum delay time for processing live regions on the same node.

This distinguishes the time we use to queue live region output vs the time we
use to drop live regions if fired on the same ancestry.

BUG= 641548 , 641548 , 641786 
TEST=type rapidly in Docs; verify all key presses are echoed with braille mode off.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

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

[modify] https://crrev.com/89cf7451ed3e6091f24c641309fe057f92817cf9/chrome/browser/resources/chromeos/chromevox/cvox2/background/live_regions.js

Braille mode = off, character nav reports letters correctly, but spaces are silent. However, Braille mode = On, spaces are read as "space", so not sure if we can re-scope this bug to %20 or if a new bug should be opened.

Generally, I don't like rescoping bugs since it makes reading the bug confusing.

As for the space issue, likely a Docs one since they're in control of the live region that reads the space, but I can investigate.

Yep, exactly: live region verbalizations drop for whitespace (spaces, tabs, etc.) and some punctuation. Same root cause of why capital letters sound the same as lower case letters with Braille support off in Docs.

This presents a major usability challenge for screen reader users as it 
stands now.



On 10/3/2016 9:17 AM, laur… via monorail wrote: