Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use unique IDs for ARIA references. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
63
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/duplicate-id-aria/SKILL.mdWhen ARIA attributes point to duplicate IDs, assistive technologies may read the wrong label or description, providing misleading information to the user.
Identify elements where an ARIA attribute references an id that appears multiple times in the DOM.
Ensure all elements referenced by ARIA attributes have unique IDs and update the references accordingly.
Explain how unique IDs are essential for establishing reliable relationships between ARIA attributes and their targets.
Review the rendered markup and interactive states that affect Use unique IDs for ARIA references. 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-aria
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.