Issue metadata
Sign in to add a comment
|
Incorrect contentEditable feedback with NVDA when moving by line |
||||||||||||||||||||||
Issue descriptionChrome Version: 58.0.3004.0 (Official Build) canary(64-bit) OS: Win10 Screen reader: NVDA 2016.4 and JAWS 18 “content editable issues are still big. NVDA doesn’t consistently read the deleted character when you backspace. When you scroll by line, you sometimes get the previous line and not the current line.” What steps will reproduce the problem? (1) Using above combo on new message in Gmail.com (2) Type a few lines (3) A. UP/DOWN ARROW to line-nav B. BACKSPACE to delete characters What is the expected result? 3A: Focused line to be uttered 3B: Deleted character to be uttered What happens instead? 3A: previous line instead of current line 3B: Silence
,
Mar 28 2017
,
Apr 21 2017
,
Apr 21 2017
,
Jul 27 2017
,
Aug 4 2017
,
Sep 1 2017
,
Sep 7 2017
,
Sep 7 2017
Chrome 63.0.3207.0 (Official Build) canary (64-bit) (cohort: 64-Bit) Windows 10 Enterprise Version 10.0.14393 Build 14393 NVDA 2017.3 JAWS 2018 Beta FireFox 55.0.3 (64-bit) Hello, I can reproduce this issue in Chrome using NVDA but not JAWS using these steps: With NVDA on, compose a new email. Type three lines of text. Use up arrow keys to navigate to the top line. This reads as expected. Press the down arrow twice, noting that the first line is read twice even though the second line's content is different. Then, backspace and note that nothing is read during the character deletion. Repeat these steps with JAWS and the three lines are read correctly as expected. Pressing the backspace button announces the characters being deleted. Not reproducible with JAWS. Cannot repro in FireFox both with JAWS and with NVDA.
,
Dec 10 2017
Line navigation has been fixed. Backspace issue is mostly on NVDA's side and is being worked on in another bug. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hwi@chromium.org
, Feb 6 2017Labels: -a11y-2017