a11y/tabs-keyboard

Dlaczego

Screen reader users who hear "tab list" press the arrow keys, because that is what the role promises. If every tab is a separate Tab stop and arrows do nothing, the widget behaves unlike its announcement and keyboard users tab through every tab to reach the panel.

Poprawka

Roving tabindex: the selected tab has tabindex="0", the others -1. Arrow keys move focus (and select, in automatic activation) with wrapping; Home and End go to the first and last tab; Tab moves into the panel. Use manual activation (Enter or Space selects) when showing a panel is slow. Set aria-orientation="vertical" for a vertical list.

Przykłady

tablist.addEventListener('keydown', (e) => {
  const next = { ArrowRight: i + 1, ArrowLeft: i - 1, Home: 0, End: tabs.length - 1 }[e.key]
  if (next === undefined) return
  e.preventDefault()
  select((next + tabs.length) % tabs.length)
})

Źródła

• WAI-ARIA Authoring Practices, Tabs pattern (keyboard interaction)

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain a11y/tabs-keyboard