Level ARobustObsolete in 2.2
4.1.1

Parsing

This criterion is obsolete in WCAG 2.2. It always passes now, so you no longer need to test for it.

In plain English

If you searched for “WCAG 4.1.1”, here is the short answer: you can stop worrying about it. This criterion was removed in WCAG 2.2 and is now treated as always passing. It no longer counts as a failure and you do not need to test it.

It used to require valid HTML, no duplicate id values, properly nested and closed tags, because older assistive technologies read the raw HTML themselves and got confused by mistakes. Today, browsers build a cleaned-up accessibility tree that assistive tech uses instead, so those specific parsing errors no longer create barriers on their own.

What this means for you

  • Do not spend audit time on 4.1.1. It is obsolete in WCAG 2.2.
  • The accessibility problems it used to catch (like a duplicate id breaking a label association) are now caught by the criteria that actually describe the user impact, especially 4.1.2 Name, Role, Value.
  • Valid HTML is still worth keeping for reliability and maintainability, it just is not a WCAG requirement by itself anymore.

A note on versions

4.1.1 still exists in WCAG 2.0 and 2.1. If a contract or older audit references “WCAG 2.1 AA”, it technically includes 4.1.1, but because it always passes, meeting it takes no extra work. For a plain-language look at what actually changed between versions, see our guide on WCAG 2.2 vs 2.1 for ecommerce.

Frequently asked questions

Is WCAG 4.1.1 Parsing still required?+

No. Success Criterion 4.1.1 Parsing was removed (marked obsolete) in WCAG 2.2. It is now considered always satisfied, so you do not need to test against it. It remains in WCAG 2.0 and 2.1 for historical reference only.

Why was 4.1.1 Parsing removed?+

It originally required valid HTML (no duplicate IDs, properly nested tags, complete start and end tags) because old assistive technologies parsed raw HTML themselves. Modern browsers and assistive tech now use the browser's processed accessibility tree instead, so the specific parsing problems this criterion covered no longer cause accessibility barriers. Anything that still matters is covered by other criteria, like Name, Role, Value (4.1.2).

Do I still need valid HTML?+

Valid HTML is still good practice and helps reliability, but it is no longer a WCAG requirement on its own. Focus your effort on the criteria that still apply, especially 4.1.2 Name, Role, Value, which covers the accessibility issues that duplicate IDs or broken markup used to cause.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

Understanding 4.1.1 ↗How to Meet 4.1.1 ↗

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 4.1.1?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit