Improve the SC 2.1.2 No Keyboard Trap Understanding #4316
Closed
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
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
- Moving dialog example higher because it is more common
stevefaulkner
approved these changes
Apr 7, 2025
| <p>The keyboard focus is not considered as trapped when the user can navigate away from a UI | ||
| component using the unmodified tab or arrow keys or when another “standard exit method” exists. | ||
| What is a “standard exist method” depends on the user’s hardware and software. A press | ||
| of the <kbd>ESC</kbd> key is such a “standard exit method”. When the press of the hardware back |
Member
There was a problem hiding this comment.
the "When" sentence doesn't quite work structure-wise
|
|
||
|
|
||
| <p>The intent of this success criterion is to ensure that that content does not “trap” the | ||
| keyboard focus within subsections of content on a web page or app. It is common to restrict |
Member
There was a problem hiding this comment.
the "It is common..." insert here seems out of place. I'd move it to the next paragraph, and change this back to talking about the problem
Member
|
x-ref #4381 |
Co-authored-by: Patrick H. Lauke <[email protected]>
Contributor
Author
|
Thanks for the review and feedback, @patrickhlauke! |
|
patrickhlauke marked as non substantive for IPR from ash-nazg. |
patrickhlauke
added a commit
that referenced
this pull request
Nov 2, 2025
Ports over most of the ideas from #4316, but extends/clarifies them further.
Member
|
Closing this draft PR in favour of #4726 (as this PR here has conflicts, and it won't allow changes to be pushed to it) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Very drafty Friday afternoon start of an improvement here.