Revise Custom Keys Documented (#598)#602
Draft
fstrr wants to merge 11 commits into
Draft
Conversation
fstrr
commented
Mar 2, 2026
fstrr
commented
Contributor
- add new term for “custom keyboard command”
- revise provision
* add new term for “custom keyboard command” * revise provision
✅ Deploy Preview for wcag3 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for wcag3-howtos canceled.
|
In an effort to get new ACT Rules onto the WCAG site (because it’s likely quicker this way), I’ve duplicated the `tests` directive to create a new `actrules` one. We’re running out of heading levels, so I’ve used a description list to mark up the content. I’ve also left the “this section is non-normative” content in there.
- Re-title to No Repetitive Interactive Elements to cover non-link interactive elements - Add an exception - Add first draft ACT rules
Contributor
|
Preview diff at Guideline 2.4.1 Keyboard interface input (this PR as compared to Editor’s draft). |
iadawn
requested changes
Jun 10, 2026
| --- | ||
|
|
||
| Non-standard keyboard commands provided by content authors are documented and that documentation is programmatically and visually available from any :term[page]/:term[view] to which they apply. | ||
| :term[Custom keyboard commands] are documented. That documentation is :term[actively available] from any :term[page]/:term[view] to which it applies. |
Contributor
There was a problem hiding this comment.
Suggested change
| :term[Custom keyboard commands] are documented. That documentation is :term[actively available] from any :term[page]/:term[view] to which it applies. | |
| :term[Custom keyboard commands] have :term[actively available] documentation on any :term[page]/:term[view] on which the custom keyboard command can be used. |
| 1. Check that documentation of keyboard commands exists. | ||
| For each :term[custom keyboard command] that works on a page/view: | ||
| 1. Check that documentation of the keyboard commands exists. | ||
| 2. Check that the documentation is available from the page/view. |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. Check that the documentation is available from the page/view. | |
| 2. Check the custom keyboard command is documented on the page/view on which they custom keyboard command can be used. | |
| 3. Check that a link to custom keyboard command(s) documentation is available on the page/view on which the custom keyboard command is used. |
| 2. Check that the documentation is available from the page/view. | ||
|
|
||
| **Expected results** | ||
| - #1 and #2 are true. |
Contributor
There was a problem hiding this comment.
Suggested change
| - #1 and #2 are true. | |
| - #1 is true. | |
| - #2 or #3 is true. |
|
|
||
| Passed example 1 | ||
| : A search input can be focused using a custom keyboard command of / (forward slash). This custom keyboard command is documented as programmatically related description text for the input. | ||
| : [Passing example 1](https://cdpn.io/pen/debug/dPpyVZQ/508d2feff6fba738c4a825c54d8cb94c) |
Contributor
There was a problem hiding this comment.
I think we should be looking to include worked examples directly in our repo rather than relying on a third-party hosting service.
| issueLabel: No repetitive links | ||
| --- | ||
|
|
||
| The :term[page]/:term[view] does not have adjacent :term[interactive elements] that achieve the same outcome |
Contributor
There was a problem hiding this comment.
Suggested change
| The :term[page]/:term[view] does not have adjacent :term[interactive elements] that achieve the same outcome | |
| Adjacent :term[interactive elements] that achieve the same outcome are not included in the :term[page]/:term[view]. |
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
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.