The Web Content Accessibility Guidelines (WCAG) 2.2, the latest iteration of the internationally recognized standards for web accessibility, brings forth some much-anticipated key updates to ensure a more inclusive online experience. They were released in October of 2023, and they extend WCAG 2.1 by adding nine new success criteria to improve accessibility for digital content and applications.
WCAG 2 was developed through the World Wide Web Consortium (W3) process in partnership with individuals and organizations around the world to provide a single shared standard for web content accessibility that meets the needs of people, organizations, and governments globally.
WCAG guidelines show how to make web content more accessible to people with disabilities. Web content refers to the type of information in a web page or web application and includes:
- Information such as text, images, and sounds.
- Coding or markup that defines a structure, presentation, etc.
WCAG is primarily for those who are looking for technical standards and is primarily intended for web content developers, web authoring tool developers, or others that want or need a standard for web accessibility, including mobile accessibility.
To learn more about Web Content Accessibility Guidelines (WCAG) and about previous versions, see the W3’s WCAG Overview.
What changed?
Several of the newly introduced criteria in WCAG 2.2 are rooted in established accessibility best practices, including visible keyboard focus and upholding consistency throughout user experience.
The 2.0 and 2.1 success criteria are principally the same in 2.2, with one exception: 4.1.1 Parsing is dated and removed from WCAG 2.2.
For more information, check out WCAG 2 FAQ | Web Accessibility Initiative (WAI) | W3C. As always, it is recommended that these be added to accessibility development and testing to stay up to date.
Guidelines 2.4.11 – 2.4.13: Navigable
This guideline provides ways to help users navigate, locate content, and determine where they are within a webpage or web application.
Guidelines 2.4.11 through 2.4.14 involve visible keyboard focus. Visible keyboard focus determines a user’s place on a page when navigating a website from a keyboard or other assistive technology. The new changes give additional details that state that keyboard focus should not be hidden by additional elements on a page and recommend changes to attributes such as color contrast and the sizing of the focus indicator.
Who does it affect?
People who cannot use a mouse need to see what has keyboard focus on a web page.
Guidelines 2.5.7 – 2.5.8: Input Modalities
This guideline facilitates users in operating functionality through a range of inputs beyond keyboards.
- Guideline 2.5.7 details that dragging movements (the actions of clicking and dragging with a mouse) must be achievable via another method.
- Guideline 2.5.8 defines the minimum click area size for target elements, ensuring a minimum size or as having sufficient spacing around them.
For 2.5.7, all functions that use a dragging movement for operation must be achieved by a single pointer that does not use dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
For 2.5.8, the minimum click area size for target elements like buttons is 24 by 24 pixels.
Who does it affect?
Modifying these will help people who have physical impairments and cannot click on small buttons that may be together, such as a person with a hand tremor.
Guideline 3.2.6: Predictable
This guideline makes web pages appear and operate in predictable ways.
Guideline 3.2.6 extends the existing WCAG 2.1 criteria by continuing to advance a constant user experience. Help options, including a website’s contact information, forms, and other related elements should be placed in a regular location on every page of the website.
Who does it affect?
Users can find information more easily when it is placed consistently. For example, a person with a cognitive disability can rely on finding the same information if it’s in the same place all the time.
Guidelines 3.3.7 – 3.3.9: Input Assistance
This guideline makes web pages appear and operate in predictable ways.
- Guideline 3.3.7 covers the topic of redundant entries in user-submitted information, including medical information, in a form. Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated, or available for the user to select.
- Guideline 3.3.8 and 3.3.9 outlines guidance for authentication methods that require cognitive tests, such as remembering a password or having to solve a puzzle. AA and AAA options give developers a choice of alternative authentication options, including copy and paste to reduce having to re-type passwords.
Who does it affect?
For 3.3.7, having an application autofill information can be helpful for someone who has difficulty remembering what they entered before.
For 3.3.8 and 3.3.9, having users enter an email address that can send them a link to go onto the app or allow users to copy and paste a password.
Closing Thoughts
Updates to WCAG are crucial in improving accessibility as they reflect technological advances. With technology constantly evolving, these updates ensure that accessibility guidelines keep up the pace with new developments. It also addresses the emerging challenges that may arise and expands the scope for diverse needs. Lastly, it enhances the user experience and facilitates widespread adoption to prioritize accessibility in digital initiatives globally.