From WCAG 2.0 to WCAG 2.2: Differences and Innovations Between Versions
The Web Content Accessibility Guidelines (WCAG) were created to ensure that web content is accessible to all individuals, including users with disabilities. WCAG standards are constantly updated and evolve according to innovations in web technologies and user needs. In this blog post, we will examine the version differences from WCAG 2.0 to WCAG 2.2 and the impact of these changes on web accessibility.
What is WCAG?
Web Content Accessibility Guidelines (WCAG) are standards that include principles and technical criteria for web content to be perceivable, usable, understandable and robust for everyone. These principles are:
- Perceivable
- Operable
- Understandable
- Strong
WCAG 2.0 (2008)
WCAG 2.0 is the version that forms the basis of accessibility and has been accepted as a standard for a long time. There are a total of 12 guidelines and 61 success criteria under the basic principles.
Key Points:
- Basic contrast ratios have been determined.
- The requirement for alternative text for images has become standard.
- The regular and hierarchical use of titles has gained importance.
WCAG 2.1 Update (2018)
WCAG 2.1 has been expanded with additional criteria to address new needs, particularly those resulting from the widespread use of mobile and touch-enabled devices.
Key Additions:
- Compatibility with touch interaction on mobile devices.
- Support for screen orientation (landscape and portrait).
- Clear specification of fields for auto-completed forms.
WCAG 2.2 Update (Latest Version)
WCAG 2.2 introduced more detailed criteria to improve the user experience. This version takes into account the needs of users with cognitive and mobility impairments and adds 9 new success criteria.
Innovations with WCAG 2.2:
1. Keyboard Focus Indicator
When users navigate with the keyboard, it is mandatory that the focused element is clear and distinct.
2. Target Size
Clickable targets (buttons, links) must have a certain minimum size (e.g. 44x44 pixels).
3. Accessible Authentication
Indicates that more accessible authentication methods that will reduce users' cognitive load should be used.
4. Gesture Control Alternatives
Gesture-based interactions should be made accessible with alternative methods.
5. Helpful Information in Form Fields
In order to prevent errors by users, explanatory information about form fields should be provided.
6. Consistent Help
Help options should be consistent and accessible in different sections of the website.
General Differences Between WCAG 2.2 and Previous Versions
- WCAG 2.2 takes into account the mobile user experience and the needs of users with cognitive disabilities.
- It encourages the creation of user-friendly interfaces by introducing new rules that make it easier for users to interact with the site.
- It strengthened detailed requirements for screen reader and keyboard navigation.
The development of WCAG standards is an important step in making the digital world accessible to everyone. WCAG 2.2 is full of innovations that aim to reach a wider audience of users. By making your websites compliant with the current standards, you can provide a more inclusive and equitable internet experience for your users.
You should check out other
Accessiblee Blogs
Web Accessibility
17.03.2025
Tips for Accessible Documents; Accessibility for Your Documents and Papers
Accessible documents are content that allows all users, especially those with visual, hearing, mobility or cognitive limitations, to easily access information. Having digital documents accessible is not only a necessity, but a fundamental condition for providing a better experience for all users.
Web Accessibility
17.03.2025
Accessibility Guide for Mobile Apps
Many applications ignore accessibility standards and create obstacles for certain user groups. So how can you design your application so that everyone can use it comfortably? Let's examine effective ways to increase mobile accessibility together...