Update keyboard to remove normative acceptance of "completely custom … #3670
Conversation
This file contains 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
make clear that ANY key would pass
…ithub.com/w3c/wcag into patrickhlauke-understanding-keyboard-note
replacing "keyboard users" with "users of the keyboard interface" in two places to emphasize that the SC also addresses the needs of AT users that rely on the keyboard interface - and that by implication any custom key input would not serve their needs. Removing the phrase referring to custom key operation.
…ow reintroduce the "custom key combination" idea Also harmonises some suggestions/changes that were done in only one of the two matching notes
…key or key combinations" Changes > "deviating from these conventions does <em>not</em> fail the normative requirement" to > deviating from these conventions does <em>not</em> always fail the normative requirement
|
saying "does not always fail" without explicitly explaining when it does or doesn't ... won't really help authors or testers in determining whether they do pass or fail |
chaals
reviewed
Feb 6, 2024
| @@ -75,19 +75,18 @@ <h2>Intent of Keyboard</h2> | |||
| the platform/user agent conventions it may be difficult to use, as users will need | |||
| to learn different interaction methods. As a <em>best practice</em>, content | |||
| should follow the platform/user agent conventions. However, deviating from these | |||
| conventions does <em>not</em> fail the normative requirement of this Success Criterion.</p> | |||
| conventions does <em>not</em> always fail the normative requirement of this Success Criterion.</p> | |||
There was a problem hiding this comment.
Partially dealing with @patrickhlauke's feedback...
Suggested change
| conventions does <em>not</em> always fail the normative requirement of this Success Criterion.</p> | |
| conventions does <em>not</em> automatically fail the normative requirement of this Success Criterion.</p> |
(The rest of his comment is addressed, IMHO, by the text that follows).
There was a problem hiding this comment.
that still leaves doubt though about when it does or doesn't, so authors and testers still are none the wiser
Base automatically changed from
patrickhlauke-understanding-keyboard-note
to
main
February 14, 2024 12:06
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
to
Removes
...since this is likely to fail AT users relying on the keyboard interface.