Skip to content
EnglishFrançais

WCAG (Web Content Accessibility Guidelines)

WCAG (Web Content Accessibility Guidelines) is a technical standard published by the World Wide Web Consortium (W3C) that defines testable success criteria for making web content accessible to people with disabilities. Version 2.2, published in October 2023, groups 13 guidelines under four principles and grades each success criterion at level A, AA or AAA.

Definition and how it works

The W3C writes WCAG for the people who build and evaluate websites, such as developers, designers, content authors and the makers of authoring and testing tools, which is why it presents the guidelines as a technical standard rather than as an introduction to web accessibility. The four principles require content to be perceivable, operable, understandable and robust, and each guideline under them breaks down into success criteria that a tester can check on a given page.

Conformance is cumulative: a page conforms at level A when it meets every level A criterion, at level AA when it also meets every AA criterion, and at level AAA when it meets all three levels. Because conformance applies to full pages only, a page cannot claim a level if part of it is excluded from the evaluation.

The current family has three versions, all still valid. WCAG 2.0 was published on 11 December 2008, WCAG 2.1 on 5 June 2018 with 17 additional success criteria, and WCAG 2.2 on 5 October 2023 with 9 more. Later versions add criteria without changing existing ones, apart from 4.1.1 Parsing, which WCAG 2.2 marks as obsolete, so content that conforms to WCAG 2.2 also conforms to 2.1 and 2.0. WCAG 2.2 has also been approved as the international standard ISO/IEC 40500:2025.

WCAG and ATAG: the differences

WCAG applies to the content that visitors read and use, whereas ATAG (Authoring Tool Accessibility Guidelines) applies to the tools that produce that content, including content management systems. ATAG has two parts: Part A covers the accessibility of the tool’s own interface for authors with disabilities, and Part B covers how the tool helps authors publish content that meets WCAG.

WCAG and ATAG
WCAGATAG
What it applies toWeb pages and web applicationsAuthoring tools, including CMS
Who it protectsVisitors with disabilitiesAuthors with disabilities (Part A), and visitors through the content authors produce (Part B)
Current versionWCAG 2.2ATAG 2

When an organization evaluates an accessible CMS, ATAG Part B is the part that matters for WCAG conformance, because it describes how the tool guides authors towards accessible content.

WCAG in practice

WCAG itself does not create a legal duty. Obligations come from rules adopted in each jurisdiction, and each rule names the WCAG version and level it requires.

Rules that require WCAG
RuleWho it coversWCAG version required
ADA Title II rule, US Department of Justice (2024)State and local governmentsWCAG 2.1 AA. Since an interim final rule of 20 April 2026, compliance is due by 26 April 2027 for entities serving 50,000 people or more, and by 26 April 2028 for smaller entities and special district governments
Revised Section 508 Standards (US)Federal agenciesWCAG 2.0 A and AA
European Accessibility Act, directive (EU) 2019/882Listed products placed on the EU market and listed services provided to consumers after 28 June 2025Accessibility requirements set by the directive
RGAA (Référentiel général d’amélioration de l’accessibilité, France)Bodies subject to the French accessibility obligation: public-law entities (the State, public institutions, local authorities), some private bodies with a public service mission, and companies with a French turnover above €250 millionRGAA 4.1.2 is in force; RGAA 5, expected at the end of 2026, will integrate WCAG 2.2

For an organization that runs many sites, the full-page rule changes how conformance is managed. A design system that meets WCAG gives every page an accessible frame, but each page that editors publish, with its images, headings, link text and attached documents, is part of what an accessibility audit tests. Conformance therefore depends as much on the daily publishing work as on the initial build, which is why the support that the authoring tool gives editors carries weight in the choice of a CMS. When a Jahia site is connected through the Siteimprove integration, editors can check each page for accessibility at levels A, AA and AAA without leaving the editing interface.

Frequently asked questions