Rework 2.1.4 Character Key Shortcut understanding - #5336
Open
patrickhlauke wants to merge 23 commits into
Open
Conversation
* expand the focus to not be primarily about speech users * expand the speech input explainer to match reality a bit better * remove the outdated resources section
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…cter-key-shortcuts-rework' into patrickhlauke-character-key-shortcuts-rework
…keyboard key" section
patrickhlauke
force-pushed
the
patrickhlauke-character-key-shortcuts-rework
branch
from
September 1, 2026 14:31
94f67f4 to
2942012
Compare
patrickhlauke
marked this pull request as ready for review
September 2, 2026 13:36
Member
Author
| <p>A user interacting with a web page or web app that doesn't use single-character shortcuts doesn't have this problem. Inadvertent strings of characters from the speech application are not interpreted as shortcuts if a modifier key is required. A speech user filling in a text input form may find that a phrase that is accidentally picked up by the speech microphone results in stray text being entered into the field, but that is easily seen and undone. The Resources section of this page contains links to videos demonstrating these types of issues.</p> | ||
| <p>Speech input users generally work in a single mode where they can use a mix of dictation and speech commands. The user knows to pause before and after commands, and commands are usually at least two words long. So, for instance, a user might say a bit of dictation, such as "the small boat", then pause, and say a command to delete that dictation, such as "Delete Line". In contrast, if the user were to say the two phrases together without a pause, the whole phrase would come out as dictation (i.e., "the small boat delete line").</p> | ||
| <p>In most cases, voice control/speech recognition software is "context-aware" – speech is not interpreted as dictation, unless focus is on a form control or field that accepts keyboard input. Otherwise, speech is only interpreted as a command. In addition, even when focus is inside a form control or field that accepts keyboard input, dictation does not generate "faked" synthetic key presses – the spoken text is generally injected directly into the relevant form control/field. Synthetic key presses only happen when a user gives an explicit command, such as "Press X key".</p> | ||
| <p>However, there are some voice control/speech recognition programs (such as <a href="https://talonvoice.com/">Talon Voice</a>) that are not "context-aware". All speech is interpreted as either a command or dictation, regardless of where the current focus is. In addition, saying certain keywords is interpreted by some programs as a shorthand for the "Press … key" command, leading to potential unintentional single key presses. Critically, programs that are not "context-aware" may also turn dictation into synthetic key presses, meaning that an unintentionally spoken word can become a sequence of single-key commands if the cursor focus happens to be in the wrong place. Character key shortcuts will be problematic for users of these non-context-aware programs.</p> |
Contributor
There was a problem hiding this comment.
Reference to Talon Voice: How long will that be valid? Leave out brand name?
Member
Author
There was a problem hiding this comment.
the issue here is that it seems Talon is pretty much the only tool out there that behaves this way it seems...this is a way to salvage the whole voice angle, in my view, as none of the other voice control/voice access tools commonly used now have the problem this SC purports to solve...
Contributor
There was a problem hiding this comment.
I agree with Detlev, I would not get as far as naming a specific software here
baldino-m
reviewed
Sep 4, 2026
baldino-m
reviewed
Sep 4, 2026
baldino-m
reviewed
Sep 4, 2026
baldino-m
reviewed
Sep 4, 2026
Co-authored-by: Baldino Morelli <baldino.morelli@usablenet.com>
patrickhlauke
commented
Sep 4, 2026
alastc
reviewed
Sep 4, 2026
kfranqueiro
reviewed
Sep 4, 2026
Co-authored-by: Alastair Campbell <ac@alastc.com>
Co-authored-by: Kenneth G. Franqueiro <kfranqueiro@users.noreply.github.com>
bruce-usab
reviewed
Sep 6, 2026
Co-authored-by: Bruce Bailey <bruce@bailey4.us>
…rowse/focus mode information and resources link to more in-depth explanation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stretch goals (to discuss with TF):
Closes #953