New issue
Advanced search Search tips

Issue 793113 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 730965
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

A11Y: NVDA does not read input type number controls in Chrome

Project Member Reported by dsexton@chromium.org, Dec 7 2017

Issue description

65.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

 
number.html
360 bytes View Download

Comment 1 by nek...@chromium.org, Dec 15 2017

Labels: combo-boxes editing
This is an editing bug in addition to a combo boxes bug because the issue is that when the caret is at the end of the edit field inside the spin control, affinity is set to downstream which causes AXPosition to retrieve the spin button after the text field instead of the returning a position inside the text field. A possible fix is to hide the spin buttons "+" and "-" from the a11y tree.
Possibly related to issue 781016 - 
Mergedinto: 730965
Status: Duplicate (was: Available)

Sign in to add a comment