Creating an accessible website is a significant and ongoing endeavor, but before embarking on this journey, it's crucial to grasp the basics of compliance. Compliance levels can be confusing, so let's break it down.
Understanding WCAG
First things first, what's WCAG? It stands for Web Content Accessibility Guidelines, a set of technical standards that underpin almost all accessibility laws and regulations globally. These guidelines cover content and technical accessibility, and they are quite extensive. I read almost all the documentation to prepare for my Web Accessibility Specialist exam from IAAP, and it took hours a week for months! However, if you're a content writer or a website manager, you won't need to read it yourself. Experts like myself break it down for you!
Breaking Down Compliance Levels
Now, let's unravel the intricacies of compliance levels. The level of compliance consists of two components: the version number and letters. There are two primary versions of WCAG—1 and 2. Version 1 is entirely obsolete, so you'll likely never come across it. The current version is the second one, which includes 2.0, 2.1, and 2.2. These iterations introduce new Success Criteria, which are individual measurable requirements that build upon one another. To meet 2.1, you must first fulfill 2.0, and the same goes for 2.2.
Understanding the Letters: A, AA and AAA
The letters A, AA, and AAA represent different levels of conformance, and each Success Criteria falls into one of these three categories. The WCAG authors devised these levels based on the end-user impact and the level of difficulty in meeting the requirement.
- A: These requirements address the most essential accessibility needs and have the highest end-user impact. Achieving A-level compliance still requires significant effort, but it doesn't require compromising on style or functionality.
- AA: This level of conformance sits in the middle and is mandated by most accessibility laws. It strikes a balance between meeting user needs and feasibility.
- AAA: While AAA represents the highest level of compliance, it's not a standard applicable to entire websites, as suggested by WCAG authors. Instead, it serves as a goal and is applied selectively. AAA requirements can require compromises on content, functionality and style as they’re quite stringent, whereas A and AA almost universally improve usability for all users, regardless of whether they have accessibility needs.
Potential Changes to the AODA
The Accessibility for Ontarians with Disabilities Act (AODA) has required WCAG 2.0 AA compliance since January 1, 2021, with two exceptions for multimedia content. These requirements were phased in over several years to provide organizations with ample time to meet them. However, regrettably, many public sector organizations in Ontario are still far from achieving compliance.
What about future changes? While I can't predict legislative alterations with certainty, I recommend focusing on WCAG 2.0 AA compliance in the short and medium term. It's unlikely that the legislation will change soon, but one can never be sure. If you're considering substantial software investments, such as a new website or public facing tools, ensure that your vendor is willing to meet WCAG 2.1 and 2.2 AA standards in the future, if they aren't already compliant. AAA compliance, realistically, will likely never be required across an entire website, as the WCAG authors themselves suggest applying those Success Criteria selectively.
Looking ahead: WCAG 3
WCAG 3 promises significant changes from any iteration of version 2. It will likely introduce a complete restructuring, incorporating bronze, silver, and gold compliance levels to account for partial compliance. While I eagerly anticipate the flexibility that WCAG 3 might offer, it's important to note that this version is still years away from publication, making it impossible to work towards compliance at this time. The best thing you can do to prepare for it is to meet current WCAG standards. This means that you shouldn’t be asking your software vendors to meet WCAG 3, and if they claim they do, you should be worried!
Summary
To recap, the Web Content Accessibility Guidelines (WCAG) comprise versions 2.0, 2.1, and 2.2, with Success Criteria categorized as A, AA, and AAA based on their end user impact and difficulty to meet them.
For now, your focus should be on meeting AODA's requirement of WCAG 2.0 AA compliance. Don’t concern yourself with 2.1, 2.2 until you’ve already met the existing compliance requirements under the AODA. And certainly don’t be worried yet about the early draft version of 3.0. When sourcing new software, consider looking for 2.1 or 2.2 compliance, but seeking compliance with 3.0 or AAA doesn’t make sense!
