Why WCAG 2.2 removed 4.1.1 Parsing, and what it means for your reports

For years, validator output filled accessibility reports under one heading: 4.1.1 Parsing. Duplicate ids, unclosed tags, attributes repeated on the same element. Most of it had no effect on anyone, and the W3C has now said so formally.

What changed

In WCAG 2.2, success criterion 4.1.1 is marked "Obsolete and removed". It is gone from the 2.2 standard.

For WCAG 2.0 and 2.1, which many laws still reference, the W3C added a note to the Understanding document instead: "This success criterion should be considered as always satisfied for any content using HTML or XML."

Why

4.1.1 was written in 2008, when assistive technology sometimes read a page's HTML directly and could trip over broken markup. The W3C's current explanation is that the HTML standard now tells browsers exactly how to handle incomplete tags, wrong nesting, duplicate attributes and non-unique ids, and that assistive technology works from what the browser builds. Its conclusion: "In practice, this criterion no longer provides any benefit to people with disabilities in itself."

What still matters

The important words are "in itself". Some of the old 4.1.1 failures still break things for people, and they are now caught by the criteria that describe the actual harm:

• Duplicate ids that something refers to. If two elements share id="email" and a <label for="email"> points at it, the label may name the wrong field. That's a 4.1.2 Name, Role, Value or 1.3.1 Info and Relationships failure.
• Broken ARIA references. aria-labelledby or aria-describedby pointing at a missing or duplicated id leaves a control without the name or description the author intended.
• Invalid nesting that changes meaning. An <li> outside any list, or a table with rows that break its header structure, loses relationships that 1.3.1 requires.

A duplicate id on two decorative divs that nothing refers to harms nobody. It isn't worth a ticket.

What this means for your reports

• Scanner results: AccessiSight no longer reports anything under 4.1.1. Duplicate ids that are referenced by a label or ARIA attribute are reported under 4.1.2, because that's where the harm is.
• Conformance reports for WCAG 2.0 or 2.1: the W3C note gives you a documented basis for treating 4.1.1 as satisfied for HTML content. Cite it in the remarks.
• Section 508: the US Section 508 standards incorporate WCAG 2.0 by reference. If you report against 508 for a federal buyer, check how that agency wants 4.1.1 handled rather than assuming.

The fastest way to clean up an old report is to delete the 4.1.1 section and check whether any of its items were really one of the three problems above.

Sources: WCAG 2.2 and Understanding 4.1.1 Parsing (W3C).