What is WCAG?

An introduction to WCAG, their benefits, their limits, and why they're important to learn.

Introduction

You may have heard about the Web Content Accessibility Guidelines (WCAG) but weren’t sure what they were or how to use them; this article is for you!

It’s understandable to feel overwhelmed by the technical terms used in WCAG, such as “conformance level,” “priority level,” and “success criteria.” However, these are simply terms used to define the various methods of creating websites that are accessible to everyone.

What is WCAG?

WCAG are a set of guidelines designed to help website creators determine how accessible their websites are. These guidelines have been developed by the World Wide Web Consortium (W3C) and the W3C’s Web Accessibility Initiative.

They were originally published in 1999 as a recommendation from W3C but they’ve been updated several times since then to ensure they’re up-to-date with technological advancements; most recently, version 2.2 was published in October 2023. The release of WCAG 2.2 is expected this year and the W3C has now published a working draft of version 3.0.

If you’re new to WCAG, it can be a little daunting to think about everything you need to do to make your website compliant, but at their core these guidelines aim to ensure the following:

• Web pages are designed to be accessible to all kinds of users, including those who can’t use a mouse or keyboard, those who have low vision, color blindness, dyslexia, cognitive impairments such as poor memory or slow processing speed (e.g., attention deficit disorder), deafness or hearing loss (including partial hearing loss).
• Web content is perceivable, operable, understandable, robust, and durable.

WCAG specifications include things like the requirement that content is available in a format usable by screen readers, using color contrast ratios between foregrounds and backgrounds so that people with color blindness or other visual disabilities can still see the content, providing an alternative to visual or audio media where possible, and many other things you might need to think about when delivering an accessible website.

How WCAG is organized

Recent versions of WCAG are organized around four general principles related to how people access web content. Under this model accessible content must be perceivable, operable, understandable, and robust (POUR).

Perceivable

Content must be perceivable by all users, regardless of their abilities. Some users may rely on sight, for example, to read content or view an image; others, who use a screen reader or braille display, must have access to the same information.

Operable

User interface components and navigation mechanisms must be operable by all users, irrespective of their physical abilities or assistive technology. While some users may operate a mouse, others might rely on a keyboard, voice recognition, or switch control devices.

Understandable

Information and the user interface should be understandable to all users. When presenting content, plan to accommodate a diverse range of cognitive abilities, language proficiencies, and levels of experience. For example, use plain language and consistent navigation patterns to prevent barriers.

Robust

Web content must be robust enough to work with a variety of browsers, devices, and assistive technologies. For example, a user with low vision might use a screen magnifier on a mobile device, while a user with a physical disability might rely on voice recognition software on a desktop computer.

The levels of WCAG

For all of these guidelines, there are three levels of compliance: A, AA, and AAA. Each level describes how accessible the website is for people with disabilities.

Level A is the minimum level of compliance. While this is considered passing, it leaves the most people excluded.

Level AA is the mid-range level of compliance. This level means the website has met all Level A and additional Level AA requirements. This level is what most websites should aim for and represents a reasonable balance between inclusion and practicality.

Level AAA is the highest level of compliance. This means the website has met all Level A and Level AA requirements and provides additional AAA features, such as greater color contrast or enhanced audio media with sign language interpretation. Meeting this level for some features can be challenging, and some types of content cannot conform to every guideline at this level.

WCAG and the law

In the U.S., two major acts should be considered when it comes to digital accessibility: The Rehabilitation Act (particularly Section 508) and the Americans with Disabilities Act (ADA).

While these acts were originally concerned with physical access to facilities and services, they have been updated to include legal protections for digital access too. In the same way that a physical storefront might be legally expected to add a ramp to its entrance, these acts added a legal expectation for websites to be made accessible too.

The ADA protects the rights of people with disabilities, such as in employment, public accommodations, commercial facilities, and telecommunications. It prevents discrimination and promotes equal opportunities.

Section 508 of the Rehabilitation Act requires federal agencies and organizations receiving federal funding to provide digital information in a way accessible to disabled individuals.

The Section 508 requirements comply with accessibility standards like WCAG, which has become the standard in several accessibility-related lawsuits. Some organizations have had to settle or been ordered to pay for fixing accessibility errors on their website, as well as the plaintiff’s legal fees and punitive damages.

For more details about legal regulations, see our Accessibility and the Law guide.

Using WCAG

Getting started using WCAG can seem like a lot if you don’t know where to begin. Here are some tips for how to make a start:

• Focus on the basics. There are many things to learn about WCAG, but you don’t need to know everything all at once to start making your website more accessible. begin by focusing on a few of the important basics, such as providing text alternatives for images and ensuring your website is navigable with a keyboard.
• Break it down. Don’t feel like you must make your website perfectly accessible all at once. Break it down into smaller steps to tackle one at a time. This will make the process less daunting and more manageable.
• Don’t be afraid to ask for help! You aren’t alone, plenty of resources are available online if needed.