These results are for non-Corp accounts. For corp accounts, there are no known working builds. 

Bumping up to level 1 priority since this is a regression. 

Additional note, I looked into the NVDA documentation and there is not feature parity for Say To Cursor and Say From Cursor. Therefore, this is a JAWS-specific regression. 

FYI, NVDA has the following commands in relation to the system caret: Say all, Read current line, Read current text selection, Next sentence, Previous sentence. Read current line works without issue in Chrome 63.0.3227.0 (Official Build) canary (64-bit) (cohort: 64-Bit). 

Hi Doug,

It turned out that this bug reproduced intermittently around the builds found by the bisect. That is, when I ran the bisect multiple times I had different results. For example, for one run, the first known bad build was 499976 and for another run a few moments later 499976 became a good build and 499977 became the first known bad build. Because of this, David listed all CLs associated with +- 10 builds from that target. He found the following CL made by you which is why we are now recommending that you reproduce it on your machine:
https://chromium-review.googlesource.com/c/chromium/src/+/659217

If this isn't the culprit, there is a small chance it is related to the other accessibility change in that +-10 build range: 0ee1e46aa8d9 Remove unused method AriaLabelledbyElements 

Please let us know if you have further questions. 

Thanks,

Laura 
  

I found a different cl that might be the cause.  From the bisection, we are probably looking for a change made after 500773 (known good), but no later than 500782 (first known bad).
  https://chromium.googlesource.com/chromium/src/+log/df93d69db604c650a582df8d32dc54a2d43c7c71..0b62c1d3ddf30c98930e19464c22803092868acc


Which implies that it was this:
     https://chromium.googlesource.com/chromium/src/+/6335ae2d3b49e332fa49e909ec6fe5802590980e%5E%21/


Turns out that Aaron fixed this with:
   https://chromium-review.googlesource.com/c/chromium/src/+/692336

Assigning to myself to repro now that a fix has been posted. 

Resolving this bug as Verified since I can no longer repro this behavior.

Google Chrome	63.0.3236.0 (Official Build) canary (64-bit) (cohort: 64-Bit)

Here is what I did: 
# Launch new Google Doc in a non-Corp account, make sure that in Accessibility tab, Settings > Enable braille support is checked 
# Type a bunch of text to fill a line, for example 8 sets of "Hello World": "Hello World Hello World Hello World Hello World Hello World Hello World Hello World Hello World"
# Put cursor in the middle of the line of text
# Invoke keys for Say to Cursor, INSERT+HOME 
# Four sets of "Hello World" are read (start of line to that point)
# Invoke keys for Say from Cursor, INSERT+PAGE UP
# # Four sets of "Hello World" are read except for the last word, World, since it is on the next line.