Issue metadata
Sign in to add a comment
|
A11y: JAWS virtual cursor view unstable in Chrome with Forms |
||||||||||||||||||||||||
Issue descriptionGoogle Chrome 64.0.3268.0 (Official Build) canary (64-bit) (cohort: Clang-64) Windows 10 Enterprise Version 1607 Build 14393.1770 NVDA 2017.3 JAWS 2018.1710.42 private preview release I am resolving this issue as WontFix because I can't replicate it. Report from a user to investigate: "The virtual cursor view just disappears randomly. You need to turn the virtual cursor off and turn it back on to be able to read the text. I don’t know if this is a bug in Chrome, Forms, or Jaws." I tried to repro it using these steps: # Create an example form with two questions. One uses a short answer response for an edit field and the other uses a paragraph response for an edit field. # Launch JAWS and Chrome Canary # Navigate to the form # Enter a lot of text in the paragraph field, then short answer, then back to paragraph again. Enter at least 60 words. # Tab back and forth between these fields quickly adding more text each time. # Navigate around the website and your open programs quickly, putting focus onto the Omnibox, other programs open in Windows, and around the submit button. # Listen to what is spoken after each transition between states. # Repeat with Chrome and NVDA. During this time, forms mode turned on and off as expected as I navigated around and the virtual cursor kept reading the content as expected. It also stayed on while typing a lot of text into the paragraph edit field. Speculation: one possibility for the user's complaint is that JAWS and NVDA treat the form differently: in JAWS you use the arrow keys to navigate headings while NVDA includes the headings while reading the contents of each edit field.
,
Nov 16 2017
Assigning to David S for another look.
,
Nov 21 2017
I have tested with a simple sample form and am unable to reproduce this bug. Find my sample form attached. Please provide exact repro steps so I can confirm and bisect.
,
Dec 1 2017
Nektar@ determined the cause of this bug: We don't always fire the DOCUMENT_LOAD_COMPLETE event. Assigning to him to investigate.
,
Dec 10 2017
,
Dec 11 2017
Problem identified and patch created.
,
Dec 11 2017
,
Dec 11 2017
,
Dec 12 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7d3a2280ccdfb7c1bb1ace857edf678dcf519fdf commit 7d3a2280ccdfb7c1bb1ace857edf678dcf519fdf Author: Nektarios Paisios <nektar@chromium.org> Date: Tue Dec 12 04:21:46 2017 Keep the same tree root when the root is simply updated R=dmazzoni@chromium.org Bug: 785100 , 761882 Change-Id: Iab2181a6208b116eb2043446eb8edb4061a59d76 Tested: Manually with Jaws and NVDA on crbug.com and freedomscientific.com, unit test Reviewed-on: https://chromium-review.googlesource.com/820107 Commit-Queue: Nektarios Paisios <nektar@chromium.org> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#523332} [modify] https://crrev.com/7d3a2280ccdfb7c1bb1ace857edf678dcf519fdf/ui/accessibility/ax_tree.cc [modify] https://crrev.com/7d3a2280ccdfb7c1bb1ace857edf678dcf519fdf/ui/accessibility/ax_tree_unittest.cc
,
Dec 12 2017
,
Dec 12 2017
Tested with crbug.com
,
Jan 11 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nek...@chromium.org
, Nov 15 2017Status: Available (was: WontFix)