Section 508 Guidance Outlines Keyboard Accessibility Requirements and Manual Testing Methods

The U.S. General Services Administration's Section508.gov has issued guidance highlighting the requirements and testing methods for keyboard accessibility across electronic media.

Statutory Requirements Under Section 508

Section 508 requires federal agencies to ensure that all information and communication technology (ICT) procured, maintained, or used is operable without requiring a mouse or other pointing device. This applies to digital content, including electronic documents, websites, and desktop and mobile software.

Keyboard accessibility serves individuals with mobility disabilities, users who are blind or have low vision, users of assistive technology that emulates keyboard input, people with temporary limitations preventing mouse use, and those who prefer keyboard navigation.

Manual Keyboard Testing Procedures

Section508.gov notes that basic keyboard accessibility issues can be identified by testing digital products without a mouse using primary navigation commands:

• Tab: Moves focus forward through interactive components such as links, form fields, and buttons.
• Shift + Tab: Moves focus backward through interactive components.
• Enter: Activates controls, links, and buttons.
• Spacebar: Toggles or activates specific controls, such as checkboxes and buttons.
• Arrow keys: Navigates options within component structures, such as menus, lists, and radio button groups.
• Escape: Closes or dismisses modal dialogs, menus, and related interface elements.

Evaluation criteria during keyboard testing include whether all interactive elements are reachable, whether controls can be activated, whether the navigation order follows a logical reading sequence, whether users can enter and exit components without getting stuck, and whether the focused element is visually distinguishable.

Focus Indicators and Keyboard Traps

The guidance emphasizes two structural requirements:

• Visible focus indicators: Elements receiving keyboard focus must present a discernible visual change, such as an outline, border, or underline, enabling users to locate their current interface position. The guidance instructs against suppressing or removing focus styling without providing an alternative visible indicator.
• Prevention of keyboard traps: Users navigating into interactive components—including dialogs, menus, and embedded media players—must be able to exit them using the keyboard alone. Scenarios where keyboard focus cannot navigate away without a pointing device constitute keyboard traps.

Additional information referenced by the publication includes resources hosted by WebAIM on keyboard accessibility and testing protocols.