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

Issue 616180 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Wallpaper picker accessibility issues

Project Member Reported by lpalmaro@chromium.org, May 31 2016

Issue description

Version: 53.0.2749.3
OS: Chrome

What steps will reproduce the problem?
Navigate to settings > Set Wallpaper. 

1) Contrast on this UI is poor. The gray text on the black backgroun is not meeting our 4.5:1 min. contrast level. We need to make the text lighter to enhance contrast. 

2) The UI is not accessible using keyboard only, or keyboard + Chromevox screen reader. I can't interact with this UI using just the keyboard. We need to ensure that  a user can navigate through this UI just using tab, shift tab, arrows and enter to select a given item, and that visual focus is always clear. 

3) We also need to ensure that this works properly with the Chromevox screen reader. Right now, since keyboard support is not there, we also can't use the Chromevox screen reader to navigate around. We need proper labels for the different wallpapers so a blind/visually impaired user can understand what the wallpaper is via spoken feedback. 


@Albert, any thoughts on who can own this work? 
 
Owner: abodenha@chromium.org
Status: Assigned (was: Untriaged)
Friendly ping - Albert, do you know who owns this UI? 
Cc: dtseng@chromium.org jennschen@chromium.org kuscher@chromium.org
Labels: -Pri-3 Hotlist-Accessibility Pri-2
I'm able to navigate with just the keyboard, but it's really non-obvious what's happening with focus. There are 3 distinct regions in the picker that can be toggled with tab, but only the bottom region gives any indication when it's active.

ChromeVox is unable to do anything with the picker at all. I'm guessing it's trying to use ChromeVox classic and script injection is failing. I suspect the right answer is to use ChromeVox next and make sure all the wallpapers are properly labeled.

jennschen@ and kuscher@ it seems like we need to consider things from a UX perspective for at least 1 and 2.
Owner: kuscher@chromium.org
Labels: NewComponent-Accessibility NewComponent-Accessibility-ChromeVox
Labels: -NewComponent-Accessibility-ChromeVox NewComponent-Accessibility-Browser
Labels: -newcomponent-accessibility-browser -newcomponent-accessibility

Sign in to add a comment