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 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.

Interact

You can interact by sending webmentions or by visiting a syndicated copy of this post.

Syndication

This post has been syndicated to:

• The Fediverse
• IndieNews

Web­mentions

This site supports Webmentions, a backlink-based alternative to traditional comment forms.

Send a Webmention Toggle 4 Webmentions

Webmentions received for this post appear in the following list after I approve them. I sometimes send Webmentions to myself on behalf of linking sites that don’t support them. I auto-replace broken links with Wayback Machine snapshots, if they exist.

Feel free to contact me directly with feedback; here’s my contact info