Issue metadata
Sign in to add a comment
|
ChromeVox should honor system keys |
||||||||||||||||||||||
Issue descriptionChromeVox provides various accelerators. AFAICT these accelerators *never* honor the system keys. If I've remapped search to some other key, I would expect that to impact ChromeVox. This is especially important when running a ChromeOS build on the desktop as to test these keys requires unbinding a bunch of keys used by the desktop window manager. Ugh!
,
Apr 3 2018
For reference: I wanted to test ChromeVox on a linux desktop chromeos=1 dev build In order to do this on gLinux Debian rodete w. Cinamon v 3.4.6, I had to: 1) System Settings -> Keyboard -> Layouts -> Options... -> Alt/Win key behavior -> "Hyper is mapped to Win keys" 2) Remove *all* System Settings -> Keyboard -> Shortcuts Keyboard bindings that reference "Super" It would be nice to document these steps somewhere, perhaps here: https://chromium.googlesource.com/chromium/src/+/lkcr/docs/accessibility/chromevox_on_desktop_linux.md It would be even nicer if we somehow made this easier for chrome devs to setup/test. (why doesn't remapping eg. Caps Lock to Search in chrome://settings/keyboard-overlay work?)
,
Sep 14
,
Sep 14
FWIW, I think this entails having EventRewriterController/EventRewriterChromeOS be added as event rewriters before the accessibility event rewriters. Hopefully that would be straightforward and not break and a11y features. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ovanieva@chromium.org
, Mar 16 2018Status: Assigned (was: Untriaged)