Obligatory WCAG 2.2 Launch Post

Created on November 12, 2023 at 11:31 am

Obligatory WCAG 2.2 Launch Post

Updated October 12, 2023 DATE , originally posted October 8, 2023 DATE ; 0 Comments ORG

It seems everybody who dabbles in digital accessibility is blogging about WCAG 2.2 CARDINAL now that it finally went live. This is my obligatory post, but I am not promoting it because there is already so much noise and much of the content is regurgitated.

If you are not aware, WCAG 2.2 CARDINAL became a W3C Recommendation (a standard) on 5 October 2023 DATE . That was about a year later DATE than originally suggested. It would have been sooner but for some objections on two CARDINAL WCAG 2.0 and WCAG 2.1 CARDINAL Success Criteria. This is part of why all those WCAG 2.2 CARDINAL posts landed immediately — they had already been written and were just waiting since the new WCAG 2.2 CARDINAL SCs were stable.

The launch date was also telegraphed a few days early DATE , so that gave an extra head start.

The Links

The only reason to write this post, after all.

Mine

I have already written about WCAG 2.2 CARDINAL :

The 411 CARDINAL on 4.1.1 CARDINAL , from December 2022 DATE and perhaps forever current. It applies to WCAG 2.1 CARDINAL since WCAG 2.1 CARDINAL was updated on 21 September DATE to assert 4.1.1 CARDINAL is always satisfied for HTML and XML ORG documents.

, from December 2022 DATE and perhaps forever current. It applies to WCAG 2.1 CARDINAL since WCAG 2.1 CARDINAL was updated on 21 September DATE to assert 4.1.1 CARDINAL is always satisfied for HTML and XML ORG documents. What’s New in WCAG 2.2 CARDINAL , from August 2020 DATE and wildly out of date (but useful if you want to see what was chipped away from first ORDINAL drafts).

W3C

More importantly, W3C has written about WCAG 2.2 CARDINAL :

Everyone Else

And now some of the others. I am not linking to posts or articles on Medium, LinkedIn ORG , or other inaccessible platforms, nor am I linking to PDFs because really why would anyone do that, and definitely no overlay vendors. These are without any endorsement on my part:

Also, while readers of my stuff know I have been tracking and poking WCAG 2.2 for years now, I am not going to lay claim to having had a hand in it. Unlike others (side-eyes UserWay).

I may add more links later.

Connecting to blog.lzomedia.com... Connected... Page load complete