Coming Next: WCAG 2.2

Posted by Kim Krause Berg cre8pc    Updated

It is a myth that website accessibility is a once and done exercise. Similar to how SEO’s follow every Google algorithm update and chase the results to see what blew up, accessibility for websites and apps is also in a constant state of fluctuation.

In other words, you can’t make a change in your code and think it will last forever.

Computer devices change. Browsers change. Technology changes. Standards change. Rules, guidelines and laws change, in every state, province and country.

How business is conducted online changes too.

These changes are driven by me and you. Your children. Your families. Friends. Neighbors. Customers. Clients. Employees.

Accessibility Design Includes You (Sooner or Later)

Accessibility design is referred to as inclusive design because we not only must learn how to use the web, we may also need help to use it at all.

We grow older. We are unique. We are born with disabilities and sometimes develop them over the course of our lives. We break an arm, or hand or suffer from depression or a temporary emotional freak out from stress or an emergency.

We need our computers in different ways in those crazy moments and normal daily ones. It is out of this understanding and respect for you, that website accessibility testing is done. It is a not an automated quick fix by AI.

Because you are not robots.

WCAG 2.2

The first draft of WCAG 2.2 was made available on August 11. To get an idea of the work involved in changing accessibility guidelines, take a look at the comments at GitHub.

It is backwards compatible to WCAG 2.0 and WCAG 2.1. There are nine new success criteria in WCAG 2.2, which is expected to be officially adapted later this year.

New Success Criteria for WCAG 2.2

WCAG 3.0 is On Deck

It will NOT be backwards compatible. In fact, it is a do-over.

The WCAG3.0 August 27 Editor’s Draft can be read now.

“WCAG 3.0 uses a framework that allows it to address more disability needs than WCAG 2.X, as well as address publishing requirements and emerging technologies on the web such as web XR (augmented, virtual and mixed reality) and voice input. It will also provide non-normative information about the ways web technologies need to work with authoring tools, user agents, and assistive technologies.”

Fasten your seat belts.