Search

Items tagged with: WCAG




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 is now published as a Web Standard (“W3C Recommendation”)!

For an introduction to WCAG and a link to WCAG 2.2, see the WCAG 2 Overview
w3.org/WAI/standards-guideline…

There are a few updates in the WCAG 2 FAQ
w3.org/WAI/standards-guideline…

See new "In briefs" in
What's New in WCAG 2.2

w3.org/WAI/standards-guideline…

#WCAG #WCAG2 #a11y


.@w3c WCAG should not be developed/designed for the benefit of #accessibility testing vendors. It is there to improve the user experience of disabled people.

#web #a11y #politics #WCAG










"Regardless of what accessibility conformance level you target, do not arbitrarily open links in a new window or tab. If you are required to do so anyway, inform users in visible text." adrianroselli.com/2020/02/link… via @aardrian #UIDesign #IXD #a11y #links #wcag #tips