What Is WCAG 2.2? A Practical, Easy-to-Understand Explanation of Why You Should Start Working on Web Accessibility Now

Many people who are beginning to take an interest in web accessibility feel unsure about where to start. In particular, for corporate website managers, PR teams, marketing departments, agency directors, and staff at local governments or educational institutions, even if they hear that accessibility is important, it can still be hard to see how it connects to day-to-day content updates and site improvements. However, web accessibility is not some special extra task. It is a basic quality standard for delivering information to the people who need it, in the form they need it. In this first article, we will carefully organize what WCAG 2.2 is, why it is receiving renewed attention now, and how it should be understood from a practical, day-to-day business perspective.

What you will learn in this article

• The basic position and role of WCAG 2.2
• Why web accessibility is being emphasized now
• What kinds of people and organizations need to respond
• How to think about its compatibility with the UUU web accessibility service
• The practical perspective this series will focus on

WCAG 2.2 is an international guideline for web content accessibility developed by the W3C. It became a W3C Recommendation in October 2023, and while it builds on WCAG 2.1, it adds nine new success criteria. At the same time, one existing success criterion was removed. Content that conforms to WCAG 2.2 is also considered to conform to WCAG 2.0 and 2.1, so it does not overturn previous ways of thinking. Rather, it is easier to understand as a practical reinforcement of areas such as usability and cognitive support that have often been overlooked. A Japanese translation is also available, making it easier for practitioners in Japan to refer to it.

What matters here is not to think of WCAG 2.2 as “a difficult standard only used by specialists.” Certainly, the document itself is technical, and at first it may feel a little intimidating. But the essence of its content is actually very straightforward. Are headings structured in the right order? Do link texts make sense on their own? Can the site be operated using only a keyboard? If a user makes an input mistake, can they easily correct it? Do moving elements create discomfort or confusion? These questions are not only for people with disabilities. They also matter for people hurriedly searching for information on smartphones, people whose vision or motor control has changed with age, people who are not comfortable with Japanese, and people whose hands are temporarily difficult to use. In other words, the most natural way to read WCAG 2.2 is not as a special accommodation for a limited group, but as a shared set of rules for creating websites that are easier for everyone to use.

So why is this topic receiving so much attention now? One reason is the growing social demand for accessibility. In Japan, from April 1, 2024, amendments to the Act for Eliminating Discrimination against Persons with Disabilities came into force, making the provision of reasonable accommodation mandatory for private businesses as well. Websites and online services are now the entry point for corporate and organizational information, applications, inquiries, recruitment, and sales. If that entry point is difficult to use, it not only narrows opportunities for users but may also lead to missed business opportunities and a loss of trust for the organization itself. In addition, the Digital Agency has made clear that it uses JIS X 8341-3:2016 and WCAG 2.2 as the basis for its web accessibility efforts, which shows that accessibility is not a passing trend but a quality standard that requires ongoing work.

Within this context, who benefits most from accessibility? For example, people responsible for updating corporate websites can deliver key content such as news releases, recruitment information, IR materials, and product information more accurately to a wider range of users. Staff at local governments and educational institutions can provide essential daily and learning-related information in ways that leave no one behind. For production companies, accessibility becomes a valuable basis for improving the quality of design and implementation, and for sales and directors it becomes a persuasive perspective for helping solve client problems. Accessibility also works well alongside improvements in SEO, site navigation, inquiry completion rates, and lower form abandonment rates, which means it often helps raise the quality of the entire user experience. Sites that are easier to read, easier to search, and less confusing tend to be not only more comfortable for users, but also more effective for the organizations that run them.

For example, imagine this situation. On a document request form, required fields are indicated only in red text. For users who have difficulty perceiving color differences, that information becomes harder to understand. If an error appears but only says, “Please check your input,” users may not know what exactly needs to be corrected. If a navigation menu is designed only for mouse use, users browsing with only a keyboard cannot reach the pages they need. If important information exists only inside images and the alternative text is insufficient, then that content is missing in screen reader environments. None of these are unusual edge cases. They are all common problems in real-world web operations. WCAG 2.2 provides a framework for noticing and systematically improving these kinds of “somehow inconvenient” experiences rather than overlooking them.

There is also one point that is often misunderstood in practice. When people hear “web accessibility,” they sometimes think, “Can’t we just solve it by adding a tool?” Certainly, support services that let users adjust text size, contrast, animation, screen reading, translation, furigana display, and similar functions can be helpful because they expand users’ choices while browsing. The UUU web accessibility service also has strong affinity with this kind of support-oriented approach, and because it emphasizes ease of introduction, it is easy to view it as an entry point into accessibility efforts. At the time of its release in June 2024, it introduced features such as contrast adjustment, text resizing, line and letter spacing adjustment, animation stop, text-to-speech, translation, and furigana display.

However, this point needs to be understood carefully. What a service like UUU is mainly useful for is helping users adjust the viewing environment to suit their own needs. On the other hand, if the page’s heading structure is broken, if form fields do not have proper labels, if link wording is vague, if the operation order is unnatural, or if error messages are unhelpful, those issues cannot be fundamentally solved without revisiting the original design and implementation. In other words, introducing a support service and improving the quality of web content itself according to WCAG 2.2 are not opposing approaches; they are different things with different roles. Throughout this series, it will be important not to blur that difference, but instead to organize both measures that expand users’ viewing assistance options and measures that improve the content itself properly. UUU has strong compatibility with accessibility efforts, but it cannot necessarily be said to be sufficient on its own. This sense of balance is extremely important in practice.

So where should web managers begin? A good first step is to ask, “For whom might our site be difficult to use?” For example, is the text too small to read? Are the explanatory sentences too long and unclear? Are important explanations provided only in images? Can users reach key features without a mouse? Are form input errors easy to correct? Just checking major pages from these points of view can help accessibility stop feeling abstract and start looking like a concrete list of improvements. Then, instead of trying to memorize all of WCAG 2.2 at once, it is much easier to proceed by understanding one basic area at a time: headings, links, images, forms, keyboard operation, color and contrast, and so on. This series will follow that same flow.

This series is designed to be useful even for people who do not yet have deep specialist knowledge. It is intended as a practical entry point for people in small and medium-sized companies without dedicated accessibility staff, PR personnel running sites alongside other responsibilities, local government employees publishing information through CMS platforms, and agency staff who want to strengthen their accessibility proposals—in other words, anyone in the position of thinking, “I know this matters, but I do not yet know how to move forward.” It will also be written in a way that can be shared with executives and decision-makers, helping them understand accessibility not merely as a cost, but as something connected to expanded access, trust building, stronger brand value, and continuous quality improvement. Technical terms will be explained as simply as possible, while still building up perspectives that can be directly used in practice.

Finally, here is a summary of this first article. WCAG 2.2 is the latest international guideline for web accessibility, and it is a basic standard that modern web operations cannot afford to ignore. Behind it are rising social responsibility, growing attention to reasonable accommodation, government policy, and the need to deliver information properly to diverse users. At the same time, support measures such as the UUU web accessibility service are highly compatible with accessibility efforts from the perspective of viewing assistance, and can be seen as useful entry points. However, true improvement requires a willingness to review content design, HTML semantics, operability, input support, and operational systems as well. In the next article, we will look at what has changed in WCAG 2.2, organizing the newly added success criteria in practical language and exploring the points that matter most in real-world work.

Reference Links

• W3C: Web Content Accessibility Guidelines (WCAG) 2.2
• W3C WAI: WCAG 2.2 is a Web Standard “W3C Recommendation”
• WAIC: Web Content Accessibility Guidelines (WCAG) 2.2 Japanese Translation
• WAIC: Announcement of the Publication of the WCAG 2.2 Japanese Translation
• Digital Agency: Web Accessibility
• GUX Inc.: Launch of the Web Accessibility Service “UUU”