Issue metadata
Sign in to add a comment
|
A11Y: NVDA does not read input type number controls in Chrome |
||||||||||||||||||||||||
Issue description65.0.3287.0 (Official Build) canary (64-bit) (cohort: Clang-64) NVDA 2017.4 JAWS 2018 Steps to repro: # With NVDA running: open the attached file in Chrome # Tab to the number control # Press up arrow 9 times, noting NVDA's feedback # Notice NVDA says 'blank' as the numbers change Expected: NVDA reads each number as it changes Actual: NVDA reads 'blank' for each number # Press NVDA+up arrow (NVDA+l in laptop layout) to read the current line # Note NVDA says 'blank' # Press left arrow so the caret is on the number # Press NVDA+up arrow (NVDA+l in laptop layout) to read the current line # Note NVDA reads the number Expected: NVDA reads the number Actual: NVDA only reads the number when the caret is on the number Perform all tests above with JAWS Note that JAWS reads while changing numbers and current line Expected: Works as expected
,
Dec 18 2017
Possibly related to issue 781016 -
,
Apr 2 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nek...@chromium.org
, Dec 15 2017