8000 Understanding Character Key Shortcuts · Issue #787 · w3c/wcag21 · GitHub
[go: up one dir, main page]
Skip to content
This repository was archived by the owner on Jun 30, 2018. It is now read-only.

Understanding Character Key Shortcuts #787

Closed
awkawk opened this issue Mar 2, 2018 · 6 comments
Closed

Understanding Character Key Shortcuts #787

awkawk opened this issue Mar 2, 2018 · 6 comments
Labels
Understanding

Comments

@awkawk
Copy link
Member
awkawk commented Mar 2, 2018

The 2.4.11 Character Key Shortcuts (A) SC has draft Understanding content that can be viewed at Understanding Character Key Shortcuts.

Please review the Understanding document and submit a comment on this issue for any changes that are needed to the content.
@joshueoconnor
Copy link
Contributor
joshueoconnor commented Mar 8, 2018 •
edited
Loading

Too many commas. Consider writing shorter sentences.

This paragraph is duplicated:

"This success criterion is becoming increasingly important in the mobile realm as growing number of apps more fully enable keyboard controls (see resources).'

@mbgower
Copy link
Contributor
mbgower commented Mar 9, 2018

I have made various editorial changes for clarity and consistency and created Pull Request 801.
I also removed Example 4, which does not seem to meet the requirements of the SC. I am pasting it here for reference:

Example 4: Native Speech Alternate Control

A mechanism is provided to allow users to change character-key shortcuts including to strings of up to 25 characters. These can directly serve as native speech commands for any speech engine.

@awkawk
Copy link
Member Author
awkawk commented Mar 9, 2018

@mbgower Process correction for you - don't worry about making a pull request from the Character key shortcut understanding document into the Master branch - once the group agrees with the content we will handle it.

If you feel like you have significant changes that you want to suggest, then create a branch for those changes and once people review them we can pull them into the Character-key-shortcut branch and THEN we can do the pull and merge into Master.

I think that removing example 4 is one change that I would want to make sure that the TF was in agreement on, but the way you did it here that example won't be in the rawgit version linked in this issue.

@lauracarlson
Copy link
Contributor
lauracarlson commented Mar 26, 2018 •
edited
Loading

Editorial comment:

To match the other Understanding documents, consider starting the Intent section with, "The intent of this success criterion is..." It is a good way to get straight to the point.

@lseeman
Copy link
Contributor
lseeman commented Apr 22, 2018

Can we add that: allowing all short cut keys to be personlized and remaped could help all users , as the same keys can have the same actions across all content. This is particularly helpful for people with impaired memory function or reduced learning speed.

@alastc alastc mentioned this issue Apr 23, 2018
Merged
@michael-n-cooper michael-n-cooper mentioned this issue Jun 12, 2018
Closed
@michael-n-cooper
Copy link
Member

This issue was moved to w3c/wcag#351

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Understanding
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@joshueoconnor @michael-n-cooper @awkawk @lauracarlson @lseeman @mbgower
0