Google Chrome 65.0.3322.3 (Official Build) canary (64-bit) (cohort: Clang-64)
Windows 10 Enterprise Version 1607 Build 14393.2007
NVDA 2017.4
JAWS 2018.1801.18 Private Beta 
Firefox ESR 52.5.3 (64-bit)

Resolving as Docs issue. 

# Launch JAWS, turn of virtual cursor with JAWS + Z
# Open Docs with end-user account, enable accessibility with ctrl alt z
# Create example Doc with misspelling: apple, pear, pineappple, appleq 
# Use keyboard shortcut to navigate to next misspelling, Ctrl + ' 
Expected: misspelled word is read
Actual: On the first misspelled word, pineappple is read as expected. However, when moving to the next misspelled word, Docs announces "no more misspelled words" while putting focus on appleq. 

# Close JAWS, launch NVDA, press NVDA+space to enter focus mode
Actual: the cursor jumps to the misspelled word but nothing is read at all. Tying a character in the new focused area reads the letter entered and letter is inserted where the cursor jumped. 

Compare to Firefox + JAWS:
Nothing is read at all with arrow keys. 
Compare to Firefox + NVDA:
Same behavior as NVDA with Chrome 
___

Originally reported in b/69840688  

Windows 8.1
Chrome: 63.0.3239.59 beta (64 bit)
JAWS: 18.0.4321

Steps Performed:
a. Open docs and enter text in edit region with misspellings.
b. Navigate to misspellings in accessbility menu.
c. Now try to move to next/previous misspelling.

Actual Result:
Screen Reader doesn't announce that focus is moved to misspelling.

Expected Result:
Screen Reader should announce that focus is moved to misspelling.