Keyboard Navigation Checklist

Generate a WCAG keyboard QA checklist for any UI component type.

About Keyboard Navigation Checklist

Generate a step-by-step QA checklist for keyboard accessibility testing. Select your component type (modal, dropdown, datepicker, carousel, etc.) and get a scenario-based checklist covering Tab order, focus trapping, Escape key, skip links, and ARIA roles.

How to Use

  1. 1Select the UI component type you want to test (modal, dropdown, carousel, form, navigation, etc.).
  2. 2The checklist is generated instantly with ordered test scenarios.
  3. 3Each scenario includes the action, expected behavior, and the WCAG criterion it covers.
  4. 4Check off items as you test in your browser.
  5. 5Copy or print the checklist for your QA team.

Frequently Asked Questions

Why is keyboard navigation required by WCAG?
WCAG 2.1.1 requires all functionality to be available via keyboard. Users with motor disabilities, power users, and anyone who cannot use a mouse rely on keyboard navigation.
What is a focus trap?
A technique used in modal dialogs: when the modal is open, Tab key cycles only through the modal's focusable elements and cannot reach content behind the overlay.
What are skip links?
Hidden links at the top of the page that become visible on focus (e.g. "Skip to main content"). They let keyboard users bypass repetitive navigation menus.
What WCAG criteria does keyboard testing cover?
2.1.1 Keyboard, 2.1.2 No Keyboard Trap, 2.4.3 Focus Order, 2.4.7 Focus Visible, and 4.1.2 Name, Role, Value.