Issue metadata
Sign in to add a comment
|
a11y: JAWS 2018 not reading search suggestions in Omnibox |
||||||||||||||||||||||
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 ZoomText Private Beta - 11.7.11.410 Search suggestions in Omnibox are not read with JAWS 2018, other AT (including older versions of JAWS) work as expected. # Launch Canary and JAWS # Paste in "short film where dogs like" into Omnibox (alternatively: do this in the google.com search box) # Navigated down the results using the down arrow key Expected: Screen reader would read the suggestions as I navigated them Actual: Screen reader did not read the suggestions # Close JAWS, Launch Canary and NVDA # Paste in "desert flower bouquet si" into Omnibox # Navigated down the results using the down arrow key # All suggestions read as expected # Close screen readers, launch Canary and ZoomText # Magnify screen to level 2 # Paste in "stainless steel pull sa" into Omnibox # Examine all results - magnified without issue # Navigated down the results using the down arrow key # All suggestions read as expected
,
Nov 14 2017
Also repros in 55 so this is not a regression: Google Chrome 55.0.2841.0 (Official Build) (64-bit) This does not repro in Firefox's version of the address bar: Firefox 56.0.2
,
Nov 14 2017
,
Nov 14 2017
,
Nov 14 2017
This is a regression in JAWS and I've communicated with the developers.
,
Nov 14 2017
,
Nov 22 2017
Update from aleventhal@ I've been able to repro the bug of JAWS not reading the autocomplete as follows: 1. Unload JAWS and Chrome 2. Load Chrome, do not load JAWS yet 3. Once Chrome is loaded, run JAWS 4. Hit Ctrl+L and try to use autocomplete (URL bar) Not only is it silent, but I also see that only get_accValue is used, and none of the IA2 APIs such as get_text, get_textAtOffset, get_selection, which JAWS normally exercises for this control. To get JAWS working again, load a page and start reading it with the virtual cursor. Sometimes this works. Or, just exit Chrome and relaunch it. Now when you hit Ctrl+L, JAWS uses the IA2 APIs and has no trouble. NVDA doesn't have this issue with Chrome. However, JAWS doesn't have the issue with Firefox. Tech note to add to bug: we should see whether we are allowing QueryService to IA2 to succeed.
,
Nov 23 2017
,
Dec 13 2017
VFO says this is an issue on their side, with JAWS ignoring some value change events. Will keep monitoring.
,
Dec 14 2017
,
Dec 15 2017
,
Dec 15 2017
,
Jan 25 2018
Any remaining issues are on the JAWS side. Unfortunately, as they are fixing them, some users have older versions of JAWS and will not have the fix.
,
Jan 26 2018
Fixed, although older versions of JAWS are likely to remain affected. The issue seems to be intermittent.
,
Feb 28 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by leberly@chromium.org
, Nov 14 2017