Skip to main content
متصفحك قديم جدًا لعرض هذا الموقع بشكل صحيح. يُرجى التحديث إلى أحدث إصدار من Chrome أو Edge أو Firefox أو Safari.
Back to WCAG Database
Level AWCAG 2.0

4.1.1 Parsing

In content implemented using markup languages, elements have complete start and end tags, are nested according to specification, do not contain duplicate attributes, and IDs are unique.

Last reviewed: September 9, 2026

Understanding 4.1.1

4.1.1 Parsing was formally removed from WCAG 2.2 and marked obsolete by the W3C Working Group, which determined it no longer has any testable failure conditions. It originally existed because early assistive technologies parsed HTML directly, and malformed markup, such as unclosed tags, duplicate IDs, or improper nesting, could cause a screen reader to misread or fail on a page. Modern browsers and the HTML5 specification now mandate a standard error-correction algorithm for parsing malformed markup, so every user agent, including assistive technology built on modern browser engines, handles it the same predictable way.

How to Meet It

No action is required to conform to 4.1.1 under WCAG 2.2 conformance claims; the criterion has been removed and is not evaluated. This is because HTML5 defines a mandatory parsing algorithm that all conforming browsers must implement, so malformed markup is now handled consistently across user agents rather than being ambiguous or failure-prone as it could be in the pre-HTML5 era. Writing valid, well-formed HTML remains good engineering practice for maintainability and interoperability, but it is no longer a distinct WCAG conformance requirement.

Frequently Asked Questions

Should I remove 4.1.1 checks from my accessibility test suite or audit checklist?

Yes, for WCAG 2.2 conformance claims: 4.1.1 no longer exists as a success criterion in WCAG 2.2 and auditors should not cite it. If you still must conform to WCAG 2.0 or 2.1 under a contractual or legal requirement, it remains part of those versions and should still be tested there.

Does this mean HTML validity no longer matters for accessibility?

It matters less for parsing-specific failures, but duplicate IDs can still break other criteria. For example, duplicate id values can cause aria-labelledby/aria-describedby references or for/id label associations to resolve incorrectly, which can fail 1.3.1 or 4.1.2. Markup validity is still worth maintaining even though 4.1.1 itself is gone.

Related Success Criteria

4.1.2 Name, Role, Value4.1.3 Status Messages

Quick Facts

  • Criterion4.1.1
  • LevelA
  • IntroducedWCAG 2.0

Automate Compliance

AccessiSight automatically scans and identifies 4.1.1 issues in your codebase.

Try Scanner Free