This check finds duplicate id values when an ARIA relationship such as aria-labelledby, aria-describedby, aria-controls, or aria-owns points to that ID.
Why this matters
An ID reference is expected to resolve to one element. When the same value appears more than once, a browser or assistive technology may use the wrong label, description, panel, or control. The resulting experience can be ambiguous even when the page looks correct visually.
How to fix it
- Search the rendered DOM for every duplicated ID, including IDs generated by reusable components.
- Generate a stable unique ID for each component instance and use the same value in the associated ARIA attribute.
- Avoid copying static IDs into repeated modal, accordion, form, or tab markup.
- Confirm that each space-separated ARIA ID reference points to one existing element.
When the finding appears across many URLs, fix the shared component or layout that produces it instead of patching generated HTML page by page. Recheck representative templates and responsive states after deployment so the correction does not create a regression elsewhere.
How to verify the fix
Reload the page, inspect the rendered DOM rather than only the source template, and confirm that each referenced ID occurs exactly once. Then test the affected control with a keyboard and an accessibility tree inspector.
Keep before-and-after evidence for the affected URL, original output, correction, and verification method. If markup changes after load, test consent states, localization, responsive variants, and client-side navigation because the initial HTML and rendered DOM can differ.