New issue
Advanced search Search tips

Issue 800915 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

A11Y: inbox.google too verbose when selecting messages

Reported by nimerjaber1@gmail.com, Jan 10 2018

Issue description

Version: 65.0.3316.0
Reproduction Steps: 
1. inbox.google.com and log in.
2. Press j to jump to the first bundle or message. If a message, press x. If a bundle, prss enter, navigate to a message, and press x to select the bundle.
3. Press j to jump to the next message, and press x to select.
Expected: As soon as the message is selected, the reading of the message is stopped, and Chromevox utters 1 selected, 2 selected, etc.
Actual: The message reading is interrupted and restarted, and only once the entire subject and preview is read is the selection count announced.

For this, it is much preferable to have Chrome utter nothing at all than to re-read the subject and preview.

Thank you for all you do.

 
Components: -UI>Accessibility UI>Accessibility>ChromeVox
Labels: -Pri-2 Pri-3
Owner: dtseng@chromium.org
Status: Available (was: Unconfirmed)
Summary: A11Y: inbox.google too verbose when selecting messages (was: Nimer's back, inbox.google too verbose when selecting messages)
Project Member

Comment 2 by bugdroid1@chromium.org, Feb 6 2018

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

commit b0fcecbfe73dc6335aa67126af738c14f4ee7221
Author: David Tseng <dtseng@chromium.org>
Date: Tue Feb 06 19:50:41 2018

Cleanup: queueing vs flushing

ChromeVox currently defaults to generate speech output with queue mode category flush.

Changes:
- remove no-op calls to force queue mode to category flush
- users of Output should now consider
|forceModeForNextUtterance|
as the global switch for queue mode behavior
- Output.prototype.withQueueMode should be considered as a local way of specifying queue mode. It gets overridden by the global mode if set.
- live region output is locally category flushed/ queued, keyboard handler is globally flushed.

chromevox_tests: ensure live region suite in particular passes (which contains various tricky cases for queue mode in various situations).

Bug:  800915 
Test: manual: test on inbox.google.com. Ensure pressing 'x' triggers flushed speech.
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ic767411e7d4a017c274e33b596b77b8312adac6c
Reviewed-on: https://chromium-review.googlesource.com/895059
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#534759}
[modify] https://crrev.com/b0fcecbfe73dc6335aa67126af738c14f4ee7221/chrome/browser/resources/chromeos/chromevox/cvox2/background/background.js
[modify] https://crrev.com/b0fcecbfe73dc6335aa67126af738c14f4ee7221/chrome/browser/resources/chromeos/chromevox/cvox2/background/desktop_automation_handler.js
[modify] https://crrev.com/b0fcecbfe73dc6335aa67126af738c14f4ee7221/chrome/browser/resources/chromeos/chromevox/cvox2/background/keyboard_handler.js
[modify] https://crrev.com/b0fcecbfe73dc6335aa67126af738c14f4ee7221/chrome/browser/resources/chromeos/chromevox/cvox2/background/output.js

Status: fixed (was: Available)

Sign in to add a comment