New issue
Advanced search Search tips

Issue 845695 link

Starred by 2 users
Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

A11y: Clear button in the shortcut input field on chrome://extensions/shortcuts is missing an accessible label

Reported by gurupras...@gmail.com, May 22 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3437.2 Safari/537.36

Steps to reproduce the problem:
1. Install a chrome extension that contains a few configured keyboard shortcuts
2. Open chrome://extensions/shortcuts
3. Inspect the "clear" button adjacent to shortcut inside the shortcut input field 
5. In the Accessibility tab of the dev tools, observe that the name property of the clear button is "" 
6. Navigate to the clear button with JAWS screen reader, observe that clear button is announced as "Unlabeled 0 button"
7.Navigate to it with NVDA screen reader, observe that clear button is announced as "button"

What is the expected behavior?
The clear button should have an accessible label that is associated to the respective command name.
Ex: Label = "Clear activate landmarks shortcut", when the command name is activate landmarks
Then the screen readers would announce the clear button as "Clear activate landmarks shortcut" button

What went wrong?
The clear buttons for the commands are missing accessible labels, so they are announced as "buttons" by the ATs

Did this work before? No 

Chrome version: 68.0.3437.2  Channel: canary
OS Version: 10.0
Flash Version:
Clear button - missing label.png
55.6 KB View Download
Missing label - JAWS test.png
42.2 KB View Download
Missing label - NVDA test.png
35.4 KB View Download

Comment 1 by krajshree@chromium.org, May 23 2018

Labels: Needs-Triage-M68

Comment 2 by krajshree@chromium.org, May 23 2018

Labels: M-68 Triaged-ET FoundIn-68 Target-68 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #68.0.3437.2 and latest canary #68.0.3438.0.

This issue is seen only with Material design extensions. It is working fine in old UI.

As this issue is seen from the introduction of material design extension flag from M63, considering this issue as Non-Regression and marking as untriaged for further inputs from dev team.

Thanks...!!
►

Sign in to add a comment