Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use appropriate tabindex values. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 11% | 0% |
| case-23 | ✗→✓ | ▲ Improved | -24% | 0% |
| case-02 | ✓→✗ | ▼ Worse | -21% | 0% |
| case-14 | ✓→✓ | ＝ Same ✓ | 10% | 0% |
| case-08 | ✓→✓ | ＝ Same ✓ | -10% | 0% |
Incorrect tabindex values can create a confusing navigation experience, making it difficult for keyboard users to predict where focus will move next.
tabindex="0" for custom interactive elementstabindex="-1" for elements that should only be focusable via scriptCheck for any positive tabindex values and ensure custom interactive elements are focusable.
Remove positive tabindex values and use tabindex="0" or -1 appropriately.
Explain why positive tabindex values are problematic for keyboard navigation and user experience.
Review the rendered markup and interactive states that affect Use appropriate tabindex values. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/tabindex
Other measured skills in the registry, with their headline benchmark lift.