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

Issue 689195 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

Docs: focus character isn't uttered and BACKSPACE doesn't utter deleted character

Project Member Reported by chaok@google.com, Feb 6 2017

Issue description

Chrome Version: 58.0.3004.0 (Official Build) canary(64-bit)
OS: Win10
Screen reader: NVDA 2016.4 and JAWS 18

“When you arrow through a document, in Firefox, arrow keys will tell you the letter you are focused on; on Chrome it won’t. When you hit backspace, it doesn’t read the letter that was deleted” noting that he uses Docs with Braille mode off. 

What steps will reproduce the problem?
(1) Using above combo
(2) docs.google.com with Braille mode off
(3) Type some text
a. RIGHTarrow to a character > LEFT ARROW over same character
b. BACKSPACE character

What is the expected result?
3A: focused character to be uttered
3B: deleted character to be uttered

What happens instead?
Silence


 

Comment 1 by hwi@chromium.org, Feb 6 2017

Cc: -hwi@chromium.org -pkasting@chromium.org -rpop@chromium.org
Labels: -a11y-2017
removing label and cc after chat w/ chaok@
Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 27 2017

Labels: Hotlist-Google
Labels: triage-lpalmaro
62.0.3201.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
Windows 10 1607 14393.1593
NVDA 2017.3
JAWS 2018 Beta 

Hello,

I am not able to reproduce this issue with JAWS + Chrome with screen reader support enabled but can repro it with NVDA + Chrome. It appears to be somewhat related to the one-time setup of screen reader support since I can reproduce the bug in all cases with that mode turned off. Note that screen reader support does NOT turn on braille Support, it's a separate setting within the Accessibility tab of Docs.

# Open a doc, enable screen reader support using ctrl + alt +z, type some text "Hello world"
# Launch JAWS
# Right and left arrow across typed text. 
# Observe that JAWS speaks as expected, reading one character at a time.
# Backspace to delete the last character, d. Observe that d is spoken "blank d" This is expected. 
# Turn screen reader support off with ctrl + alt + z. 
# Observe that arrow keys and backspace do not speak the character that has focus. 
# Turn screen reader support back on. 
# Quit JAWS, launch NVDA
# Press arrow keys left and right. Note that the first character is not spoken but characters after that are spoken.
# Press backspace at the end. The first deletion, d, is not spoken. Subsequent characters are spoken when deleted. 


Now using NVDA and JAWS on FireFox 55.03 (64-bit)

# Launch Google Docs, open doc with "Hello world" written in it, enable screenreader support with ctrl + alt + z
# Launch JAWS 
# Arrow keys and backspace work as indicated, as expected
# Close NVDA, launch JAWS
# Arrow keys and backspace work as indicated, as expected (note that the backspace is not spoken, but this is consistent with normal NVDA behavior)

When screenreader support is disabled, characters are not read just like Chrome. The screen reader support makes the difference. 



Labels: -Hotlist-Google -triage-lpalmaro
Owner: nek...@chromium.org
Status: Available (was: Untriaged)
Nektarios, please take a closer look at this with NVDA.
Labels: a11y-secondary
Cc: lpalmaro@chromium.org nek...@chromium.org rbenz@google.com dmochak@google.com dmazz...@chromium.org
 Issue 681177  has been merged into this issue.
Cc: kkaja@google.com
 Issue 675647  has been merged into this issue.
 Issue 600146  has been merged into this issue.
Status: Assigned (was: Available)

Sign in to add a comment