WCAG 2.0

WCAG 2.0 is the second major version of the Web Content Accessibility Guidelines, a set of internationally recognized standards for making web content accessible to people with disabilities. Published on December 11, 2008, by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI), WCAG 2.0 was a significant evolution from its predecessor, WCAG 1.0, which had been published in 1999. WCAG 2.0 was a landmark achievement in web accessibility. While WCAG 1.0 was closely tied to specific technologies (particularly HTML), WCAG 2.0 was designed to be technology-agnostic—its principles and success criteria can be applied to any web technology, including HTML, CSS, JavaScript, PDF, Flash (at the time), and emerging formats. This technology independence was a deliberate design choice that has allowed WCAG 2.0 to remain relevant far longer than its predecessor. The guidelines are organized around four foundational principles, known by the acronym POUR: Perceivable, Operable, Understandable, and Robust. Under these principles sit 12 guidelines, and beneath those guidelines are 61 testable success criteria assigned to conformance levels A, AA, or AAA. WCAG 2.0 also became an ISO standard (ISO/IEC 40500:2012), further cementing its status as the global benchmark for web accessibility. It has been incorporated into legislation and regulations in dozens of countries, making it the most widely adopted accessibility standard in history.

WCAG 2.0 matters because it established the framework that defines web accessibility worldwide. Before WCAG 2.0, there was no universally accepted, technology-neutral standard for making the web accessible. WCAG 1.0 existed but was increasingly outdated, tied to HTML-specific techniques, and difficult to apply to the dynamic, JavaScript-heavy web that was emerging in the mid-2000s. WCAG 2.0 solved these problems by focusing on outcomes rather than techniques. Instead of prescribing specific HTML elements or attributes, WCAG 2.0 describes what accessible content should achieve. This approach means the standard can be applied to technologies that did not exist when it was written. The legal significance of WCAG 2.0 cannot be overstated. When the U.S. Access Board updated Section 508 in 2017, it incorporated WCAG 2.0 Level A and AA. Canada's AODA requires WCAG 2.0 Level AA for web content. The European standard EN 301 549 references WCAG. Courts in ADA lawsuits routinely use WCAG 2.0 as the standard against which website accessibility is measured. For organizations subject to these laws, WCAG 2.0 compliance is not optional. From a user perspective, WCAG 2.0 addresses the needs of people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. By meeting WCAG 2.0, websites become more usable for everyone, including older adults with changing abilities and users in challenging environments.

### The POUR Principles **Perceivable**: Information and user interface components must be presentable to users in ways they can perceive. This means content cannot rely on a single sense. If something is visual, there must be a text equivalent for screen readers. If something is auditory, there must be captions or transcripts. Key guidelines under Perceivable include: - Text alternatives for non-text content - Captions and alternatives for time-based media - Adaptable content that can be presented in different ways - Distinguishable content with sufficient contrast and audio control **Operable**: User interface components and navigation must be operable. All functionality must be available from a keyboard, users must have enough time to read and use content, content must not cause seizures, and users must be able to navigate and find content. Key guidelines under Operable include: - Keyboard accessibility - Enough time to read and interact - Seizure and physical reaction prevention - Navigable structure with clear wayfinding **Understandable**: Information and the operation of the user interface must be understandable. Text must be readable, web pages must operate in predictable ways, and users must be helped to avoid and correct mistakes. Key guidelines under Understandable include: - Readable text content - Predictable page behavior - Input assistance for forms **Robust**: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. This means using proper markup, ensuring parsing is correct, and providing name, role, and value information for interface components. ### Success Criteria Structure Each success criterion in WCAG 2.0 is: - **Testable**: It can be objectively evaluated, either through automated testing, manual inspection, or a combination. - **Technology-agnostic**: It describes an outcome without specifying how to achieve it in a particular technology. - **Assigned a level**: A, AA, or AAA, based on impact, achievability, and whether it would limit content design. ### Supporting Documents WCAG 2.0 is accompanied by extensive supporting documents: - **Understanding WCAG 2.0**: Explains each success criterion, its intent, and its benefits. - **Techniques for WCAG 2.0**: Provides specific implementation techniques categorized as sufficient, advisory, or failure techniques. - **How to Meet WCAG 2.0**: A customizable quick reference guide. These supporting documents are updated independently of the standard itself, allowing implementation guidance to evolve as technologies change.

**Example 1: Text Alternatives (Perceivable)** An online news article includes a photograph of a city council meeting. Under WCAG 2.0 Success Criterion 1.1.1, the image must have an alt attribute that conveys the same information the image communicates—for example, "City council members voting on the new budget proposal, March 2026." A decorative image would have an empty alt attribute (alt="") to be correctly ignored by screen readers. **Example 2: Keyboard Navigation (Operable)** A web application features dropdown menus, modal dialogs, and interactive charts. Under WCAG 2.0 Success Criterion 2.1.1, every interactive element must be reachable and operable using only a keyboard. Users must be able to open menus with Enter or Space, navigate options with arrow keys, and close dialogs with Escape—without ever needing a mouse. **Example 3: Predictable Behavior (Understandable)** A form on a government website uses a dropdown menu to select a state. Under WCAG 2.0 Success Criterion 3.2.2, simply selecting a value from the dropdown should not automatically submit the form or navigate to a new page. Changes in the setting of any user interface component should not automatically cause a change of context unless the user has been advised beforehand. **Example 4: Robust Markup (Robust)** A developer creates a custom toggle button using a `<div>` element styled to look like a switch. Under WCAG 2.0 Success Criterion 4.1.2, this custom component must have a proper accessible name ("Dark mode"), role ("switch" or "checkbox"), and programmatically determinable state ("on" or "off"). Using ARIA attributes—`role="switch"`, `aria-checked="true"`, and `aria-label="Dark mode"`—satisfies this requirement.