RE: Changes to "Character Key Shortcuts" concern

Hi Kim,

It is hard to tell from the examples, but it didn’t look like anything had focus when those issues triggered?

Without that phrase it impacts the keyboard accessibility of native HTML elements (another show-stopper). A select drop-down is a component with single-character keyboard short-cuts that only trigger when it has focus.

From reading the (very useful & good) Understanding doc, if you were focused on a select drop-down and spoke some dictation that would be passed through and it would skip down options in the drop-down. Is that a problem?

It appeared that the problem cases were ones that are global, that trigger when nothing is focused, or are not specific to the component that has focus.

Is there a more exact phrase that would help?

Cheers,

-Alastair

From: Kim Patch

Good with the first two changes. The “unless... focus” change would be very bad for users. The background section of the understanding document addresses this. So do the videos. See the “Hey Kim” use case. This is a show stopper for speech users.
Cheers,
Kim

Kim Patch