WCAG 2.0: A Web Accessibility Standard for the Evolving Web
Loretta Guarino Reid, Andi Snow-Weaver · 2008 · Proceedings of the 2008 International Cross-Disciplinary Conference on Web Accessibility (W4A) · doi:10.1145/1368044.1368069
Summary
Written by two members of the WCAG working group (from Google and IBM respectively), this paper explains the major design challenges faced in developing WCAG 2.0 and the strategies adopted to address them. WCAG 1.0, finalized in 1999, was designed for a web of static HTML pages and had become increasingly inadequate as the web evolved to include CSS, JavaScript, AJAX, Flash, SVG, PDF, and user-generated content. The authors identify several critical problems with WCAG 1.0: it was HTML-specific, many requirements were subjective and not objectively testable (a key reason the US government did not adopt it for Section 508), and its "Until user agents..." provisions assumed browser and assistive technology improvements that were slow to materialize. WCAG 2.0 addressed these issues through three fundamental architectural decisions: organizing requirements around four technology-neutral principles (Perceivable, Operable, Understandable, Robust); replacing the priority-based checkpoint system with three conformance levels (A, AA, AAA) based on multiple factors including achievability and impact on design freedom; and separating normative success criteria from informative, technology-specific techniques that can be updated independently. The paper examines how WCAG 2.0 handles the blurring of boundaries between content, user agents, and authoring tools in the Web 2.0 era, introducing concepts like "partial conformance" for pages containing third-party content and "accessibility-supported" technologies.
Key findings
The paper articulates several design decisions that shaped WCAG 2.0 and remain foundational to web accessibility practice. The concept of "accessibility-supported" technologies resolved a thorny question: rather than prescribing which technologies are accessible, WCAG 2.0 defines criteria for determining whether a technology has sufficient user agent and assistive technology support in a given context — recognizing that support varies by environment and language. The "used but not relied upon" principle for non-accessibility-supported technologies enabled graceful degradation, allowing authors to use newer technologies while ensuring core content remains accessible without them. The paper details how ARIA emerged as a critical bridge technology, enabling JavaScript-driven custom controls to expose roles, states, properties, and keyboard focus to assistive technologies — directly addressing WCAG 2.0 success criteria that were otherwise difficult to meet with scripted interfaces. On policy, the authors note that TEITAC (the US advisory committee refreshing Section 508) had harmonized its recommendations with WCAG 2.0, and that China had based its 2007 web accessibility standards on WCAG 2.0, signaling the standard's trajectory toward global adoption.
Relevance
This paper provides essential historical context for understanding why WCAG 2.0 is structured the way it is — knowledge that remains directly relevant since WCAG 2.0 remains the most widely referenced web accessibility standard globally and the foundation for WCAG 2.1 and 2.2. The technology-neutral, principle-based architecture the authors describe has proven remarkably durable, successfully accommodating mobile web, single-page applications, and other technologies that did not exist in 2008. The discussion of "accessibility-supported" technologies and partial conformance for third-party content anticipates challenges that have only intensified with modern web development practices like embedded widgets, social media integrations, and third-party advertising. For practitioners, understanding the rationale behind the separation of normative success criteria from informative techniques explains why techniques documents are living resources that evolve independently of the standard itself — a distinction that continues to cause confusion in the accessibility community.
Tags: WCAG · web standards · accessibility guidelines · WAI · ARIA · accessibility policy · conformance · technology neutrality
Standards referenced: WCAG 1.0 · WCAG 2.0 · WAI-ARIA · Section 508 · ATAG · UAAG