Recognizing Changes in Web Content Accessibility Guidelines and Incorporating Them into the Testlio Process

Being a volunteer in the World Wide Web Consortium (W3C), I have witnessed a lot of the change as it happens and I participate in the group as a way to help define how the rules are tested both manually and in the automation tools. Even though I might not be a key player in the group, being invited into the task force allows me to stay up to date with the latest updates and best practices. So when there are updates to the recommended test practices, as the Director of Accessibility at Testlio, I use my understanding to help deliver the latest updates to clients, and share with the team of auditors.

The Web Content Accessibility Guidelines (WCAG) were initially published in 1999 as an effort to bring together multiple authors and establish recommendations for accessibility. Over the years, the guidelines have undergone three updates. In 2008, WCAG 2.0 was released, just before the first smartphone was launched with a screen reader. Consequently, WCAG 2.1 was introduced in 2018 to include specific checks for mobile devices after the use of smartphones became more widespread.

WCAG version 2.2 was published on the 5th of October 2023. I am happy to inform you that the Testlio Accessibility Center of Excellence has updated the current tests, and all audits are now using WCAG 2.2 as a baseline. This was done within a week of the new checkpoints being released. We are primarily focusing on the Level A and AA checkpoints, which includes adding 6 new tests. More importantly, we have also removed 4.1.1 after the errata for removing it from all WCAG 2.x versions was released. This ensures that our clients know we are testing the latest guidance as approved by the W3C working groups.

The tests affected by the updates are:

1. Removing 4.1.1 as redundant due to technology updates.
2. Adding tests for:
   1. 2.4.11 Focus Not Obscured (Minimum) (AA)
      Making sure keyboard focus is not completely hidden by sticky headers/menus/dialogs.
   2. 2.5.7 Dragging Movements (AA)
      Ensuring that if the user must complete an action by dragging content with the mouse, there is a keyboard alternative.
   3. 2.5.8 Target Size (Minimum) (AA)
      All actionable items meeting the success criterion requirements have a target or hot area of at least 24 by 24 CSS pixels. The exceptions tend to be a link or button in a paragraph of text or list, or, the default settings of the user agent.
   4. 3.2.6 Consistent Help (A)
      Making sure every product allows the user to find information or contact someone as needed.
   5. 3.3.7 Redundant Entry (A)
      Filling out forms can sometimes ask for more data entry than is necessary, this success criterion guides us to make sure we do not enter data twice unless it is necessary. For instance, when confirming the entered password.
   6. 3.3.8 Accessible Authentication (Minimum) (AA)
      Logging in to products can be difficult for users, offering an alternative like the ability to be emailed a password, or copying and pasting from a secure password manager, are catered for.

It’s worth noting that WCAG 2.2 is the final version of WCAG 2.x. The next release will be called WCAG 3.0, and the “WC” will no longer stand for Web Content. Instead, it will refer to the brand W3C as the guidelines will incorporate the three branches of guidelines that are currently available: Authoring Tool Accessibility Guidelines (ATAG), User Agent Accessibility Guidelines (UAAG), and WCAG itself. It’s interesting to note that before the full acronym was agreed upon, it was referred to as AG or “Silver” for those who know the periodic table!