Standard

WCAG

1999ActivePublished: 1 October 2026Updated: 1 October 2026Published

Key innovation

Unified web content accessibility into a single testable, technology-neutral standard built on the four POUR principles and three conformance levels (A, AA, AAA).

How it works

WCAG organises requirements into a hierarchy: the four POUR principles (perceivable, operable, understandable, robust) split into guidelines, which in turn split into specific success criteria. Each success criterion is assigned to one of three levels: A (minimum), AA (standard, most often legally required) and AAA (highest). Conformance at a given level means satisfying all criteria at that level and the levels below it. Criteria are written to be testable and technology-independent, and supporting documents (Understanding, Techniques) describe ways to meet them. WCAG 2.0 defined 12 guidelines; WCAG 2.1 added one guideline and 17 success criteria, and WCAG 2.2 added a further 9 criteria, for a total of 13 guidelines.

Problem solved

Before WCAG there was no common, measurable criterion for web accessibility, which made it hard for people with disabilities to use content and impossible to assess conformance consistently. WCAG provides a uniform, technology-neutral set of testable success criteria.

Components

PerceivablePOUR principle

Information and user interface components must be presentable to users in ways they can perceive (e.g. text alternatives, captions, sufficient contrast).

OperablePOUR principle

User interface components and navigation must be operable, including full keyboard access and no time limits that exclude users.

UnderstandablePOUR principle

Information and the operation of the interface must be understandable: readable language, predictable behaviour and input assistance.

RobustPOUR principle

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

Implementation

Implementation pitfalls

Technical conformance without real usabilityHigh

Meeting success criteria on paper does not guarantee the page is genuinely usable by people with disabilities.

Fix:Complement automated audits with testing involving real users and assistive technologies.

Relying solely on automated toolsMedium

Automated tools detect only a fraction of success criteria; many of them require manual evaluation.

Fix:Combine automated testing with manual review against the WCAG success-criteria checklist.

Treating level AAA as a mandatory targetLow

WCAG notes that AAA conformance is not achievable for all content and is generally not required as a blanket policy.

Fix:Adopt level AA as the baseline target and apply AAA criteria selectively.

Evolution

Original paper · 1999 · W3C Recommendation · W3C Web Accessibility Initiative (WAI)

Web Content Accessibility Guidelines 1.0

W3C Web Accessibility Initiative (WAI)

1999

WCAG 1.0 — W3C Recommendation

Inflection point

The first version became a W3C Recommendation on 5 May 1999.

Web Content Accessibility Guidelines 1.0 (paper)

2008

WCAG 2.0 — W3C Recommendation

Inflection point

Introduced the four POUR principles and 12 guidelines (11 December 2008); later also published as the ISO/IEC 40500 standard.

Web Content Accessibility Guidelines (WCAG) 2.0 (paper)

2018

WCAG 2.1 — W3C Recommendation

Added one guideline and 17 success criteria, covering mobile, low vision and cognitive needs among others (5 June 2018).

Web Content Accessibility Guidelines (WCAG) 2.1 (paper)

2023

WCAG 2.2 — W3C Recommendation

Added 9 new success criteria, for a total of 13 guidelines (5 October 2023; updated 12 December 2024); also published as ISO/IEC 40500:2025.

Web Content Accessibility Guidelines (WCAG) 2.2 (paper)

2026

WCAG 3.0 — Working Draft stage

W3C Accessibility Guidelines (WCAG) 3.0 remains at the Working Draft stage; a new evaluation model is intended to replace the current level system, with several more years of work ahead.

W3C Accessibility Guidelines (WCAG) 3.0 (paper)