SC 2.4.11 problematic in non-web ICT context; also Understanding text being overtaken by events

[peterkorn]

First, in the non-Web context there may be AT that uses single-key keystrokes for performance reasons. This SC shouldn't apply to them. Second, Understanding text is based on circa 2016 speech recognition technology (e.g. Dragon Naturally Speaking on a PC), which is being overtaken by events. To wit, both Alexa and Google Assistant now have speaker identification, and so the real-life example in Understanding can be addressed by the voice recognition system.

[awkawk]

Thank you for commenting. For more information about how the AG WG will process this issue, see the following:

• Issue Processing - How the WG will discuss the issue
• Issue Resolution - Identifying and responding to the official WG response
• Issue Notification - How to limit notifications from GitHub

[awkawk]

(Official WG Response)
Thanks for the comment.

The first part of your comment is that AT may use single-key keystrokes. The SC is not designed to apply to keystrokes implemented by AT, which is intended to be clarified by the "If a keyboard shortcut is implemented in content" phrase. If the content implements a keyboard shortcut then the content author needs to attend to this SC, but if content is used by a person who is using AT that implements single-key shortcuts then it is not the responsibility of the content author (e.g. a web page that has headings conforms even though some screen readers/AT implement navigation quick keys to jump to headings).

Regarding the second part, we will update the Understanding text with additional examples and will consider adding an example for Alexa/Google Home - type systems. It is worth noting that the issue being addressed can arise with only one speaker in the room, as the speech recognition tools will process human speech and send a sequence of keystrokes through the keyboard interface and triggering a single key shortcut.

[awkawk]

The WG decided on the above response, so we changed the text in the comment containing the proposed response to read "[Official WG Response]". Please confirm is you are satisfied with the response within 1 week. If we haven't heard a response in a week we will regard the resolution as satisfactory.