Skip to main content
RAAMA

10.3 On each screen, the navigation must not contain any keyboard traps. Is this rule respected?

WCAG references
  • 2.1.1 Keyboard (A)
  • 2.1.2 No keyboard trap (A)

Official methodology to test criterion 10.3

Test 1 (10.3)

iOS
  1. Connect an external keyboard (and configure keyboard navigation).
  2. Navigate all the elements on the screen using the dedicated keyboard keys (by default in iOS, the Tab and arrow keys are used to navigate content).
  3. Check that
    • from the current position, the next or previous focusable item can be reached using the keyboard navigation keys;
    • the element currently in focus offers a method that can be used with the keyboard (for example, a keyboard shortcut) to reach the next or previous element.
  4. If this is the case, the criterion is validated. Note: Some complex elements, often managed by the platform, can call on optimised navigations which generally use the direction arrows to move from one part of the component to another. The keyboard trap test is then limited to checking that the component can be reached and that it is possible to move on to the next component or return to the previous component. The actual use of the component is not checked in this criterion.
Android
  1. Connect an external keyboard (and configure keyboard navigation).
  2. Navigate through all the elements on the screen using the keys on the keyboard (the keys or combination of keys that will have been associated in Switch Access for the "Next" and "Previous" parameters).
  3. Check that
    • from the current position, the next or previous focusable element can be reached using the keyboard navigation key;
    • the element currently in focus offers a method that can be used with the keyboard (for example, a keyboard shortcut) to reach the next or previous element.
  4. If this is the case, the criterion is validated. Note: Some complex elements, often managed by the platform, can call on optimised navigations which generally use the direction arrows to move from one part of the component to another. The keyboard trap test is then limited to checking that the component can be reached and that it is possible to move on to the next component or return to the previous component. The actual use of the component is not checked in this criterion.