New issue
Advanced search Search tips

Issue 755389 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

[A11y Assessment - Function Keys] Need a more intuitive experience with function key labels

Project Member Reported by lpalmaro@chromium.org, Aug 14 2017

Issue description

OS: Chrome
Version: 61.0.3163.38

1. Enable ChromeVox Ctrl Alt Z
2. Attempt to use function keys (top row of keys)

We should consider adding spoken labels to some of these keys, to make the experience more clear. I would imagine that users may find it helpful if when they pressed the go back button, that ChroemVox spoke "go back" then the page title. Same for go forward. I think of these physical buttons more similarly to the UI buttons, so we should make sure the user's context is clear when they press them. 

We also need a state change spoken when you press the enter full screen button. Right now, it's just silent, and we really need it to tell the user "entered fullscreen mode" or "exited fullscreen mode". 

Last, we need to figure out a better way to handle the mute button. I propose that when a user presses the mute button, that ChromeVox first speaks "muting", and then it mutes the system. This is how Mac handles this with VoiceOver. Then when you press again, ChromeVox should speak "unmute". 
 

Comment 1 by dtseng@chromium.org, Sep 18 2017

Owner: ----
Status: available (was: Assigned)

Comment 2 by dtseng@chromium.org, Sep 18 2017

Cc: dtseng@chromium.org
 Issue 725632  has been merged into this issue.
Labels: top-cvox
Owner: dtseng@chromium.org
David, is this something you could take on as part of our ChromeVox hotlist? 
Status: Assigned (was: Available)

Sign in to add a comment