# Keyboard Accessibility Audit

Keyboard accessibility means users can operate a digital experience without a mouse.

In WCAG audits, this is tested manually because tools cannot fully evaluate whether the journey works.

## What to test

Teams should test:

*   Tab and Shift+Tab.
    
*   Enter and Space activation.
    
*   Escape behavior.
    
*   Arrow-key behavior in widgets.
    
*   Focus order.
    
*   Focus visibility.
    
*   Modal focus management.
    
*   Menus and overlays.
    
*   Form validation.
    
*   Responsive layouts.
    

## Common failures

Keyboard failures include unreachable controls, controls that focus but do not activate, hidden focus, keyboard traps, skipped form fields, broken modal behavior, and shortcuts that trigger unexpectedly.

## Evidence

A good audit finding should include the exact keyboard path, expected behavior, actual behavior, WCAG mapping, user impact, and retest method.

## Conclusion

Keyboard accessibility is not optional polish. It is core operability.

If users cannot complete the journey without a mouse, the issue should be documented, remediated, and retested.

Read the original guide on IAAP Audit: https://iaapaudit.com/blog/keyboard-accessibility-wcag-audit-testing