Review rendered HTML for duplicate IDs used by ARIA attributes, which connect elements to labels and descriptions for assistive technology. Identify ambiguous references, correct IDs and their links, and explain how to verify the changes.
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.
Checks for duplicate IDs referenced by ARIA attributes and helps correct them so labels and descriptions connect to the intended elements. ARIA attributes communicate interface roles and states to assistive technology. The skill examines references such as aria-labelledby. When multiple elements share an ID, it reviews both the target IDs and the attributes that reference them. It also explains why duplicates can cause a different label or description to be read aloud.
Use it when a screen reader reads an unexpected description, or when reviewing a screen that repeats the same component. It examines rendered HTML and states during interaction, identifying the specific elements involved. Where needed, the review also covers native HTML semantics, keyboard operation, and focus movement.
There are no special notes.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
When 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/rules/accessibility/duplicate-id-aria
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.