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 unique IDs for active elements. 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-09 | ✗→✓ | ▲ Improved | -3% | 0% |
| case-01 | ✓→✓ | = Same ✓ | 1% | 0% |
| case-02 | ✓→✓ | = Same ✓ | 1% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 0% | 0% |
| case-04 | ✓→✓ | = Same ✓ | -26% | 0% |
Duplicate IDs on active elements can cause browsers and assistive technologies to skip items, misdirect focus, or fail to trigger the correct action.
Search for duplicate id attributes on focusable or active HTML elements.
Assign a unique id to each active element to ensure correct focus handling and accessibility.
Explain how unique IDs on active elements prevent navigation errors for keyboard and screen reader users.
Review the rendered markup and interactive states that affect Use unique IDs for active elements. 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/duplicate-id-active
Other measured skills in the registry, with their headline benchmark lift.