Robust -- WCAG Principle 4

What Does "Robust" Mean?

Robust is the fourth and final top-level principle in WCAG 2.2 ^[1], closing out the POUR acronym -- Perceivable, Operable, Understandable, Robust. The principle states that content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies. Where Perceivable, Operable, and Understandable govern the user-facing surface of the page, Robust governs the contract between the page and the software that reads it: the browser, the screen reader, the voice-control engine, the switch interface, the braille display, and whatever user agent ships next year that nobody has written yet. A page fails the principle when it renders correctly in a sighted developer's browser but exposes something ambiguous, missing, or malformed to the accessibility tree that every assistive technology consumes.

The failure mode is concrete: a custom toggle built from a <div> with a click handler exposes no role and no state, so a screen reader announces it as a generic group rather than "button, pressed"; a modal dialog that omits role="dialog" and aria-modal="true" leaves virtual-cursor users free to navigate the obscured background content; an inline form-validation message injected into the DOM after submission is never announced because it is not wired to a live region, leaving a screen-reader user staring at a form that silently refused to submit. Each is a robustness failure because the visual rendering is fine but the programmatic surface -- the machine-readable name, role, state, and status stream that assistive technology depends on -- is missing or wrong.

The principle decomposes into a single guideline, 4.1 Compatible, which in WCAG 2.2 contains two success criteria: 4.1.2 Name, Role, Value at Level A and 4.1.3 Status Messages at Level AA. Readers coming from WCAG 2.0 or 2.1 should note that 4.1.1 Parsing was removed in WCAG 2.2 and is no longer a success criterion ^[1]; the requirement it used to carry -- that start tags, end tags, and attributes be well-formed and nesting correct -- was made redundant by modern HTML parsers, which recover from malformed markup deterministically, and by the HTML specification's own conformance requirements. A build that would have tripped 4.1.1 in 2018 is no longer a WCAG failure in 2.2, though it may still be an HTML conformance bug worth fixing on its own merits. This is a common point of confusion in audit reports carried over from older rulesets.