Issue metadata
Sign in to add a comment
|
Virtual keyboard window is not hooked by ChromeVox |
||||||||||||||||||||||||
Issue descriptionChrome Version: 59.0.3048.0 OS: 9391.0.0 kevin What steps will reproduce the problem? (1) Enable ChromeVox with Ctrl-Alt-Z (2) Go to tablet mode and launch Chrome (3) Focus on omnibox and open virtual keyboard. (4) Tap virtual keyboard What is the expected result? Virtual keyboard window should be hooked by ChromeVox and outlined by orange rectangle. What happens instead? Chrome window below the virtual keyboard is hooked.
,
Apr 19 2017
,
Apr 19 2017
Working on this now: https://codereview.chromium.org/2803823002/
,
May 4 2017
What would happen to the focus of the typing if we do that? Just want to make sure we don't accidentally break actual typing for users who need ChromeVox.
,
May 4 2017
Shouldn't affect typing at all. Our goal is just to create a good experience for blind users on a touchscreen Chromebook. I finished making the virtual keyboard window part of the accessibility tree. That was a technical detail, we had been missing it because it was directly embedded in an aura Window instead of in a View or in a tab. Now that works. Next we just want to improve the feedback when you tap on a key.
,
Aug 10 2017
Actually, I'm still not seeing the keyboard if ChromeVox was already running. I have to toggle it off then back on to see it. Can you please take another look? Thanks!
,
Aug 10 2017
Also, feel free to reassign if you don't have time to look.
,
Sep 6 2017
I think this is fixed by 755514.
,
Jan 22 2018
,
Jan 23 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by oka@chromium.org
, Apr 10 2017