New issue
Advanced search Search tips

Issue 822493 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

ChromeVox doesn't respect user-specific key mappings from settings

Project Member Reported by leberly@chromium.org, Mar 16 2018

Issue description

Google Chrome OS 67.0.3369.0 (Official Build) canary (64-bit)
Firmware Version Google_Samus.6300.276.0

This affects users who want custom key mappings for both internal and external keyboards with Chromebooks. Use cases include attaching a Windows keyboard to the Chromebook via USB and changing the mappings on the internal keyboard to accommodate users who like Mac style keyboard layouts. 

Steps to repro for internal keyboard:
# Enable ChromeVox with ctrl + alt + z
# Go to Settings > Keyboard
# Change Search to the Alt
# Change Alt to be Search
# Attempt to linear navigate holding down the physical alt key (search) and the arrow keys
Expected: nav works
Actual: alt key is still treated as alt key, linear nav not working. The search key is still treated as a the search key. 

However, if ChromeVox is disabled, the system has switched the keys properly. Using the physical search key (alt) + ctrl + l will bring focus to the launcher.  While ChromeVox is enabled, the system isn't getting key commands for launcher, etc.

Steps for external keyboard are the same except the Caps Lock key should be set to Search. The same problems are present.
 
Components: UI>Accessibility>SelectToSpeak
Labels: M67test
This also applies to STS with the same repro steps as above.

External Windows keyboard and internal keyboard - same bug

Google Chrome	67.0.3383.0 (Official Build) dev (64-bit)
Firmware Version	Google_Samus.6300.276.0
Chrome OS with flag enabled: #enable-experimental-accessibility-features

Comment 2 by katie@chromium.org, Apr 17 2018

Components: -UI>Accessibility>SelectToSpeak
Labels: a11y-testers
Actually this should work with STS as of 67.0.3387.0. +a11y-testers to confirm; removing Select-to-Speak component.
Labels: -a11y-testers
Google Chrome	67.0.3396.12 (Official Build) dev (64-bit)
Firmware Version	Google_Samus.6300.276.0

Confirmed, STS respects the keyboard remappings. I am able to invoke STS when I set the hardware Alt key to be search. I can use both the search + s and the search + mouse drag version. 

Sticky Keys also respect the remappings.

I also confirmed that this is NOT fixed in ChromeVox. Settings hardware Caps Lock to Search did not allow me to use it as a Search key in linear navigation, for example. 

Removing a11y-testers label, please put back on when we can test a ChromeVox fix. 

Sign in to add a comment