We all know that ensuring equal access to online information and services is essential. The World Wide Web Consortium (W3C), provides us with guidelines, better known as the WCAG (Web Content Accessibility Guidelines) for making digital content more accessible for everyone. A more inclusive online experience. Who doesn’t want that?
And now there is a new version of these guidelines: WCAG 2.2. Curious what it’s all about? GX is here to explain. But first, what is WCAG again?
What is WCAG?
Are you aware that by lacking digital accessibility, you're essentially excluding a quarter of your audience? Indeed, around 25% of individuals have disabilities that hinder their use of digital services — if these are not accessible.
Digital accessibility also has extra advantages for your organization. For example, your social responsibility contributes to a positive image of your organization. It shows that your company is socially involved and cares. Another advantage is SEO optimization. A well-structured website is excellent for indexing.
Slowly, more and more digital services are accessible to everyone — and that’s all thanks to WCAG.
WCAG revolves around four fundamental principles: Perceivable, Operable, Understandable, and Robust (POUR). Each principle covers specific success criteria, designed to enhance the accessibility of digital content. Holding onto these principles, organizations can create content that is perceivable to all users. Their fundamentals are operable across different devices and assist new technologies.
It focuses on the guidelines for web content accessibility for three key groups:
- People with a cognitive, language, or learning disability;
- People with a visual impairment;
- People with a disability on mobile devices.
What's new in WCAG 2.2
Just like the internet and our online behavior, the WCAG is constantly advancing and updating.
In the new update, WCAG 2.2, they added 6 new criteria. A few of these new criteria are especially meant to improve the accessibility on tablet and phone.
We’ll give you some practical examples and tips for the implementations of the new guidelines. Curious about the full list of changes? You can find these here.
1. Simplifying navigation on websites and apps
Guideline 2.4 from the WCAG 2.2 : “Navigable”, is part of the Operable principle. It is important that users:
- are able to easily navigate through your website or app
- can quickly find content
- always know where they are when they're browsing the website
This last point in particular does not always go well. You can improve here by highlighting the active tab in the navigation menu and always providing a breadcrumb trail.
2. Be aware of the different ways that users use to interact with your content
Not everyone uses a mouse or keyboard. All forms of input have to be doable for all kinds of helping tools. For example, with voice control it is not possible to perform gestures and performing drag and drop actions might not be possible due to a physical limitation.
Alternatives for using a mouse: using a pointing stick that can be moved with the mouth or browsing by means of eye tracking. You can imagine that it is difficult for these users to properly click on small parts of your website. WCAG 2.2, requirements for a minimum size of the target areas are set.
3. Be predictable and prevent confusion
Being predictable may sound boring, but being predictable on a website makes it easier to use for your visitors. You ensure that users can quickly find what they are looking and therefore are also more likely to buy something from your webshop.
Some websites and (especially) web shops make a sport of hiding contact details. This way they avoid a potentially enormous pressure on their customer service. However, for some users extra customer service is very important. Offer them a helping hand by making your contact details easy to find when an action needs to be performed.
WCAG 2.2 states that “help” information should be easy to find in general. This could be contact information, but a chatbot or FAQ can also provide help. Be aware that when you use one of these tools, that it should always be found in the same place on your website.
4. Make log-in and filling in forms easier
User input is probably one of the most essential things for the conversion of your website (e.g. a contact form or checkout in a webshop). Therefore, help users avoid mistakes and correct them.
A lot of websites also require logging in. To buy something in an online shop or to change your contact details, for example. For the security of data, logging in should not be too easy, of course. However, for some users logging in can be really hard. Think of those Captcha quizzes that ask you to click on all the traffic lights. When visually impaired, or when using a blow stick, this can be a nightmare to perform within the required amount of time.
WCAG 2.2 states that logging should be easier for users. For example, you can offer an alternative option for a “cognitive test” (such as a Captcha). With logging in via a link that you receive by email, for example.
Does your website meet the WCAG 2.2 standards?
Making a quick difference: low-Hanging Fruit
You're probably asking yourself now: does my website meet the WCAG 2.2 standard? And if not, where do I start? Focusing on “low-hanging fruits” is a good way to start. These may include simple, yet impactful measures such as providing descriptive alternative text for images, ensuring logical heading structures for easy navigation, and maintaining adequate color contrast for readability.
Check where you stand with an accessibility audit
Embracing WCAG guidelines is not only becoming a legal obligation for most organizations (through the European Accessibility Act), but it is also of moral importance. By prioritizing accessibility best practices, organizations can expand their audience reach, enrich user experiences, and demonstrate a steadfast commitment to inclusion. With WCAG 2.2 just being released, there's no better time for you to reassess your accessibility initiatives and position yourself as a champion of digital inclusivity.
Want to know if your website meets the new WCAG 2.2 guidelines? Check it with our GX accessibility audit or read this blog.
