Delays in WCAG 2.2: A Necessary Step for Better Standards
Written on
Understanding the Delays of WCAG 2.2
What’s causing the hold-up with WCAG 2.2? Originally scheduled for release in the summer of 2021, the new timeline has shifted to late 2022. This ongoing delay raises questions about the reasons behind it.
The Accessibility Guidelines Working Group (AGWG) has hinted at the upcoming WCAG 2.2, but they emphasize that further revisions are needed. They describe it as "mostly complete" but still require additional adjustments and documentation.
While my impatience grows, I recognize the importance of this upcoming release. It will serve as a key recommendation for web content accessibility and is expected to be the final version in the WCAG 2.0 series. With WCAG 3.0 years away, the pressure to finalize this version is significant.
Challenges to the Release
Upon reviewing feedback from contributors, it's clear why WCAG 2.2 faces continuous delays. Aspects such as standards, examples, documentation, and terminology are all under scrutiny.
This level of critique is not inherently negative; it indicates active engagement from contributors. However, it can lead to lengthy discussions, slowing down the process. The AGWG follows a waterfall method for releasing updates, meaning any necessary changes could take considerable time, especially since WCAG 2.1 has just reached its four-year mark.
Furthermore, many organizations are legally bound to comply with the latest AGWG recommendations, necessitating a zero-tolerance approach to inaccuracies in standards. An incomplete or incorrect set of guidelines could expose numerous companies to legal risks.
Wilco Fiers, a project manager for WCAG 3.0 and a key member of the Accessibility Conformance Testing (ACT) Task Force, shared insights into the future of WCAG in an interview. You can listen to his thoughts here:
In his article, "Why WCAG 2.2 is still in the oven," Fiers discusses the lengthy refinement process for Success Criterion 3.3.7: Accessible Authentication, a new Level A standard. He points out the challenges of finding appropriate language for exceptions to this criterion, emphasizing the need for a balance between accessibility and security.
He also mentions that Success Criterion 2.4.11: Focus Appearance, one of the new additions to WCAG 2.2, was particularly complex to formulate.
This complexity highlights why the finalization of WCAG 2.2 has faced numerous setbacks. The AGWG is committed to considering all conditions and exceptions, which inevitably takes time.
Reassessing the Current Approach
Given the ongoing delays and the potential risks of premature releases, is it wise to stick to this trajectory? The immediate legal implications following a new WCAG release create a strong incentive for delays. Once released, there is no turning back.
For companies bound by AGWG's releases, renegotiating contractual obligations could be beneficial. While I advocate for accessibility, I believe it's imprudent to tie oneself strictly to compliance standards, especially with a trigger mechanism. Instead, companies might consider undergoing regular accessibility audits and addressing findings systematically.
The AGWG is reportedly making changes to its processes, which should ideally come to fruition with WCAG 3.0.
Looking Ahead to WCAG 3.0
With the advent of WCAG 3.0, the AGWG intends to adopt a more iterative approach, releasing smaller updates more frequently once the standard is finalized. However, it's crucial to note that WCAG 3.0 will not replace WCAG 2.2; instead, they will coexist as independent standards.
This could provide an opportunity for companies legally obligated to follow AGWG guidelines to comply with WCAG 2.2 while WCAG 3.0 undergoes refinement, even after its release.
Accepting the Delays
I’m personally okay with the delays for WCAG 2.2 for several reasons:
- The standards will be better refined.
- Accessibility teams will have more time to familiarize themselves with the new Success Criteria.
- Importantly, as accessibility advocates, we don’t wait for compliance standards to drive necessary changes within our teams.
Ultimately, the delays may push back the much-anticipated WCAG 3.0 release, which is needed for future progress.
Let’s extend some understanding to the AGWG and the ACT Task Force. They face a challenging task and are striving to produce robust standards, which takes time.
Additional Resources
[Why WCAG 2.2 is still in the oven by Wilco Fiers](#)
[WCAG 2.2 — Editor’s Draft](#)
[WCAG 2.2 — Working Draft](#)
[WCAG 3.0 — Working Draft](#)
[My articles on WCAG](#)
- [WCAG 3.0: What you need to know about the future of accessibility standards](#)
- [WCAG 2.2 updates: what changes may be quickly coming](#)
- [WCAG 2.2: Visible Controls — what it means and how to meet it](#)
- [WCAG 2.2: Redundant Entry — what it means and how to meet it](#)
- [The accessibility no-win scenario: autocomplete and help text](#)
The first video, "The 6 WCAG 2.2 AA changes you need to implement right away," provides a concise overview of critical changes to implement for compliance.
The second video, "WCAG 2.1 Article 2.2.1," explains specific guidelines that are essential for understanding the new standards.