New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 731088 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Accessible text line offsets incorrect for list items entered in contentEditable

Project Member Reported by ja...@nvaccess.org, Jun 8 2017

Issue description

Chrome Version: 61.0.3122.0 (Official Build) canary(64-bit)
OS: Windows 10 Version 1703 (OS Build 16199.1000) 64-bit

What steps will reproduce the problem?

(1) Start Chrome and the NVDA screen reader.
(2) Open this URL: data:text/html,<div contentEditable="true"><ul><li>a</li></ul></div>
(3) Focus the text box and press control+end to move to the end of it.
(4) Press enter, then type "b", then press enter, then type "c".
(5) Press up arrow to move to the previous line.

What is the expected result?
NVDA should only announce "b".

What happens instead?
NVDA announces both "b" and "c".

On the list accessible, the line offsets for the second list item (offset 1) are returned as (1, 3). This is incorrect, as this covers both the second and third list items. Instead, the line offsets should be (1, 2).

Impact: This makes lists very difficult at best (unusable at worst) in editors for Chrome + NVDA users, including the Gmail composer.
 
Labels: triage-nektar
Labels: triage-aaron
Cc: nek...@chromium.org
Components: -UI>Accessibility UI>Accessibility>Compatibility
Labels: -Pri-3 Pri-2
Owner: ----
Status: Available (was: Untriaged)
Labels: -triage-aaron -triage-nektar
Owner: nek...@chromium.org

Comment 6 by nek...@chromium.org, Nov 22 2017

Status: Fixed (was: Available)

Sign in to add a comment