- 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.1.1
Return to Tests_for_CR
Contents
Status
written 21 October 2014
Author
Jan Richards
Success Criteria
2.1.1 Provide Full Keyboard Functionality: All functionality can be operated via the keyboard using sequential or direct keyboard commands that do not require specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. free hand drawing). This does not forbid and should not discourage providing other input methods in addition to keyboard operation including mouse, touch, gesture and speech. (Level A)
Tests
Test Procedure 1
- Open a test document that contains enabled elements (standard form fields, buttons, links)
Sample HTML test document: Sample page with form controls, buttons, links - Connect a keyboard (corded, Bluetooth-connected, etc.) or keyboard emulator.
- Check that you can navigate and operate all UA user interface functionality (menus, toolbars, settings, documentation, etc.)
- Check that you can navigate and operate enabled elements in the content (standard form fields, buttons, links)
Expected Results 1
- Check #3 and #4 are true