What Is WCAG? Understanding the Web Content Accessibility Guidelines

The Web Content Accessibility Guidelines, commonly known as WCAG, are the internationally recognized technical standards for making digital content accessible to people with disabilities. Developed by the World Wide Web Consortium (W3C) through a collaborative effort involving disability advocacy groups, government agencies, accessibility researchers, and industry professionals, WCAG provides the framework that organizations worldwide use to evaluate and improve digital accessibility.

WCAG is not a law in itself. It is a set of technical standards. However, WCAG has been adopted or referenced by virtually every major accessibility law and regulation globally, making it the de facto benchmark for legal compliance. If your organization needs to comply with the European Accessibility Act, the Americans with Disabilities Act, Section 508, or any of the dozens of other national accessibility regulations, WCAG is the standard you will be measured against.

The Four Principles: POUR

Everything in WCAG is organized around four foundational principles known by the acronym POUR. These principles define what it means for digital content to be accessible.

Perceivable means that information and user interface components must be presentable to users in ways they can perceive. This does not mean that every user must be able to perceive content with all senses — it means that content must be available through at least one sense that the user can rely on. For example, images need text alternatives so that people who cannot see them can still understand the information. Videos need captions so that people who cannot hear the audio can still follow along. Text must have sufficient contrast against its background so that people with low vision can read it.

Operable means that user interface components and navigation must be operable by all users. Every function available through a mouse must also be available through a keyboard. Users must have enough time to read and interact with content. Content must not be designed in a way that causes seizures or physical reactions. Users must be able to navigate, find content, and determine where they are within a site.

Understandable means that information and the operation of the user interface must be understandable. Text must be readable and comprehensible. Web pages must appear and operate in predictable ways. Users must be helped to avoid and correct mistakes — especially in forms where errors can have significant consequences.

Robust means that content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies such as screen readers. This requires clean, well-structured code that follows web standards and communicates information correctly to all technologies that access it.

The 13 Guidelines

Under the four POUR principles sit 13 guidelines that provide the specific goals authors should work toward. These guidelines are not testable themselves but provide the framework for the testable success criteria.

Under Perceivable, there are four guidelines covering text alternatives for non-text content, alternatives for time-based media, adaptability of content presentation, and distinguishability of content including contrast and audio control.

Under Operable, there are five guidelines covering keyboard accessibility, sufficient time for users, seizure and physical reaction prevention, navigability, and input modalities beyond keyboard and mouse.

Under Understandable, there are three guidelines covering readability, predictability of web page behavior, and input assistance for forms and error handling.

Under Robust, there is one guideline covering compatibility with current and future user agents and assistive technologies.

Success Criteria: The Testable Requirements

Each guideline contains specific success criteria — testable statements that determine whether content meets the accessibility standard. WCAG 2.2, the current version, contains 86 success criteria in total. Each success criterion is assigned one of three conformance levels: A, AA, or AAA.

Success criteria are written to be technology-neutral. They describe what needs to be achieved, not how to achieve it. The specific techniques for meeting each criterion depend on the technology being used — HTML, CSS, JavaScript, PDF, or other formats. W3C provides separate documentation of sufficient techniques and common failures for each success criterion.

A Brief History of WCAG

WCAG has evolved significantly since its first publication. WCAG 1.0 was released in May 1999, containing 14 guidelines with a priority-based conformance system. It was groundbreaking for its time but was heavily tied to specific technologies, particularly HTML.

WCAG 2.0, published in December 2008, was a fundamental reimagining. It introduced the POUR principles, the three-level conformance system (A, AA, AAA), and technology-neutral success criteria that could apply to any web technology rather than being tied to specific markup languages.

WCAG 2.1, published in June 2018, added 17 new success criteria to address gaps that had emerged, particularly around mobile accessibility, low vision, and cognitive disabilities. It was designed as an interim update while work continued on future versions.

WCAG 2.2, published in October 2023, is the current standard. It adds nine new success criteria and removes one (SC 4.1.1 Parsing, now considered obsolete). The new criteria focus on improved keyboard navigation, touch target sizes, cognitive accessibility, and authentication usability. WCAG 2.2 is backward compatible — content that conforms to 2.2 also conforms to 2.1 and 2.0.

Who Is Responsible for Accessibility?

A common misconception is that accessibility is solely a development task. In reality, accessibility is a shared responsibility across every role involved in creating digital content. Designers make decisions about color, contrast, layout, and interaction patterns that fundamentally determine accessibility. Developers implement the technical underpinnings — semantic markup, keyboard support, ARIA attributes. Content creators write the alt text, the link text, the headings, and the instructional copy that users rely on. Product managers and business leaders set the priorities and allocate the resources.

Accessibility works best when it is integrated into every phase of the design and development process, not bolted on at the end. The earlier accessibility is considered, the less expensive and disruptive it is to implement.