New issue
Advanced search Search tips

Issue 789280 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 791665
Owner: ----
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

A11Y: ChromeBook labels for buttons and checkboxes on extension management page are not descriptive for chromevox users

Project Member Reported by dsexton@chromium.org, Nov 28 2017

Issue description

Bug from a user:
wile playing with my new  chrome book i have found a few more unlabled  controles steps to find them 
  open  extenchons and start tabbing  through the window the first check box is not  labled and the rest of the buttons in there need work many of the controls in this window just say remove from chrome. 
 for the controle to  meet   w3c the  controle needs to  be read out of context and these buttons and check boxes do not meet that standered 
 

Comment 1 Deleted

I noticed that In Chrome Stable and Canary on Windows, the extension sections are separated by headings, but not in Chrome OS. 
Cc: -l...@accessaces.com
Actually pasting repro steps:
Chrome: 64.0.3270.0 (Official Build) dev (64-bit)
Firmware Version	Google_Samus.6300.174.0

Steps to repro:
# With chromevox running: open the extensions page: alt+f > more tools > extensions
# Tab through all options on the page
# Notice that Chromevox does not announce which extension each button or checkbox controls

Expected: The extension name would be announced along with the control's purpose

Actual: Only the control's purpose is announced

# Explore all controls on the page using search+left and right arrow keys
# Notice that extension names are announced, but it is difficult to know in the middle of the document which set of controls will control a particular extension

Expected: Each extension and it's controls would be separated from the previous and next set

Actual: There is nothing to differentiate one set from another

Comment 4 by l...@accessaces.com, Nov 28 2017

hello:  heddings are not enough it needs to have a lable that includs the
information if you tab  throu it  needs to stand alone and speak the proper
lable not just remove from chrome but what are  you  removing from  chrome
think of it this way if you bring up the list of buttons in jaws what do
you see you don't see the hedding you see the label only so it should be
formated like this remove x from  chrome and x is the item your  removing
Components: UI>Browser>ExtensionsManagement
Mergedinto: 791665
Status: Duplicate (was: Available)
This is a duplicate of Issue 791665

Sign in to add a comment