Issue metadata
Sign in to add a comment
|
Jumping to next and previous misspelled word in Docs not announced properly
Reported by
nimerjaber1@gmail.com,
Aug 26 2016
|
||||||||||||||||||||||
Issue descriptionMode: force_next Version: 54.0.2837.0 Reproduction Steps: 1. Enable Chromevox Next 2. docs.google.com>>blank document. 3. Type the following line: Marbels and Qubes are great idems to any kolekshion. 4. Navigate to the top of the document. 5. Ctrl+' to jump to the next misspelled word. Expected: Focus is brought to the next misspelled word, and the cursor location is announced. Better yet, the misspelled word is announced, and a user is placed at the beginning of that word. Actual: Chromevox reads... not sure really. Sometimes, it reads part of the line with the misspelled word on it. Other times, it reads nothing. And maybe 10-15% of the time, it actually reads the misspelled word. this happens in either direction, with next or previous misspelled word.
,
Aug 26 2016
Braille mode is on as with it off, navigation is unstable at best, and there is a lot more verbalization. I would be happy to repro and test without Braille mode...
,
Aug 26 2016
Is the fact that it doesn't work with Braille mode ON a Docs or ChromeVox Next issue?
,
Aug 26 2016
This appears to be a docs issue, as the same bug can be reproduced with NVDA.
,
Aug 26 2016
Shawn, considering that this is reproduced in both ChromeVox Next and NVDA, can you take a look?
,
Aug 28 2016
ctrl+' focuses/reads random words/lines, but doesn't indicate that it's misspelled.
,
Aug 29 2016
,
Oct 25 2016
This is strictly a Docs issue since they are in control of speech. Docs is whitelisted for using the Classic engine now, so a fresh look would be appreciated. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Aug 26 2016