Web Content Accessibility Guidelines (WCAG) 2.0

Plain English Summary

The Web Content Accessibility Guidelines (WCAG) 2.0, published by the World Wide Web Consortium (W3C) in December 2008, is the internationally recognized standard for making web content accessible to people with disabilities. It is not a law itself, but it has been incorporated into laws and regulations around the world, making it the de facto legal standard for web accessibility.

WCAG 2.0 is built around four principles, often remembered by the acronym POUR: content must be Perceivable, Operable, Understandable, and Robust. Under these four principles, 12 guidelines provide the goals that web developers should work toward. Each guideline has testable success criteria at three levels: A (minimum), AA (recommended), and AAA (ideal).

Level AA is the standard most commonly referenced in legal and regulatory contexts. When courts, the DOJ, or settlement agreements refer to "WCAG compliance," they almost always mean Level AA.

Who This Applies To

WCAG 2.0 is a voluntary technical standard, but its legal significance means it effectively applies to:

Organizations Legally Required to Follow WCAG 2.0:

• Federal agencies (Section 508 incorporates WCAG 2.0 AA)
• Federal contractors and technology vendors selling to the government
• Organizations subject to accessibility laws in countries that have adopted WCAG 2.0 (EU, Canada, Australia, and others)

Organizations Practically Expected to Follow WCAG 2.0:

• Any business operating a website that qualifies as a place of public accommodation under ADA Title III
• State and local governments (Title II, with the 2024 rule now specifying WCAG 2.1 AA)
• Educational institutions
• Healthcare providers
• Financial institutions
• E-commerce businesses

Who Creates WCAG: WCAG is developed by the Web Accessibility Initiative (WAI) of the W3C, through a collaborative process involving accessibility experts, disability advocacy organizations, industry representatives, and government agencies from around the world.

Key Requirements

The Four Principles (POUR)

1. Perceivable -- Information and user interface components must be presentable to users in ways they can perceive.

• Provide text alternatives for non-text content (images, videos, audio)
• Provide captions and alternatives for multimedia
• Create content that can be presented in different ways without losing meaning
• Make it easier for users to see and hear content

2. Operable -- User interface components and navigation must be operable.

• Make all functionality available from a keyboard
• Give users enough time to read and use content
• Do not design content in ways known to cause seizures
• Provide ways to help users navigate, find content, and determine where they are

3. Understandable -- Information and operation of the user interface must be understandable.

• Make text readable and understandable
• Make content appear and operate in predictable ways
• Help users avoid and correct mistakes

4. Robust -- Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.

• Maximize compatibility with current and future tools

Conformance Levels

Level A (Minimum): 25 success criteria addressing the most fundamental barriers. Failure to meet Level A means some users will be completely unable to access the content. Examples:

• All images have alt text (1.1.1)
• All functionality is keyboard accessible (2.1.1)
• Pages have descriptive titles (2.4.2)

Level AA (Recommended Standard): 13 additional success criteria beyond Level A. This is the level referenced in most legal and regulatory frameworks. Examples:

• Color contrast ratio of at least 4.5:1 for normal text (1.4.3)
• Content can be resized up to 200% without loss of functionality (1.4.4)
• Consistent navigation across pages (3.2.3)
• Error suggestions are provided when input errors are detected (3.3.3)

Level AAA (Ideal): 23 additional success criteria. This level is aspirational and not typically required by law. Examples:

• Enhanced contrast ratio of 7:1 (1.4.6)
• Sign language interpretation for prerecorded audio (1.2.6)
• Context-sensitive help is available (3.3.5)

Supporting Documents

WCAG 2.0 includes extensive supporting documents:

• Understanding WCAG 2.0: Explains each guideline and success criterion in detail
• Techniques for WCAG 2.0: Provides specific coding techniques that satisfy the success criteria
• How to Meet WCAG 2.0: A customizable quick reference

Enforcement and Penalties

WCAG 2.0 itself is not enforceable -- it is a voluntary standard. However, it becomes enforceable when incorporated into law:

Section 508 (Federal)

The 2017 Section 508 refresh directly incorporates WCAG 2.0 Level A and AA. Federal agencies and their contractors must meet these standards. Violations can result in administrative complaints, lawsuits, and procurement consequences.

ADA (Title II and Title III)

While the ADA does not explicitly reference WCAG, courts and the DOJ have consistently used WCAG 2.0 AA as the benchmark. The 2024 Title II rule formally adopted WCAG 2.1 AA, but WCAG 2.0 AA remains relevant as the baseline that WCAG 2.1 builds upon.

International Adoption

WCAG 2.0 has been adopted as a standard (or the basis for standards) in:

• European Union (EN 301 549)
• Canada (Accessible Canada Act)
• Australia (Disability Discrimination Act)
• Israel, Japan, and many other countries

Penalties by Legal Context

• Section 508: Administrative remedies, injunctive relief, attorneys' fees
• ADA Title II: Compensatory damages, injunctive relief, attorneys' fees, loss of federal funding
• ADA Title III: Injunctive relief, civil penalties up to $150,000, attorneys' fees
• State laws: Varies; California and New York allow monetary damages

Practical Implications

For Web Developers

• Start with Level A and build to Level AA. Do not attempt to achieve AAA across your entire site -- it is not practical for all content types.
• Use semantic HTML. Proper heading structure, landmark elements, form labels, and ARIA attributes are the foundation of WCAG compliance.
• Test with automated tools first, then manually. Tools like axe, WAVE, and Lighthouse catch structural issues, but manual testing catches usability issues.
• Test with screen readers. NVDA (free for Windows), VoiceOver (built into macOS/iOS), and TalkBack (built into Android) should all be part of your testing toolkit.

For Content Creators

• Write descriptive alt text for every meaningful image.
• Use headings in proper order (H1, H2, H3) to create document structure.
• Ensure sufficient color contrast between text and background.
• Provide captions for all video content and transcripts for audio content.
• Use descriptive link text (not "click here" or "read more").

For Organizations

• WCAG 2.0 is the floor, not the ceiling. While it remains legally relevant through Section 508, the accessibility community and regulatory trend is moving toward WCAG 2.1 and 2.2. Start with 2.0 AA if you must, but plan for 2.1 AA.
• Accessibility is ongoing. Conformance is not a one-time achievement. Every new page, post, or feature must meet the standards.

Key Dates and Deadlines

| Date | Event | |------|-------| | December 11, 2008 | WCAG 2.0 published as a W3C Recommendation | | October 2012 | WCAG 2.0 approved as ISO/IEC 40500:2012 | | January 18, 2017 | Section 508 refresh published, incorporating WCAG 2.0 AA | | January 18, 2018 | Refreshed Section 508 standards take effect | | June 5, 2018 | WCAG 2.1 published, superseding WCAG 2.0 |

WCAG 2.0 remains an active W3C Recommendation and a valid conformance target. Content that conforms to WCAG 2.1 or 2.2 also conforms to WCAG 2.0, as the later versions only add new success criteria without modifying existing ones.

---

This content is provided for educational and informational purposes only and does not constitute legal advice. For guidance on your specific situation, consult a qualified attorney. Laws and regulations are subject to change, and this information may not reflect the most current legal developments.