WCAG 2.1 SC 4.1.1: Parsing (Level A)
4.1.1 Parsing (Level A) — what it requires, a common failure example, and how to fix it. Part of WCAG 2.1's 4.1 Compatible guideline under the Robust principle.
WCAG 2.1 guidelines hub → Robust → 4.1 Compatible
4.1.1 Parsing (Level A)
Compatible means your markup works correctly with the range of user agents and assistive technologies people actually use — current browsers, screen readers, voice control software, switch devices — including tools you didn’t test against directly, because they all rely on standards-compliant, well-formed markup to do their job.
This page is educational technical reference material, not legal advice. Meeting WCAG 2.1 does not by itself determine legal compliance with the ADA or any other law — consult qualified counsel for legal risk questions.
Plain-language explanation: In WCAG 2.1, this criterion required markup to be well-formed — complete start/end tags, correct nesting, no duplicate attributes, unique IDs — so that any tool parsing the page would interpret it consistently.
Common failure: Two elements on the same page share the same id attribute (a common copy-paste error in templated product cards), which can cause a screen reader’s aria-labelledby or aria-describedby reference to point at the wrong element, or an unclosed <div> throws off how assistive tech interprets the structure around it.
Remediation: Run markup through an HTML validator (e.g. the W3C Markup Validator) and fix duplicate IDs, unclosed tags, and incorrect nesting.
A note for a WCAG 2.1 reference specifically: WCAG 2.2 removed SC 4.1.1 entirely. The W3C’s stated reason is that assistive technology no longer parses raw HTML itself — it relies on the browser’s own parsing, and modern browsers handle malformed markup consistently via the HTML5 parsing specification, so the failure modes 4.1.1 was written to catch are now either nonexistent or already covered by other criteria (like 4.1.2). If you’re conforming specifically to WCAG 2.1 — for a policy or contract that names that version — 4.1.1 is still in scope; if you’re free to target 2.2, this criterion no longer applies, though clean, valid markup is still good practice.
In this guideline — 4.1 Compatible: 4.1.1 Parsing (A) · 4.1.2 Name, Role, Value (A) · 4.1.3 Status Messages (AA)
Next: 4.1.2 Name, Role, Value (A) →
↑ Back to the Robust overview · Full WCAG 2.1 wiki
See a sample report or check pricing — $890 one-time, $99/month for ongoing re-checks after fixes ship.
This page is educational content about technical accessibility practice, not legal advice. Meeting WCAG 2.1 does not guarantee legal compliance with the ADA or any other law. Consult qualified counsel for legal risk questions.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.