676549 - Add keyboard shortcuts for jumping to landmarks

Status: RESOLVED DUPLICATE of bug 670928

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

Note: this bug is required for us to advocate the deprecation of 'skip links'.

As a starting point these would be useful:

1. Site Navigation
<nav>, or aria role="navigation"

2. Main content
aria role="main"

Comment 1

[Rich Schwerdtfeger]

This will free the development community from having to implement skip to main content links in rich internet applications. It is much less intrusive. Imagine having to place skip to main content links in facebook or Google+.

Comment 2

[Matt King]

Instead of making keys to move to specific landmarks, which is very limitted and difficult to discover,
Consider providing a list of landmark names/roles in a tree structure and displaying it in a dialog.
Make the dialog available from view menu and the toolbar.
Provide a shortcut key for opening the dialog.
When focus is on a landmark list item, pressing enter closes dialog and puts browser focus at the start of that region.
Put initial focus on the first main landmark item in the tree. This way, pressing the shortcut to open the dialog and then pressing enter puts focus on main.
include a search edit that filters the tree based on name or type.
In the dialog, provide buttons with accelerator keys that do the following:
- move to main
- move to next nav
- show only nav
- reorder tree by type (role)
- assign a user definable shortcut key to currently focussed landmark.

Comment 3

[David Bolter [:davidb] (NeedInfo me for attention)]

Matt, would the typical target user of your comment 2 suggestion be a screen reader user?

Comment 4

[David Bolter [:davidb] (NeedInfo me for attention)]

Just discovered we have this bug filed already.

Comment 5

[David Bolter [:davidb] (NeedInfo me for attention)]

(In reply to David Bolter [:davidb] from comment #3)
> Matt, would the typical target user of your comment 2 suggestion be a screen
> reader user?

I'm asking because it affects Ux design.