New issue
Advanced search Search tips

Issue 623370 link

Starred by 4 users

Issue metadata

Status: Verified
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Pressing the Delete key will read the letter that is deleted as opposed to the letter after the cursor

Reported by nimerjaber1@gmail.com, Jun 26 2016

Issue description

Mode: force_next
Version: 53.0.2773.0
Reproduction Steps: 
1. enable Chromevox Next and navigate to a chunk of text in an editable field.
2. Find a letter to be deleted and press the delete key.
Expected Result: Chromevox will only read the letter that receives focus. This letter is the one after the cursor. Chromevox will not read the letter that is being deleted. This is consistent with behavior of a variety of other screen readers including NVDA, JAWS and others on a variety of platforms.
Actual Result: Chromevox reads the letter that is being deleted. A user has no way of knowing the position of the cursor unless another key sequence is pressed.
 
Cc: lpalmaro@chromium.org dtseng@chromium.org
Status: Untriaged (was: Unconfirmed)
Happens on 53.0.2782.6
Labels: phease3
Status: Available (was: Untriaged)
Labels: -phease3 Phase3
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 26 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7eadf9dff59e6e7654ffd9ab3e36c170aacdab97

commit 7eadf9dff59e6e7654ffd9ab3e36c170aacdab97
Author: dtseng <dtseng@chromium.org>
Date: Tue Jul 26 23:07:02 2016

Support Windows/Linux-style forward delete feedback

In Windows and Linux, screen readers read the character to the right of the cursor. This behavior extends to forward deletes. This style of reading is more optimal if one counts the actual cahracters one hears when deleting text assuming the user needs to move to that character first.

By default, this we use this style of reading on Windows, Linux, and Chrome OS based on the ibeam cursor setting.

BUG= 623370 
TEST=chromevox_tests --gtest_filter=*Editable*.*
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation;master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2104473003
Cr-Commit-Position: refs/heads/master@{#407954}

[modify] https://crrev.com/7eadf9dff59e6e7654ffd9ab3e36c170aacdab97/chrome/browser/resources/chromeos/chromevox/common/editable_text_base.js
[modify] https://crrev.com/7eadf9dff59e6e7654ffd9ab3e36c170aacdab97/chrome/browser/resources/chromeos/chromevox/common/editable_text_test.unitjs

Status: fixed (was: Available)

Comment 6 by chaok@google.com, Sep 12 2016

using shift+backspace, ctrl+backspace, and backspace seem to properly utter the text that is deleted in: 55.0.2857.0

Thanks!

Comment 7 by dtseng@chromium.org, Sep 12 2016

Status: verified (was: Fixed)

Sign in to add a comment