FAQs on WCAG 2.0 2.1 and 2.2

WCAG 2.1, released in June 2018, builds on WCAG 2.0 by addressing gaps identified in the earlier version. It introduces 17 new success criteria, expanding on accessibility for mobile devices, people with low vision, and individuals with cognitive and learning disabilities. The guidelines are structured to maintain backward compatibility with WCAG 2.0, meaning that content conforming to WCAG 2.1 also conforms to WCAG 2.0.

WCAG 2.2, released in December 2023, is the latest version of the guidelines, adding nine new success criteria. These updates focus on making web content more accessible, particularly for users with cognitive and learning disabilities, as well as improving the overall user experience. New criteria address issues such as focus appearance, target size, and accessible authentication, ensuring that the guidelines remain relevant in the evolving digital landscape.

The main differences lie in the additional 17 success criteria introduced in WCAG 2.1, which cover areas not fully addressed in WCAG 2.0. Key additions include:

• Orientation (1.3.4): Ensuring content is viewable in both portrait and landscape orientations.
• Identify Input Purpose (1.3.5): Facilitating the identification of input fields' purposes, improving form accessibility.
• Reflow (1.4.10): Ensuring content can be presented without loss of information or functionality when viewed at 320 pixels wide.
• Non-Text Contrast (1.4.11): Enhancing the contrast of non-text elements such as icons and graphical controls.
• Text Spacing (1.4.12): Allowing users to override text spacing to improve readability without loss of content or functionality.

WCAG 2.2 introduces nine new success criteria, including:

• Focus Appearance (2.4.11): Enhancing the visibility of the keyboard focus indicator.
• Focus Not Obscured (Minimum) (2.4.12): Ensuring the focus indicator is not hidden behind other content.
• Dragging Movements (2.5.7): Providing alternatives for functions requiring dragging movements.
• Accessible Authentication (3.3.7): Ensuring users can authenticate without relying on cognitive functions such as memory.

WCAG defines three levels of conformance to provide flexibility and accommodate different contexts and resources:

• Level A (Minimum): Basic web accessibility features that address the most critical barriers for users with disabilities.
• Level AA (Mid Range): Deals with the biggest and most common barriers for users, representing the minimum level of accessibility for most organizations to meet legal requirements.
• Level AAA (Highest): Addresses the highest and most complex accessibility barriers, aiming to make content accessible to the broadest range of users, but not all content can meet AAA criteria.

While not always legally required, complying with WCAG 2.2 ensures your website meets the latest accessibility standards, enhancing the user experience and potentially reducing legal risks. Updating to WCAG 2.2 demonstrates a commitment to accessibility and can improve usability for all users, including those with disabilities.

Some of the key guidelines introduced in WCAG 2.1 include:

• • Orientation (1.3.4): Content should be viewable in both portrait and landscape orientations without requiring scrolling.
  • Identify Input Purpose (1.3.5): Programmatically identifying input fields’ purposes, helping browsers and assistive technologies to provide better user assistance.
  • Reflow (1.4.10): Ensuring that content can reflow and be readable on small screens without horizontal scrolling.
  • Non-Text Contrast (1.4.11): Ensuring sufficient contrast for graphical objects and UI components.
  • Text Spacing (1.4.12): Allowing users to adjust text spacing to improve readability.

WCAG 2.2 adds nine new success criteria, including:

• Focus Appearance (2.4.11): Ensuring that the keyboard focus indicator is clearly visible.
• Focus Not Obscured (Minimum) (2.4.12): Making sure the focus indicator is not hidden by other content.
• Dragging Movements (2.5.7): Providing alternatives for actions requiring dragging movements.
• Accessible Authentication (3.3.7): Allowing users to authenticate without relying solely on memory or other cognitive functions.

It is advisable to follow the latest version, WCAG 2.2, to ensure the most comprehensive accessibility. However, legal requirements may specify compliance with a particular version, such as WCAG 2.0 or 2.1. Reviewing regulatory guidelines and assessing the needs of your audience can help determine the best approach.

Yes, if a website complies with WCAG 2.2, it will also comply with WCAG 2.0 and 2.1, as each subsequent version builds on and includes the previous versions’ criteria. Implementing the latest standards ensures the broadest accessibility compliance.

For thorough checks, we recommend manual testing; however, various automated tools can help assess WCAG compliance, including:

• WAVE: A web accessibility evaluation tool that provides visual feedback about the accessibility of web content.
• Axe: A browser extension that performs automated accessibility testing.
• Lighthouse: A tool integrated into Chrome DevTools that audits the performance, accessibility, and SEO of web pages.

Non-compliance with WCAG guidelines can result in legal actions, fines, and damage to an organization's reputation. In many jurisdictions, such as the EU and the US, web accessibility is a legal requirement, and failure to comply can lead to lawsuits and enforcement actions by regulatory bodies.

WCAG updates are not on a fixed schedule but occur as needed to address emerging accessibility challenges and technological advancements. Major updates have occurred with WCAG 2.0 in 2008, WCAG 2.1 in 2018, and WCAG 2.2 in 2023.

Mobile accessibility is quite important as more users access web content via mobile devices. WCAG 2.1 addresses this by introducing guidelines that ensure web content is accessible on smaller screens and touch interfaces, such as ensuring content reflows without horizontal scrolling (Reflow 1.4.10) and making touch targets appropriately sized (Target Size 2.5.5).

Yes, WCAG (Web Content Accessibility Guidelines) does apply to mobile apps. WCAG sets standards for web content accessibility, and these standards are relevant to mobile apps as well. Ensuring that your mobile app follows WCAG guidelines helps create a more inclusive digital experience for users with disabilities, including those who rely on mobile devices for accessing content and services.