Expand 2.1.2 understanding to make it more ... understandable #4726
Conversation
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
Ports over most of the ideas from #4316, but extends/clarifies them further.
❌ Deploy Preview for wcag2 failed.
|
Member
Author
|
@kfranqueiro "untrapping" flagged as a spelling error... |
Contributor
Slightly amusing, since I had already needed to add "untrap". Add "untrapping" on a new line in |
Member
Author
|
ah, perfect (and yes, chuckling as well) thanks @kfranqueiro |
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.
Ports over most of the ideas from #4316, but extends/clarifies them further.
Expands on what "standard exit methods" are (and the fact that WCAG doesn't actually normatively define these, that they're hardware/OS/UA dependent, and that authors/auditors will need to use their judgement here). Also reiterates that even if untrapping involves "non-standard" methods, that's fine as long as users are informed how to do it (but still needs to be using the keyboard).
Also cleans up the markup a bit.
Supersedes #4316 (as that PR didn't allow for changes to be pushed to it, including rebasing it to the latest main branch)