Robust · Level A · Introduced in WCAG 2.0

WCAG 4.1.1: Parsing (legacy)

Published by whatisADA / Grow Wild Agency · Updated

Legacy reference: Parsing was removed from WCAG 2.2. This page supports version-specific reporting and explains how to handle existing 2.0/2.1 references.

What this criterion means

Parsing was removed from WCAG 2.2. W3C now says the legacy 2.0/2.1 criterion is always satisfied for HTML or XML. Markup problems that break names, relationships or operation should be reported under the relevant retained criteria.

A practical example

An older procurement template includes a Parsing row. Record the required WCAG version and the applicable reporting guidance instead of silently deleting the row; separately repair a duplicate ID that makes a label point to the wrong input.

How to check it

  1. Identify the exact WCAG version required by the evaluation or contract.
  2. For a 2.0/2.1 report on HTML or XML, follow W3C's current always-satisfied note and document the version and technology.
  3. Investigate actual user-facing effects of markup errors and report them under the relevant retained criteria.

What can be missed

Do not list Parsing as an active WCAG 2.2 A criterion. Equally, removal from 2.2 does not mean broken HTML associations or duplicate accessible identifiers are harmless.

Record your test

Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.

These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.

Primary sources and scope

This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.