Keyboard Access and Focus

Question 1

Purpose of Testing 2.1.2-no-keyboard-trap

Answer 1

To determine if users are able to navigate away from keyboard accessible elements and subsections of web page.

Question 2

What is NOT Tested as Part of 2.1.1-Keyboard-Access

Answer 2

If AT, such as voice recognition tool, works properly so users are able to navigate to and select interactive elements.

Question 3

What Does the Tester Validate When Testing for 3.2.1-on-focus

Answer 3

When any keyboard -accessible component receives focus, it does not initiate an unexpected change in context.

Question 4

Tester’s Purpose When Testing for 2.4.7-Focus-Visible

Answer 4

To validate that when there are keyboard-accessible interface components on a page, there is also a visible indication of keyboard focus when on each element

Question 5

Reason for Testing 2.1.1-No-Keystroke-Timing

Answer 5

To determine if any functionality requires the user to complete certain keystrokes within a specific timing between keystrokes

Question 6

Content Being Tested for 2.1.1-Keyboard-Access

Answer 6

All interactive elements on the web page

Question 7

Why is 3.2.1-On-Focus Tested

Answer 7

To validate that when a component receives focus, there is an unexpected change of context.

Question 8

Purpose of Testing for 2.4.3-Focus-Order-Meaning

Answer 8

To validate that keyboard-focusable elements receive focus in an order that preserves meaning and operability