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

Issue 717098 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Add spoken feedback for the subheaders in detailed view

Project Member Reported by minch@chromium.org, May 1 2017

Issue description

What steps will reproduce the problem?
(1)Enable ChromeVox
(2)Touch or <Tab> the subheader in detailed view, eg, "Output" or "Input" in "Audio settings"

What is the expected result?
Spoken feedback for the subheaders, eg {Output} or {Input}

What happens instead?
None spoken feedback

The subheaders may need to add spoken feedback,
1.Header of vpn type. Ex, “OpenVPN/L2TP'
2.Audio, {input} and {output}
3.Network, network type in the detailed view,
eg,{Ethernet}, {Mobile Data}, {Wi-Fi}

 
Components: UI>Accessibility UI>Shell>StatusArea
Labels: -Pri-3 Proj-MaterialDesign-CrOS M-60 OS-Chrome Pri-2
Owner: ----
Status: Available (was: Assigned)
Owner: manucornet@chromium.org
Status: Assigned (was: Available)
Bulk-assigning unassigned status area bugs to me.
Labels: -M-60

Sign in to add a comment