Open aubrey-oneal opened 1 month ago
@aubrey-oneal I always considered these two a bit different even though at a glance they feel similar. One is more guidance on how to design (and annotate) keyboard interactions (actually guidelines) — this could possibly be merged with Accessibility content though.
“Keyboard Shortcut Guidance” could probably be called just “keyboard shortcuts” (a pattern!) and be more focus on how we trigger and display shortcuts for experiences that does include them.
There is both a keyboard shortcut guidelines page in Patterns and a Keyboard (operation) guidance page.
Keyboard shortcut guidance
This pattern is suggesting a consistent way to show a user the keyboard shortcuts within a product
Keyboard (operation) guidance
This is "pattern" is outlining how to annotate keyboard operations of a product, likely used to hand off to a developer
Evaluate if this content is up to date (check with Gower?)
Is this content duplicative to other areas? (Carbon core or Accessibility)
[ ] Work with our accessibility experts to merge and update this content @mbgower
[ ] Add any additional missing Accessibility guidelines.
[ ] Either create a Figma or MDX draft of this content. It will live in a new page Guidelines>Accessibility, to be created in issue #5503
[ ] Explore if this should move to core as part of website phase 1