Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing templates, rendered HTML, or shared components related to Make tabs keyboard navigable. Validate the final browser-facing markup, not just the source framework abstraction.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | 6% | 0% |
| case-15 | ✓→✓ | ＝ Same ✓ | -14% | 0% |
| case-01 | ✓→✓ | ＝ Same ✓ | -21% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | -11% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | -32% | 0% |
Incorrectly implemented tabs trap keyboard users or leave screen reader users unable to understand the relationship between tabs and their content.
Verify tabs use tablist/tab/tabpanel roles, aria-selected state, and arrow key navigation between tabs.
Implement tabs with role='tablist', role='tab', role='tabpanel', aria-selected, and proper keyboard interaction patterns.
Explain the ARIA tabs design pattern and how proper implementation ensures keyboard and screen reader accessibility.
Review templates, server-rendered HTML, and shared components that output markup related to Make tabs keyboard navigable. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/tabs-accessibility
Other measured skills in the registry, with their headline benchmark lift.