Skip to main content
Version: v6

Tab element is not keyboard operable

Tab element is not keyboard operable — rule summary
FieldValue
Rule codeManual_Tab_Keyboard_Inoperable
WCAG conformance levelA
WCAG success criterion2.1.1 Keyboard
Must be fixed at sourceNo

Description

We detected a tab element that cannot be operated using a keyboard. Tabs must be fully operable using keyboard navigation alone to ensure accessibility for users who cannot use a mouse or touch screen. This includes being able to focus on tabs using the Tab key and navigate between tabs using arrow keys. Without keyboard operability, users with motor disabilities or those using screen readers will not be able to access the content controlled by these tabs

How to fix

Ensure tabs are implemented to support keyboard navigation using these best practices: Make tabs focusable with tabindex="0" if they're not already focusable elements (like buttons, inputs and links). Implement keyboard controls following the ARIA Authoring Practices:

  • Left/Right arrows to navigate between tabs
  • Home/End keys to navigate to the first/last tab
  • Space or Enter to activate the focused tab