If you have a website or distribute any type of content on the internet, you most likely want it to be available to as many users as possible. Therefore, taking care of accessibility is a way to ensure that people with different devices and, especially, those with special needs, can absorb and even be impacted by your products and services in the digital universe. In this context, knowing the WCAG is fundamental.

The acronym for Web Content Accessibility Guidelines covers the accessibility guidelines for web content worldwide.
The document, available online and for free, presents various directions for building accessible websites, apps, and platforms. However, since the language used is more directed at programmers, many people find it difficult to understand all the guidelines. With this in mind, we at CodeBlog created this article with the aim of making it easier to understand the accessibility guidelines. Continue reading and check it out:

The scope of WCAG:

When it comes to digital accessibility, it is necessary to take into account the diversity of the audience present on the internet.
In the case of people with visual impairments, for example, the presence of content with alternative descriptions is essential.
On the other hand, users with hearing impairments only consume content that is translated into sign language.
These are just some of the cases that are considered and addressed by the document, which contains numerous specifications, precisely to cover all audiences in the most complete and effective way possible.

Inside WCAG

WCAG is divided into four principles: perceivable, operable, understandable, and robust, each with its respective recommendations. Learn more about them in the next topics:

Perceivable

According to the first principle of WCAG, it is essential that web content be presented in multiple formats. This means that images must be accompanied by alternative descriptions, videos must have captions, and HTML codes must be understandable by screen readers.
These practices ensure that content is not restricted to just one format, making it accessible to a wider audience.

Operable

An operable website, application, or tool must allow all users to perform actions without facing barriers or access difficulties.
To achieve this accessibility, it is necessary to adjust the HTML coding to support keyboard navigation.
In addition, page speed plays an important role and must be balanced—that is, neither too fast nor too slow.
It is equally important to maintain a proper organization of headings and avoid elements that could trigger epileptic seizures, such as very vibrant colors, very intense lighting, or excessive pop-ups.

Understandable

The third principle of WCAG is focused, especially, on the textual content of websites and applications. To this end, it emphasizes the importance of using legible fonts and clear, objective language, avoiding highly specialized or niche expressions.
These measures make texts more accessible to people with intellectual disabilities, such as dyslexia, ADHD, Down Syndrome, and others. In addition, they also benefit users who are unfamiliar with the subject matter or face reading or interpretation difficulties.

Robust

The last principle presents specific determinations regarding the coding of platforms. According to WCAG guidelines, all HTML must be capable and properly aligned to run assistive technologies and enable navigation through the keyboard - which is fundamental for people with motor disabilities.

Recommendations

All the principles mentioned above also have recommendations, which are leveled by so-called "success criteria" - classified by compliance levels:

A: (priority 1)

Involves the simplest criteria, which represent the biggest accessibility barriers.

AA: (priority 2)

Presents broader and more comprehensive recommendations, capable of making a website more accessible for the majority of users.

AAA (priority 3):

Covers the optimization of all previous levels and presents richer and more detailed specifications that improve accessibility and user experience.

To exemplify, we present a recommendation linked to the third principle (understandable).

“3.1.4 Abbreviations:

Whenever there is an abbreviation, a mechanism must be made available so that the user can identify the full form or the meaning of the abbreviations. (Level AAA)”

General information

The WCAG guidelines were developed by the World Wide Web Consortium (W3C) back in 1999 and have undergone several reformulations over time.
WCAG 2.0, published in 2008, is the most recent version in Portuguese and has 78 criteria to make an online product (website, app, software, etc.) accessible to everyone.
Undoubtedly, understanding and applying WCAG recommendations is a way to contribute to digital inclusion and offer users broader, more accessible, and satisfying experiences.

To check the full document, just click here.

Want to stay on top of all the news, trends, and innovations in the technology universe? Then, keep an eye on CodeBlog and follow the upcoming articles that are on the way.

A big hug, and see you in the next post!