[Accessibility] Document F6! #4743
Merged
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
|
@citelao : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 572b4b6: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
Learn Build status updates of commit a4f974f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
|
We might want to add to the list of Common Keyboard Accelerators |
|
@Karl-Bridge-Microsoft, anything blocking this? |
|
Learn Build status updates of commit 0f62f83: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
PRMerger Results
|
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.
The F6 key is a critical keyboard usability feature for many users, especially keyboard-only users who do not use screen readers. However, we do not document it today. This change adds some basic F6 documentation to our accessibility & keyboarding guidelines.
What changed?
Justification
F6 is a well-known shortcut. In fact, we publicly document it in Keyboard shortcuts in Windows.
It is critical to the usability of several of key surfaces, including Edge, the literal Windows desktop, File Explorer, and many Office products (including PowerPoint and Outlook). It is a rapid accelerator for navigating the UI with keyboard (and without a screen reader, which has other tools).
However, support for F6 is declining. It is rare to find F6 support in newer apps, which instead tend to rely on hard-to-find hotkeys or, worse, just tab and arrow keys.
This is partially a documentation issue. We should document F6 as an important shortcut, and then we can discuss how to introduce F6 support more consistently in our UI.