How WCAG Was Born: The History of Web Accessibility Guidelines

The Pre-WCAG Web: Inaccessibility by Default

The early web (1990–1995) was built without accessibility in mind. HTML was designed for scientists exchanging research documents, not for broad public access. Images had no alt text requirement. Forms had no label associations. Tables were used for layout without semantic meaning. Screen reader software existed for desktop applications but the graphical, mouse-driven web was effectively inaccessible to blind users.

As the web became a mass medium in the mid-1990s, disability rights advocates — particularly those in the blindness and low-vision communities — raised concerns about the growing inaccessibility of web content. The American Foundation for the Blind, the National Federation of the Blind, and individual accessibility advocates began pushing web developers, browser vendors, and standards bodies to address the problem.

The Americans with Disabilities Act (1990) had established legal accessibility requirements for physical spaces and some electronic systems, but its applicability to websites was initially unclear. The ADA had not contemplated the web — it was passed before the web existed. The question of whether ADA covered websites would generate decades of litigation.

The Web Accessibility Initiative (1997)

Tim Berners-Lee, the inventor of the web, was committed to accessibility as a core web principle — he has stated that "the power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect." In 1997, the World Wide Web Consortium (W3C) launched the Web Accessibility Initiative (WAI) to address web accessibility systematically.

The WAI brought together disability experts, browser vendors, web developers, and assistive technology companies to develop guidelines for three groups:

• Web Content Accessibility Guidelines (WCAG): For content authors — how to make web pages accessible
• Authoring Tool Accessibility Guidelines (ATAG): For tools that produce web content — how authoring tools should support accessibility
• User Agent Accessibility Guidelines (UAAG): For browsers and media players — how user agents should support accessibility

WCAG 1.0 (1999): The First Standard

WCAG 1.0 was published as a W3C Recommendation in May 1999, authored by Wendy Chisholm, Gregg Vanderheiden, and Ian Jacobs. It defined 14 guidelines and 65 checkpoints, with three priority levels:

• Priority 1: Must satisfy — failure makes content inaccessible to one or more groups
• Priority 2: Should satisfy — failure makes content difficult to access
• Priority 3: May satisfy — failure makes content somewhat difficult to access

WCAG 1.0's conformance levels were A (all Priority 1 checkpoints), AA (all Priority 1 and 2), and AAA (all checkpoints). These letters — A, AA, AAA — persist in WCAG 2.x and 3.0.

WCAG 1.0 was primarily focused on accommodating assistive technology of the era. Key requirements included: providing text alternatives for non-text content, not relying on color alone to convey information, providing clear navigation mechanisms, using relative rather than absolute units for text size, and ensuring that pages were usable when stylesheets were disabled. The contrast ratio requirement in WCAG 1.0 was qualitative ("ensure foreground and background colors contrast well") rather than numeric.

The Legal Pressure: ADA and Section 508

WCAG adoption accelerated significantly through legal pressure rather than voluntary compliance. Two legal frameworks drove adoption:

Section 508 of the Rehabilitation Act (amended 1998): Required all US federal agencies to make their electronic and information technology accessible to people with disabilities, including websites. The Section 508 standards referenced WCAG 1.0 as a technical standard. Any organisation receiving federal funding or contracting with the government came under these requirements.

Americans with Disabilities Act (ADA): Beginning in the early 2000s, courts and the Department of Justice began interpreting Title III of the ADA (which prohibits discrimination in "places of public accommodation") to include websites. A series of high-profile lawsuits against retailers, banks, and other businesses established that inaccessible websites could constitute ADA violations. The wave of ADA website accessibility lawsuits, which grew dramatically from 2017 onward, made WCAG compliance a legal risk management issue, not just a design preference.

WCAG 2.0 (2008): Technology-Neutral Guidelines

WCAG 2.0, published in December 2008, was a comprehensive redesign of the guidelines framework. Key changes:

• Technology-neutral: WCAG 2.0 was written to apply to HTML, PDF, Flash, and any future web technology — not HTML-specific like WCAG 1.0
• POUR principles: All guidelines organised under four principles — Perceivable, Operable, Understandable, Robust — providing a coherent conceptual framework
• Quantitative contrast ratios: WCAG 2.0 introduced the specific contrast ratio requirements that remain the industry standard: 4.5:1 for normal text (AA), 7:1 for normal text (AAA), 3:1 for large text (AA)
• Testability: Each success criterion was written to be objectively testable — pass or fail — rather than qualitative

WCAG 2.0 became the global reference standard. ISO adopted it as ISO/IEC 40500:2012. Most national web accessibility laws reference WCAG 2.0 or 2.1 as the technical standard.

WCAG 2.1 (2018) and 2.2 (2023)

WCAG 2.1 (2018) added 17 new success criteria addressing mobile accessibility, low vision, and cognitive disabilities that had been underaddressed in 2.0. Key additions included orientation independence, text spacing adjustability, and reflow for small screens.

WCAG 2.2 (2023) added 9 new success criteria, primarily addressing cognitive accessibility and focus visibility. All WCAG 2.1 AA content remains compliant under 2.2. The backward compatibility between versions allows organisations to maintain a single compliance level rather than rebuilding for each new version.

WCAG 3.0 (in development as of 2024) is a ground-up redesign with a new conformance model — using scores and outcomes rather than binary pass/fail criteria — intended to better capture the spectrum of accessibility rather than a minimum threshold. It is not yet a published recommendation.

Check color contrast →