Since it's been over two years without any further information provided, we're closing this Jira issue for now. If more details become available in the future, we can reopen it. Thank you.

Since it's been over two years without any further information provided, we're closing this Jira issue for now. If more details become available in the future, we can reopen it. Thank you.

Discussing on Accessibility WG call, consensus was that a true menu for the items to create Lessons content would be better than having keyboard shortcuts for jumping to them.

However, the structure for adding content will change with Lessons 2.0, so it may not need to be modified here.

I disagree with creating specific keyboard shortcuts for this kind of navigation. As described in the WebAIM article on Accesskey, special accesskeys can easily cause confusion for users and conflict with assistive technology settings, so they should be used only when absolutely necessary. The Apple developers Human Interface Guidelines indicates that expected keyboard shortcuts should be enabled for standard menu items.

I think the issue of quick access to items in the lessons menus would be more appropriately remedied by:

1. Dividing the groupings of items into smaller, more logical groups (such as putting the three "Embed" options for Calendar, Announcements, and Forums widgets in a separate group than the options to generate links).

2. Introducing a proper heading structure for each grouping of menu items, e.g., Add Content, Create Links, Embed Content, etc., to enable navigation via headings for those who use heading link lists to navigate.

3. Putting the options in an actual menu where you can start typing the first characters of an option to skip down to its link.

Adding the UX label to this ticket to have the UX group review.

I'd also be interested in hearing your thoughts on how these menu options could be made more usable/navigable for accessibility.