WCAG 2.2 removed SC 4.1.1, Parsing (Level A). I maintain that valid markup has important benefits despite no longer being required. We may find it possible to write good software without static analysis, construct a building without blueprints, or make an accessible website without validation. They remain good practices.
WCAG’s normative text describes outcomes, not how to achieve them. Validation is but one part of the process of achieving the necessary outcomes.
Let’s not interpret the removal of SC 4.1.1 as permission to ship known errors.
Originally posted on seirdy.one/notes/2023/10/06/wc… (POSSE). #accessibility #WCAG
WCAG 2.2 and validation
WCAG 2.2 removed SC 4.1.1, Parsing (Level A). I maintain that valid markup has important benefits despite no longer being required. We may find it possible toSeirdy's Home
This entry was edited (1 year ago)
Matt Campbell
in reply to Seirdy • • •mathew
in reply to Matt Campbell • • •@matt Apparently the W3C Nu Validator supports web components custom elements.
github.com/validator/validator…
Removing validation from WCAG seems wrong-headed to me. How can you guarantee accessibility without standards conformance? Testing on literally every browser and device isn’t feasible.
Support Web Components Standard · Issue #211 · validator/validator
GitHub