WCAG 2.2: Why We Have to Wait a Little Longer (an AI perspective)

WCAG 2.2: Why We Have to Wait a Little Longer (an AI perspective)

If you are following the development of web accessibility standards, you may be wondering what is happening with WCAG 2.2, the next update of the Web Content Accessibility Guidelines (WCAG). The last Candidate Recommendation was published in January 2023, and since then, there has been no official announcement of the final release date. So, what is causing the delay and when can we expect WCAG 2.2 to be ready?

What is WCAG 2.2?

WCAG 2.2 is an extension of WCAG 2.1, which was published as a W3C Recommendation in June 2018. WCAG 2.2 aims to provide more guidance and support for users with low vision, cognitive impairments, and limited fine motor skills, as well as some general improvements for web accessibility. It introduces nine new success criteria, seven of which are at Level A and AA, and one existing criterion (Focus Visible) that has moved from Level AA to Level A.

WCAG 2.2 is intended to be backward compatible with WCAG 2.0 and WCAG 2.1, meaning that content that conforms to WCAG 2.2 also conforms to the previous versions. The Accessibility Guidelines Working Group (AGWG), a working group of the W3C that develops WCAG, expects that WCAG 2.2 can provide an alternate means of conformance for policies that require WCAG 2.0 or WCAG 2.1.

What is causing the delay?

The AGWG originally planned to publish WCAG 2.2 by the end of 2020, but due to various factors, the timeline has been pushed back several times. Some of the reasons for the delay include:

  • The need for more feedback and implementation experience from the web community on the new success criteria and their practical application.
  • The complexity and interdependence of some of the new success criteria, such as Focus Appearance and Dragging.
  • The impact of the COVID-19 pandemic on the availability and productivity of the AGWG members and reviewers.
  • The simultaneous development of WCAG 3.0, a major overhaul of the web accessibility standard that requires a lot of attention and resources from the AGWG.

When can we expect WCAG 2.2 to be ready?

The current estimate is that WCAG 2.2 will be published as a W3C Recommendation in mid to late 2023. However, this is not a guarantee, as there may be further changes or issues that need to be resolved before the final version is ready. The AGWG encourages web developers, designers, testers, and users to review the latest candidate recommendation and provide feedback on any aspect of WCAG 2.2.

Why does accessibility matter for Fortune 500 companies and enterprises?

Accessibility is not only a moral obligation, but also a strategic advantage for large and influential organizations. By making their websites, products, and services accessible to people with disabilities, Fortune 500 companies and enterprises can:

  • Reach a wider and more diverse customer base. According to the World Health Organization, more than one billion people live with some form of disability, representing about 15% of the world's population. These people have different needs, preferences, and expectations that can be met by accessible design and innovation.
  • Enhance their reputation and brand image. Accessibility demonstrates social responsibility, inclusion, and respect for human rights. It can also help attract and retain talent, investors, partners, and regulators who value diversity and equality.
  • Reduce legal risks and costs. Accessibility is increasingly becoming a legal requirement in many countries and regions, such as the United States, the European Union, Canada, Australia, and Japan. Failing to comply with accessibility standards can result in lawsuits, fines, penalties, and negative publicity.

Accessibility is not a one-time project or a nice-to-have feature. It is an ongoing process that requires commitment, collaboration, and continuous improvement. By adopting WCAG 2.2 as a guideline and a best practice, Fortune 500 companies and enterprises can ensure that they are on the right track to achieving accessibility excellence.

Source: Conversation with Bing, 4/21/2023

Since taking on my new role mid-2022, I've haven't been as involved with the AGWG. I miss it. I've also been dabbling with AI recently (who hasn't). So why not feed it a prompt on the status of WCAG 2.2 and any delay. The above is the result of the prompt. While a decent summary, I don't think Accessibility SMEs have anything to worry about (yet). :)

Thank you to all of the sources that were pulled in by AI.

References:

Web Content Accessibility Guidelines (WCAG) 2.2

WCAG 2.2 Status Update: What’s the Hold-Up? | Level Access

Are we there yet? WCAG 2.2 is at the Candidate Recommendation stage ...

Why WCAG 2.2 is still in the oven | Deque


WCAG 2.2 Status Update: What’s the Hold-Up? | Level Access

Web Content Accessibility Guidelines (WCAG) 2.2 - W3

WCAG 2.2 Update: What's The Hold-Up? - boia.org

Why WCAG 2.2 is still in the oven | Deque

WCAG 2.2 Delay - When Will It Arrive? - ADA Site Compliance

要查看或添加评论,请登录

Marc Johlic的更多文章

  • React Accessibility

    React Accessibility

    Great news for the React community: a new Accessibility page has been added to the official React docs! Lot's of great…

    1 条评论
  • TPAC 2014

    TPAC 2014

    Day Two of WCAG WG meetings at TPAC 2014 - lots of great ideas and discussions!

社区洞察