ubricHelp

Why do duplicate IDs break accessibility labels?

Rubric check: duplicate ID used by a label (check id a11y_duplicate_id_aria)

A duplicate ID used by a label means two or more elements share an id, and a <label for>, aria-labelledby or aria-describedby points at it. Browsers use the first match, so a screen reader may read out the wrong label or description.

Free, no card. Your report opens with this check first.

Why it matters for SEO

Search engines don't rank pages on duplicate IDs. The cost falls on people using assistive technology, who may hear the wrong name for a field or button and fill in a form wrongly.

This often happens when a page repeats a component, such as two newsletter forms or two copies of the menu for mobile and desktop, each with the same hard-coded IDs.

Does this matter for ChatGPT and AI Overviews?

The direct effect on ChatGPT or AI Overviews is likely small. Their answers come from your text, not your ARIA wiring.

Browser agents that fill in forms for people read the same accessibility labels as screen readers, so a label tied to the wrong field can send them wrong too. This check shares a capped allowance with Rubric's other accessibility checks.

How Rubric scores it

MinorMinor checks cost a quarter to a half of a standard check when they fail.

Why this tier: A label pointing at a shared ID can name the wrong field for screen-reader users.

It is judged on every page Rubric scores.

Every Rubric score starts at 100. When this check fails, it takes up to 3 points off. Even one failing page costs at least 1.5 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.

This is one of 5 accessibility checks. Together they can take off at most 18 points, so a site isn't marked down many times for one kind of problem.

All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.

This check doesn't cap your score. It only takes off its own points.

From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).

How common it is

Found on 43 of 300 sites where Rubric could judge it (14%). That is 41 of 287 judged sites in Rubric's 313-site test set and 2 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.

14% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)

Real sites: people checked 19 of its findings by hand and 1 was wrong (5.3%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.

Latest review round: 0 of 89 findings judged were still wrong after the last fix.

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. View the page source and search for the ID named in the report to see which elements share it.
  2. If two copies of the same form appear on one page (often a widget in the footer plus one in the content), remove one, or check whether your form plugin offers a setting for unique field IDs.
  3. If a theme or page-builder block hard-codes the ID, change it in that block's Advanced > HTML ID or CSS ID field so each copy has its own.

Shopify

  1. View the page source and search for the duplicated ID.
  2. A common cause is a section added twice, such as two newsletter sections, where the theme builds IDs without the section ID. Edit the section's Liquid file so the ID includes {{ section.id }}, for example id="Email-{{ section.id }}".
  3. If an app injects the element, ask the app developer.

Webflow

  1. Open the page in the Designer and select the elements that share the ID.
  2. In Element settings, change the ID field so each one is unique.
  3. If the element sits in a component used twice on the page, avoid a fixed ID in the component, or expose the ID as a component property. Publish.

Custom code

Give every element a unique ID, and point each label at its own field:

html
<label for="email-footer">Email</label>
<input id="email-footer" type="email">
<label for="email-hero">Email</label>
<input id="email-hero" type="email">

In component frameworks, generate IDs per instance (for example useId() in React) rather than hard-coding them.

More accessibility checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.