we discussed this in today’s accessibility team meeting, here’s our proposed approach:
- The command palette will be better served with the DEP or new features treatment. It’s a solid concept, has a reasonable case to be a core feature, but requires more maturation of the concept / implementation (see previous messages).
- Keyboard shortcuts are simple enough as a concept and fundamental enough to meet our accessibility requirements that we think we can proceed with a list of shortcuts + other aspects relevant for implementation.
@sage and I offered to help with that spec, that will be directly inspired by our experience implementing this in Wagtail, and our understanding of related requirements in the WCAG and ATAG standards. We think this is going to be simple in big part because those standards make it clear how and why to get shortcuts.
For anyone wanting to do their own research already, here are the relevant references in W3C standards that help determine which shortcuts to implement, and how to implement shortcuts:
- Developing a keyboard interface: Keyboard shortcuts in the ARIA Authoring Practices Guide (APG)
- ATAG 2.0 A.3.1 Provide keyboard access to authoring features
- WCAG SC 2.1.4 Character Key Shortcuts (Level A)