New issue
Advanced search Search tips

Issue 627159 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature
Team-Accessibility



Sign in to add a comment

[CVox Next] Keyboard settings

Project Member Reported by lpalmaro@chromium.org, Jul 11 2016

Issue description

When giving demos, some users expressed that they did like the Classic N and P keyboard navigation and that they would want a setting in Chromevox options to use N and P methodology instead of the flatter key map. Let's consider adding a setting for users who were used to this navigation and want to continue using it for jump commands.  


 
Components: UI>Accessibility
I tend to think that users liked it because it was what they were used to... but personally, I don't think there is anything efficient about the old method. I am glad that this was changed. Still, options are good...

Comment 3 by chaok@google.com, Oct 16 2016

I personally find the flat keymap in Next to be more delightful and efficient. However, users are generally resistent to change (e.g. it took me a while to adjust when NVDA changed their keymap)
Labels: NewComponent-Accessibility-ChromeVox NewComponent-Accessibility
Components: UI>Accessibility>ChromeVox
Labels: -newcomponent-accessibility -newcomponent-accessibility-chromevox
Components: -UI>Accessibility
Status: wontfix (was: Assigned)

Sign in to add a comment