Google Chrome	66.0.3336.5 (Official Build) canary (64-bit) (cohort: Clang-64)
Google Chrome	64.0.3282.140 (Official Build) beta (64-bit) (cohort: Beta)
Google Chrome	63.0.3239.132 (Official Build) (64-bit) (cohort: Stable)
Windows 10 Enterprise Version 1607 Build 14393.2007
NVDA 2017.4
JAWS 2018.1801.81 ILM 

This bug was introduced somewhere between Stable in 63 and Beta in 64 and continues to repro in Canary in 66. It does NOT repro in NVDA in any release. Steps to repro:

# Enable JAWS screen reader and open Chrome 
# Go to keep.google.com and sign in if needed. If there are no notes, add an example note. 
# Use the arrow keys to navigate across the example notes

Expected behavior from 63: As you arrow through the buttons and text fields, each are read. This includes reading the text in the note without opening it first. 

Actual in 64 and above: As you arrow through the fields, the text is omitted from the ordering. It goes from button to button and does not read the text. 

An end user reported this in a mailing list and indicated that this removes the ability to know which note you're selecting unless you open it first. 

Assigning to myself to bisect.