- Important note: This Wiki page is edited by participants of the User Agent Accessibility Guidelines working group (UAWG). It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

2.3.1

From WAI UA Wiki
Jump to: navigation, search

Return to Tests_for_CR

Status

Approved 16 October 2014 Jeanne split into 2 tests - 20 October 2014

Author

Greg Lowney

Success Criteria

2.3.1 Allow Direct Navigation to Enabled Elements: The user can move keyboard focus directly to any enabled element in the rendered content. (Level AA)

Tests

Test Procedure 1 (browser shortcuts)

Note: It is recommended that you test several different types of elements.

Note: In this test, do not use commands that merely move to the next or previous enabled element (e.g. Tab or Shift+Tab).

  1. Identify methods of activating direct navigation shortcuts to enabled elements (e.g. by exploring the UI or consulting Help documentation).
  2. Open a test document that contains rendered text and a variety of enabled elements (e.g. links and form controls).
    Sample HTML test document: test page with rendered text and enabled elements
  3. Identify enabled elements that don't have author-provided shortcuts (e.g. accesskey attribute).
  4. For one or more such elements:
    • Check that you can move keyboard focus directly to the element, skipping intervening elements, using a shortcut (e.g. typing or speaking a user-agent provided identifier, or selecting an item in a list of enabled elements).
      Note: For many user agents this ability will require adding an extension.

Expected Results 1

  • Check that #4 is true for each element tested

Test Procedure 2 (Accesskeys)

Note: It is recommended that you test several different types of elements.

Note: In this test, do not use commands that merely move to the next or previous enabled element (e.g. Tab or Shift+Tab).

  1. Identify methods of activating direct navigation shortcuts to enabled elements (e.g. by exploring the UI or consulting Help documentation).
  2. Open a test document that contains rendered text and a variety of enabled elements (e.g. links and form controls).
    Sample HTML test document: test page with rendered text and enabled elements
  3. If the document format supports author-specified shortcuts (e.g. accesskey attribute):
    1. Identify enabled elements that have author-provided shortcut (e.g. accesskey attribute).
    2. For each element:
      • Check that you can move keyboard focus directly to the element, skipping intervening elements, using a shortcut (e.g. pressing Alt+accesskey, typing or speaking an identifier, or selecting an item in a list of enabled elements).

Expected Results 1

  • Check that #3.2 is true for each element tested

Return to Tests_for_CR

Outdated

Survey of 9 October 2014

Assertion: The user can move keyboard focus directly to any enabled element in the rendered content.

1. load page (with rendered text and enabled elements (e.g. anchors, form elements)

2. using the device focus movement mechanism (e.g. number, swipe, voice input), move focus directly to the 5th enabled element skipping previous enabled elements

Retrieved from "https://www.w3.org/WAI/UA/work/wiki/index.php?title=2.3.1&oldid=909"