What WCAG 4.1.1 Requires
Obsolete in WCAG 2.2: markup previously had to be free of duplicate IDs and correctly nested tags so assistive technology could parse it reliably. Modern browsers and assistive tech handle most parsing errors, so this criterion was retired, though clean markup is still good practice.
Because it is obsolete, WCAG 4.1.1 is not counted in our WCAG 2.2 checkers, but it still applies to WCAG 2.0 and 2.1 targets and is worth keeping in mind.
Can AccessBell Test This Automatically?
Not fully. Like most WCAG criteria that depend on meaning or context, this one needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it never gets missed.
How to Test It by Hand
Run an HTML validator; while no longer a WCAG 2.2 requirement, duplicate IDs and invalid nesting can still cause real assistive technology bugs.
Common Failures
- Duplicate id attributes on the same page confuse label associations and ARIA references.
Related Criteria in Compatible
WCAG 4.1.1 Questions
What does WCAG 4.1.1 require?
Obsolete in WCAG 2.2: markup previously had to be free of duplicate IDs and correctly nested tags so assistive technology could parse it reliably. Modern browsers and assistive tech handle most parsing errors, so this criterion was retired, though clean markup is still good practice.
Can AccessBell test WCAG 4.1.1 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 4.1.1?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 4.1.1 Parsing (obsolete in WCAG 2.2) (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.