Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define area navigation key command and behavior #1546

Open
mcking65 opened this issue Sep 30, 2020 · 0 comments
Open

Define area navigation key command and behavior #1546

mcking65 opened this issue Sep 30, 2020 · 0 comments
Labels
Pattern Page Related to a page documenting a Pattern Practice Page Related to a page within the practices section of the APG

Comments

@mcking65
Copy link
Contributor

There are multiple patterns that would benefit from a recommended convention for a keyboard command to navigate among areas or sections of a page:

The functionality needed for all these patterns is similar. Recommending the same key command for all would:

  • Make learning and using the command easier.
  • Reduce the complexity of developing a convention given the scarcity of options.

The purpose of this issue is to discuss:

  • Pros and cons of merging the needs of these patterns into a single area navigation keyboard command.
  • Recommended behaviors.
  • Key assignment.

Starting proposal

Key assignments

  1. Ctrl+F6 or Cmd+F6: Move focus to next area
  2. Shift+Ctrl+F6 or Shift+Cmd+F6: Move focus to previous area
  3. Alt+F6 or Option+F6: Move focus to first element in current area
  4. Shift+alt+F6 or Shift+Option+F6: Move focus to first area

Types of areas

Areas may be a:

  • Landmark region
  • Non-modal dialog
  • Feed
  • Other type of author-defined container that calls for efficient context switching

Design Recommendations

  • Include landmark regions in the area navigation sequence.
  • When moving focus to a landmark region or feed for the first time, if the first element is interactive, place focus on that element. Otherwise focus the entire region.
  • When moving focus into a non-modal dialog for the first time, follow the modal dialog guidance for where to place focus.
  • If it would facilitate usability, when focus moves into an area, focus the element that last had focus in that area.

Note that utility of the area navigation sequence can be negatively impacted if it is too long. On a typical page, six to eight elements is likely a suitable upper limit.

@mcking65 mcking65 added Practice Page Related to a page within the practices section of the APG Pattern Page Related to a page documenting a Pattern labels Sep 30, 2020
@mcking65 mcking65 added this to the 1.2 Release 1 milestone Sep 30, 2020
@mcking65 mcking65 removed this from the Final ARIA 1.3 Additions milestone Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Pattern Page Related to a page documenting a Pattern Practice Page Related to a page within the practices section of the APG
Projects
None yet
Development

No branches or pull requests

1 participant