WCAG (Web Content Accessibility Guidelines)
WCAG, short for Web Content Accessibility Guidelines, is the international standard from the World Wide Web Consortium (W3C) that defines how to make websites, apps and digital content usable by people with disabilities, using testable success criteria at three conformance levels: A, AA and AAA.
The current version is WCAG 2.2. Most accessibility laws, including the ADA Title II rule in the US and the European Accessibility Act in the EU, point to WCAG Level AA as the benchmark for an accessible website.
What is WCAG?
WCAG is a set of guidelines for making text, images, forms, video, navigation and code accessible. It is published by the W3C's Web Accessibility Initiative (WAI) and shapes almost every definition of web accessibility used in law, procurement and contracts.
The ISO version of the standard puts it simply: "WCAG 2.2 defines how to make Web content more accessible to people with disabilities." Since October 2025, WCAG 2.2 has also been an international standard, ISO/IEC 40500:2025.
WCAG is not a law. It is the technical yardstick that laws, regulators and courts use to decide whether a site is accessible. Read the full standard at WCAG 2.2 on w3.org.
What are the core principles of WCAG?
Every WCAG success criterion sits under one of four principles, known as POUR:
- Perceivable: people can see or hear the content, for example through alt text, captions and enough color contrast.
- Operable: people can use every function with a keyboard or other input, with enough time and no keyboard traps.
- Understandable: text, labels, errors and navigation are clear and predictable.
- Robust: code works reliably with browsers and assistive technology such as screen readers, often helped by WAI-ARIA for custom components.
How does WCAG work?
WCAG is organized as a hierarchy, from broad principles down to testable checks:
| Layer | What it does |
|---|---|
Principles | Four POUR principles that every requirement supports |
Guidelines | 13 goals, such as "Text Alternatives" or "Keyboard Accessible" |
Success criteria | Testable statements, each assigned to Level A, AA or AAA |
Techniques | W3C-documented ways to meet each criterion, plus common failures to avoid |
Conformance | A page conforms at a level when it meets every criterion at that level and below |
Because success criteria are testable, teams can audit a site, record a baseline score and track progress release by release.
What is the difference between WCAG and the ADA?
WCAG is a technical standard that says how to make content accessible. The ADA is a US civil rights law that says who must make it accessible. The ADA Title II rule adopts WCAG 2.1 Level AA as its technical standard. For details, see ADA (Americans with Disabilities Act).
What are the main versions and levels of WCAG?
- WCAG 2.0 (2008): the foundation of WCAG 2.x, still referenced by Section 508 and older laws.
- WCAG 2.1 (2018): added mobile, low-vision and cognitive criteria; named in the US ADA Title II rule.
- WCAG 2.2 (2023): nine new success criteria, including focus not obscured, target size and accessible authentication; the obsolete Parsing criterion removed.
- WCAG 3.0 (Working Draft): a future model with a different structure, not yet a standard to build against.
Each version has three levels. Level A is the minimum, Level AA is what most laws require, and Level AAA is the strictest. W3C does not recommend AAA as a blanket requirement for whole sites.
Industry Insight
WCAG 2.2 was approved as ISO/IEC 40500:2025 in October 2025, which makes it easier for more countries to adopt it formally. W3C is also working to update the European standard EN 301 549 to the latest WCAG 2.2. Building to 2.2 now avoids a second round of fixes when laws catch up.
What are the benefits of following WCAG?
- Lower legal risk: WCAG conformance is the clearest way to show a site meets accessibility laws.
- Bigger audience: accessible pages work for people with disabilities, older visitors and anyone on a small screen or slow connection.
- Better search and AI visibility: headings, alt text and descriptive links help both SEO and GEO.
- Better user experience: clear structure and readable content help every visitor.
- One shared checklist: designers, developers, editors and auditors work from the same criteria.
Which WCAG level should you target?
There is one safe answer for most organizations: WCAG 2.2 Level AA.
- Public sector in the US must meet WCAG 2.1 AA under the ADA Title II rule; 2.2 AA covers it.
- Businesses selling to EU consumers show conformity through EN 301 549, which builds on WCAG; 2.2 AA covers it.
- US businesses have no named standard under Title III, but WCAG 2.1 or 2.2 AA is the common benchmark.
- Level AAA is worth applying to specific content, such as plain-language versions, not whole sites.
WCAG 2.2 is backward compatible, so a site that meets 2.2 AA also meets 2.1 AA and 2.0 AA.
How do you meet WCAG?
- Make it a project requirement: write WCAG 2.2 AA into the brief and record a baseline before a redesign or migration.
- Build accessible components: fix accessibility once in reusable widgets and templates, not page by page.
- Govern content: use content governance so alt text, headings and captions are checked before publishing.
- Test continuously: combine automated scans with keyboard and screen reader testing, ideally with people with disabilities.
Does Xperience by Kentico support WCAG?
Yes. Xperience by Kentico gives teams the building blocks for WCAG-conformant sites, while conformance depends on how each site is designed, built and maintained.
- Alt text at the source: alt-text fields on Content Hub assets, with alt text suggested by AIRA for editors to review.
- Reusable components: Page Builder widgets and reusable content carry accessible markup into every page that uses them.
- Governance: role-based permissions and approval workflows catch issues before they go live.
- Developer control: full control of front-end markup on .NET. See Development.
The City of Melville in Western Australia made accessibility a launch requirement for its redesign with partner ALYKA and raised its WCAG 2.2 compliance score from 80% to 92%. Clearview Federal Credit Union held its feature-rich banking site to WCAG 2.1 A/AA with Americaneagle.com. Read both stories in The 5 Most Accessible Websites of 2026 on Xperience by Kentico.
Who needs to meet WCAG?
Any organization with a public-facing website benefits from WCAG. It matters most for public sector bodies, education, healthcare, financial services, ecommerce and transport, where laws name WCAG or a standard built on it. See Kentico's industry expertise.
Frequently Asked Questions.
A page template defines the overall structure and layout of a page, while a widget defines an individual, configurable piece of content placed inside that structure. Templates give editors a starting point, such as a landing page layout with predefined sections, while widgets are what actually populate those sections with specific content like a hero banner or a product grid. In practice, a single page template can host many different widgets, and the same widget can appear across many different page templates.