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

Issue 854899 link

Starred by 1 user
Status: Assigned
Owner:
leberly@chromium.org
Cc:
dtseng@chromium.org
leberly@chromium.org
█ dsexton@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Team-Accessibility



Sign in to add a comment

Google TTS settings page not announced as opened in new tab (exiting settings)

Project Member Reported by leberly@chromium.org, Jun 21 2018 
69.0.3464.0 (Official Build) dev (64-bit)
Samus and Eve

This one is a bit subtle and borderline not a bug, found by dsexton@

# Enable Experimental Accessibility flag in chrome://flags
# Navigate to Settings > Manage accessibility features > Text To Speech voice settings > Speech Engines > Chrome OS built-in text-to-speech extension
# Press settings button to open Google TTS settings page
Expected: screen reader user knows that they are exiting the settings app and are now in a tab in the browser
Actual: user not aware of this, pressing the hotkeys for back puts user in unexpected place. Settings button says "Settings Button Link"

Compare this to Settings > Manage accessibility features > Enable ChromeVox > Open ChromeVox settings button visually indicates that you are leaving the settings page and screen reader announcement is "Open ChromeVox settings"

Comment 1 by leberly@chromium.org, Jun 21 2018

Cc: dsexton@chromium.org
dsexton, what do you think given that the button does include the word "link"? Should it match the Open ChromeVox Settings UI?

Comment 2 by katie@chromium.org, Jun 21 2018

Cc: dtseng@chromium.org
https://chromium-review.googlesource.com/c/chromium/src/+/1108379 will associate the settings link with the correct TTS engine, which should make this more clear.
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 21 2018 

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

commit 969b6f31a2cf2e19a6069a10941dd9a2b129322f
Author: Katie D <katie@chromium.org>
Date: Thu Jun 21 19:05:18 2018

Fix aria-describedby and one i18n string in tts_settings page.

Bug: 853576, 854901 ,854899, 854893 
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I0e027023f631f61a7969e2adc04c6ef59c87b38e
Reviewed-on: https://chromium-review.googlesource.com/1108379
Commit-Queue: Katie Dektar <katie@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569347}
[modify] https://crrev.com/969b6f31a2cf2e19a6069a10941dd9a2b129322f/chrome/browser/resources/settings/a11y_page/tts_subpage.html

Comment 4 by katie@chromium.org, Jun 21 2018 

@leberly, @dsexton, does the aria-describedby work just submitted make this bug obsolete?

Comment 5 by katie@chromium.org, Jul 18 

Ping - leberly? dsexton?

Comment 6 by leberly@chromium.org, Aug 7

Labels: M69A11yTests

Comment 7 by katie@chromium.org, Aug 7

Cc: leberly@chromium.org
Ping again?

Comment 8 by katie@chromium.org, Aug 13

Owner: leberly@chromium.org
►

Sign in to add a comment