---
title: "Understanding Web Content Accessibility Guidelines (WCAG): A Detailed Guide"
url: "https://www.iteratorshq.com/blog/understanding-web-content-accessibility-guidelines-wcag/"
type: article
description: "WCAG standards explained: the 4 principles, levels A, AA and AAA, what's new in WCAG 2.2, and which version the EAA, ADA and UK rules require."
published: 2022-04-26
updated: 2026-10-14
author: "Kinga Skarżyńska"
site: Iterators
categories: [Articles]
tags: ["Security, Compliance & Enterprise Readiness", "UX & Product Design"]
---

# Understanding Web Content Accessibility Guidelines (WCAG): A Detailed Guide

Ask anyone on a product team whether WCAG standards matter and they’ll say yes, without hesitating. Nobody argues for a website that a blind person can’t use. And then the accessibility ticket sits at the bottom of the backlog, somewhere under “fix the footer on Safari,” until someone forwards an email with the word “lawsuit” in the subject line.

I don’t think that’s bad intentions. I think accessibility looks like a specialist topic, written in specialist language (success criteria, conformance levels, normative and informative), and the document itself is long enough that most people only ever read a summary of a summary. Meanwhile the number of people it’s about is huge: the [World Health Organization](https://www.who.int/news-room/fact-sheets/detail/disability-and-health) estimates that 1.3 billion people, about 1 in 6 of us, live with a significant disability.

So here’s the version I’d want to read first: what WCAG is, how its four principles and three levels fit together, what changed in WCAG 2.2, and which version the law in your market asks for. (Usually it isn’t the newest one. That’s about to change, too.)

Already know you want your product to be accessible and compliant with WCAG? We can help! At Iterators, we design, build, and maintain custom software for startups and enterprise businesses.

![Iterators helps teams build software that meets WCAG standards](https://imagedelivery.net/xbsYPGC2JzolxD8T9X951A/www.iteratorshq.com/2022/04/iterators_wcag_cta.png/w=9999)

Schedule a [free consultation](https://www.iteratorshq.com/contact/) with Iterators today. We’d be happy to help you find the right software solution to help your company.

## What is WCAG?

> “Every time you wonder if you really need WCAG standards, think about how much you can gain by creating a product accessible to a wider group of recipients, and how much the world can gain thanks to you.”
>
> ![Izabela Kurkiewicz](https://imagedelivery.net/xbsYPGC2JzolxD8T9X951A/www.iteratorshq.com/2024/09/izabela-kurkiewicz.png/w=9999)
>
> Izabela Kurkiewicz
>
> Lead Designer @ Iterators

WCAG, the Web Content Accessibility Guidelines, is a set of testable rules for making websites and apps usable by people with disabilities. It’s written by the World Wide Web Consortium (W3C), the international body that develops web standards, through its [Web Accessibility Initiative](https://www.w3.org/WAI/standards-guidelines/wcag/).

What surprises most people when they open it is how little it says about what your product should look like. Almost everything is described as an outcome. A screen reader user can tell what a button does. A keyboard user can reach every control and get back out again. Text is readable against its background. How you get there is up to you, which is exactly why designers and developers can’t hand it to each other and walk away.

The WCAG standards are organized in layers. At the top sit 4 principles. Under them are 13 guidelines, and under those, in WCAG 2.2, 86 success criteria, each one a statement you can test as pass or fail. Every criterion has a level, A, AA or AAA. When someone says their site “meets WCAG,” they almost always mean Level AA of a specific version, and it’s worth asking which one.

![wcag standards structure](https://www.iteratorshq.com/wp-content/uploads/2026/10/wcag-standards-structure.webp)

It’s also an international standard in the formal sense. WCAG 2.0 was approved as ISO/IEC 40500:2012, and in 2025 WCAG 2.2 became [ISO/IEC 40500:2025](https://www.w3.org/press-releases/2025/wcag22-iso-pas/). Laws in the EU, the UK and the US point to WCAG, sometimes directly and sometimes through another standard that is built on it. More on that further down.

The guidelines cover visual, auditory, physical, speech, cognitive, language, learning and neurological disabilities. In practice they also help people who would never describe themselves as disabled: someone reading their phone in bright sun, a parent holding a baby in one arm, anyone over fifty whose eyes have started to disagree with small grey text.

## Who is WCAG intended for?

![Who WCAG standards are for: the developers' group and business decision-makers](https://imagedelivery.net/xbsYPGC2JzolxD8T9X951A/www.iteratorshq.com/2022/04/intended-groups-wcag.jpg/w=9999)

W3C writes the WCAG standards for the people who make web content and the tools around it. In practice I’d split that audience into two groups, the same way the graphic above does.

The first group builds. Analysts, researchers, designers, developers and testers decide, often without noticing, whether a form field has a label, whether a modal traps keyboard focus, whether an error message is red text and nothing else. For them, the WCAG standards are a reference they come back to criterion by criterion. It’s also written for the people who make authoring tools and accessibility testing tools, since a CMS that strips alt text undoes everyone else’s work.

The second group decides. Policymakers who know the legal side, managers who know what customers and the company expect, and researchers who watch how people actually behave. They rarely read a success criterion. They decide whether accessibility gets time in the sprint, and that decision tends to matter more than any single criterion.

The two groups need each other more than either likes to admit. A designer can draw a perfectly accessible flow and still watch it ship without focus states, because nobody planned the time to build them. (This comes up in retros more often than anyone would like.)

## What is web accessibility, and why do we need it?

> “If we want users to like our software, we should design it to behave like a likeable person: respectful, generous and helpful.”
>
> ![Alan Cooper](https://imagedelivery.net/xbsYPGC2JzolxD8T9X951A/www.iteratorshq.com/2024/10/alan-cooper.jpg/w=9999)
>
> Alan Cooper
>
> Software designer and programmer

Web accessibility means that people with disabilities can perceive, understand and operate what you’ve built, using whatever they rely on to do it: a screen reader, screen magnification, voice control, a switch device, captions, or just a keyboard.

The usual case for it starts with the WHO numbers from the top of this article, and they get bigger once you count temporary or situational limitations, like a broken wrist or a phone in direct sunlight. When a product doesn’t work for them, most people simply leave, and you’ll never see it in the analytics as anything other than a drop-off.

The second case is legal, and it has become a lot louder in the last two years. The European Accessibility Act has applied since June 2025, and website accessibility lawsuits in the US keep climbing. I’ll come back to both, because which WCAG standards apply to you depends on where you sell and who you are.

The third case is the one I find most convincing as a designer. Accessible products are easier to use for everyone. Clear labels, visible focus, enough contrast, forms that remember what you typed, buttons big enough to hit with a thumb. Nobody has ever complained about those. A lot of WCAG is good UX, written down precisely enough that you can test it.

There’s also the question of devices. People reach your product on phones, tablets, laptops, TVs and watches, at every zoom level, in portrait and landscape. You can’t predict which one a given person will use, so the content has to adapt. WCAG covers that too, with criteria for reflow and screen orientation that come up again below.

## What are the 4 principles of WCAG?

![The 4 principles behind WCAG standards: Perceivable, Operable, Understandable, Robust (P.O.U.R.)](https://imagedelivery.net/xbsYPGC2JzolxD8T9X951A/www.iteratorshq.com/2022/04/wcag-principles-of-accessibility.jpg/w=9999)

All of the WCAG standards hang off four principles, usually shortened to P.O.U.R.: Perceivable, Operable, Understandable and Robust. If you remember one thing from this article, I’d make it these four, because almost every accessibility bug you’ll find breaks one of them.

### Perceivable

People have to be able to take in the information with at least one of their senses. Anything that’s only visual needs a text version: alt text on images, captions and transcripts for video and audio, and structure a screen reader can announce (a heading that is a real heading, a list that is a real list). Color can’t be the only way you say something, and text needs enough contrast. At Level AA that means 4.5:1 for normal text and 3:1 for large text. You can check any pair of colors in a free tool like [WebAIM’s Contrast Checker](https://webaim.org/resources/contrastchecker/), which shows the ratio and whether it passes each level.

![wcag standards example contrast checker](https://www.iteratorshq.com/wp-content/uploads/2026/10/wcag-standards-example-contrast-checker.webp)

Netflix is a good example of this principle done well. Its closed captions describe sounds as well as dialogue, and many titles come with an audio description track that narrates what happens on screen.

![Closed captions and audio description in Netflix, an example of the Perceivable principle in WCAG standards](https://imagedelivery.net/xbsYPGC2JzolxD8T9X951A/www.iteratorshq.com/2022/04/closed-captions-example.jpg/w=9999)

*Netflix’s Closed Captions and Audio Description settings*

### Operable

People have to be able to use every control, however they interact with the screen. Everything should work from a keyboard, with no traps where focus goes into a component and can’t get out. People need enough time to read and act. Nothing should flash more than three times a second. And there should be clear ways to find your way around: page titles, a focus order that makes sense, link text that still means something out of context. The newer criteria also ask for an alternative to dragging and for touch targets that aren’t tiny.

### Understandable

People have to be able to understand the content and predict what the interface will do. The page declares its language, so a screen reader pronounces the text correctly. Menus stay in the same place from page to page, and nothing changes context just because you tabbed into a field. Forms say what they expect, explain what went wrong, and help you fix it. Plain writing helps here too, and a readability checker like Hemingway Editor shows quickly where sentences get too dense.

![wcag standards example hemingway readability](https://www.iteratorshq.com/wp-content/uploads/2026/10/wcag-standards-example-hemingway-readability.webp)

### Robust

Content has to work with the browsers and assistive technologies people actually use, now and a few years from now. In practice this mostly means semantic HTML, and making sure custom components (that beautiful dropdown your team built out of divs) expose their name, role and state to assistive technology.

Here’s how the 13 guidelines of WCAG 2.2 sit under the four principles:

| Principle | Guidelines |
| --- | --- |
| Perceivable | 1.1 Text Alternatives, 1.2 Time-based Media, 1.3 Adaptable, 1.4 Distinguishable |
| Operable | 2.1 Keyboard Accessible, 2.2 Enough Time, 2.3 Seizures and Physical Reactions, 2.4 Navigable, 2.5 Input Modalities |
| Understandable | 3.1 Readable, 3.2 Predictable, 3.3 Input Assistance |
| Robust | 4.1 Compatible |

## WCAG levels: A, AA and AAA

Every success criterion has one of three conformance levels. They stack: to meet AA you meet every A and every AA criterion, and AAA includes all three. This is what the 86 criteria of [WCAG 2.2](https://www.w3.org/TR/WCAG22/) look like by level (my count from the specification):

| Level | What it means | Criteria in WCAG 2.2 | Examples |
| --- | --- | --- | --- |
| A | The minimum. Without it, some people can’t use the content at all. | 31 | Images have text alternatives (1.1.1). Everything works from a keyboard (2.1.1). |
| AA | The level laws, public tenders and contracts ask for. It removes the most common barriers. | 24 | Text contrast of at least 4.5:1 (1.4.3). Content reflows at 400% zoom without horizontal scrolling (1.4.10). |
| AAA | The highest level. W3C doesn’t recommend requiring it for entire sites, because some content can’t meet all of it. | 31 | Text contrast of at least 7:1 (1.4.6). Sign language for prerecorded video (1.2.6). |

When a client, a tender or a regulator says “WCAG compliant,” they mean AA, almost without exception. I’d still read the AAA criteria. Some of them, like enhanced contrast for long body text, cost very little and make a noticeable difference to people reading for more than a minute.

One detail that catches teams out: conformance applies to whole pages and complete processes. A checkout counts as accessible only if every step of it is, so one inaccessible payment widget at the end can sink the whole flow, however good the rest of it is.

## WCAG 2.0 vs 2.1 vs 2.2 vs 3.0

People often ask which version to “pick,” as if they were competing products. They aren’t. Each version of the WCAG standards keeps the success criteria of the one before and adds new ones, so content that meets 2.2 also meets 2.1 and 2.0 (with one small exception, below). Moving up a version only costs you the new criteria.

| Version | Published | What changed | Where it’s required |
| --- | --- | --- | --- |
| WCAG 2.0 | December 2008 | The structure still in use: 4 principles, 12 guidelines, 61 success criteria | US federal agencies (Section 508) |
| WCAG 2.1 | June 2018 | 17 new criteria for mobile, low vision and cognitive disabilities, plus guideline 2.5 | EU public sector, EU product rules through EN 301 549 V3.2.1, ADA Title II |
| WCAG 2.2 | October 2023, updated December 2024 | 9 new criteria, 4.1.1 Parsing removed | UK public sector, EN 301 549 V4.1.1 |
| WCAG 3.0 | Working Draft | A new structure and conformance model | Nowhere yet |

### WCAG 2.0

The foundation. Published in December 2008, it introduced the structure that’s still in place: four principles, testable success criteria and three levels. US federal agencies still work to WCAG 2.0 AA under [Section 508](https://www.section508.gov/develop/applicability-conformance/).

### WCAG 2.1

Published in June 2018, [WCAG 2.1](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/) added 17 success criteria, mostly for things nobody could fully anticipate in 2008: smartphones, low vision and cognitive disabilities. Content has to reflow at 400% zoom, work in both portrait and landscape, and give buttons, icons and form borders enough contrast, as well as text. It also added a new guideline, 2.5 Input Modalities, for touch and other ways of interacting that go beyond a mouse and a keyboard.

### WCAG 2.2

W3C published WCAG 2.2 in October 2023 and an updated edition in December 2024. It adds [9 success criteria](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) and removes one, 4.1.1 Parsing, which W3C considered obsolete. That’s the small exception from earlier: a page can fail 4.1.1 under 2.0 or 2.1 and still meet 2.2.

| Success criterion | Level | What it asks for |
| --- | --- | --- |
| 2.4.11 Focus Not Obscured (Minimum) | AA | The focused element isn’t completely hidden behind sticky headers, banners or other content. |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focused element is hidden. |
| 2.4.13 Focus Appearance | AAA | The focus indicator is large enough and has enough contrast. |
| 2.5.7 Dragging Movements | AA | Anything you can do by dragging, you can also do with a single tap or click. |
| 2.5.8 Target Size (Minimum) | AA | Targets are at least 24 by 24 CSS pixels, or have enough space around them. |
| 3.2.6 Consistent Help | A | Help, like contact details or a chat, appears in the same relative place on each page that offers it. |
| 3.3.7 Redundant Entry | A | Information you already entered in a process is filled in or offered, so you don’t type it twice. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in doesn’t depend on a memory or puzzle test, unless there’s an alternative or help, such as paste and password managers. |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | The same, with fewer exceptions. |

So six of the nine count toward WCAG 2.2 AA: two at Level A and four at AA. Most of them are about details designers deal with every week: a sticky header covering the field you just tabbed into, a carousel you can only drag, a close icon the size of a crumb, a login form that blocks paste so your password manager can’t help. If your product already handles those, the step from 2.1 AA to 2.2 AA is small.

### WCAG 3.0

WCAG 3.0 is still a Working Draft. The latest one is from September 2026, and W3C says it [isn’t expected to be a finished standard](https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/) for a few more years. It also won’t replace WCAG 2: even after WCAG 3 is final, WCAG 2 won’t be deprecated for several years.

The draft has changed a lot along the way. Early versions scored each outcome from 0 to 4 and added the scores up to Bronze, Silver or Gold. The current draft drops that. Conformance now means meeting all the core requirements, and Bronze, Silver and Gold survive only as labels for tiers above that, still under discussion. It’s worth following to see where accessibility is heading. I wouldn’t build to it yet.

## Which WCAG standards apply to your organization?

The short answer: at least the version your law or contract names, and the newest one if you can. Because each version includes the one before, aiming for WCAG 2.2 AA covers any rule that asks for 2.1 AA or 2.0 AA. Most laws don’t quote WCAG directly. They point to a technical standard, and that standard points to WCAG.

![wcag standards timeline](https://www.iteratorshq.com/wp-content/uploads/2026/10/wcag-standards-timeline.webp)

| Region | Rule | Who it covers | What it requires |
| --- | --- | --- | --- |
| EU | European Accessibility Act (Directive 2019/882), from 28 June 2025 | Companies selling certain products and services to EU consumers | EN 301 549: V3.2.1 is based on WCAG 2.1 AA, the new V4.1.1 on WCAG 2.2 |
| EU | Web Accessibility Directive (2016/2102) | Public sector websites and mobile apps | EN 301 549 V3.2.1, so WCAG 2.1 AA |
| US | ADA Title II rule (Department of Justice, 2024) | State and local governments | WCAG 2.1 AA, by April 26, 2027 or April 26, 2028 |
| US | ADA Title III | Businesses open to the public | No technical standard in the regulations |
| US | Section 508 | Federal agencies | WCAG 2.0 AA |
| UK | Public Sector Bodies Accessibility Regulations 2018 | Public sector websites and mobile apps | WCAG 2.2 AA |

### The European Union

The [European Accessibility Act](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en) is the one I’d watch most closely if you sell to people in Europe, because it reaches well beyond the public sector. It covers e-commerce, consumer banking, e-books, electronic communications, access to audiovisual media and parts of passenger transport, among others. Microenterprises that provide services, meaning fewer than 10 people and no more than €2 million in annual turnover or balance sheet total, are exempt. There are transition periods (services using products already in use have until 28 June 2030), but new products and services have had to comply since June 2025.

The technical side runs through EN 301 549. Version 3.2.1, the one the EU cites today for public sector websites, is based on WCAG 2.1 AA. The new version 4.1.1, adopted in August 2026, is the first one written for the Act and aligns with WCAG 2.2. It only gives a legal presumption of conformity once it’s cited in the EU’s Official Journal, which hadn’t happened as of October 2026. If you’re building something new for the EU market now, I’d design to WCAG 2.2 AA and spare yourself a second pass next year.

Public sector bodies have had their own rule for longer: the [Web Accessibility Directive](https://www.w3.org/WAI/policies/european-union/) has applied to their websites since 2019 and 2020, and to their mobile apps since June 2021.

### The United States

In the US, the answer depends on who you are. State and local governments have a hard rule: the Department of Justice’s 2024 [Title II regulation](https://www.ada.gov/resources/2024-03-08-web-rule/) requires WCAG 2.1 AA. In April 2026 the DOJ pushed both deadlines back a year, to April 26, 2027 for governments serving 50,000 people or more, and April 26, 2028 for smaller ones and special district governments. Federal agencies follow Section 508, which still points to WCAG 2.0 AA.

Private businesses under Title III have no technical regulation at all, only [DOJ guidance](https://www.ada.gov/resources/web-guidance/) that names WCAG as a helpful reference. That hasn’t kept the lawsuits away. Seyfarth Shaw counted [3,117 website accessibility lawsuits](https://www.adatitleiii.com/2026/03/federal-court-website-accessibility-lawsuit-filings-bounce-back-in-2025/) filed in federal courts in 2025, 27% more than in 2024, and that’s federal courts only. If you want to know how those cases tend to go and what courts look at, I wrote about it in more detail in our [guide to app accessibility that actually works](https://www.iteratorshq.com/blog/accessibility-app-that-actually-works-your-wcag-implementation-guide/).

### The United Kingdom

UK public sector websites and apps have to meet [WCAG 2.2 AA](https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps), and the government has been monitoring against 2.2 since October 2024. Private companies fall under the Equality Act’s general duty to make reasonable adjustments, which doesn’t name a version.

### Mobile apps

WCAG is written for web content, but it applies to apps in practice. W3C publishes WCAG2ICT, a guide to applying WCAG 2 to [non-web software, including mobile apps](https://www.w3.org/WAI/standards-guidelines/wcag/non-web-ict/), most recently updated in December 2025. EN 301 549 has a chapter for software that follows WCAG closely, and the EU and UK rules above cover apps explicitly. If your product is mainly an app, I’d treat the WCAG standards as fully yours.

### Do you have to update with every new version?

Legally, only when your rule changes, which is how the UK moved to 2.2 in 2024 and how the EU is moving now. In practice, updating as you go is the cheaper option: each step is small if you keep up, and a lot bigger if you skip two at once.

Here’s the checklist I’d use to decide which WCAG standards to aim for:

- Find the rule that applies to you, by market and by type of organization, and note the version it names.
- Check your contracts and tenders too. Enterprise clients and public buyers often ask for a WCAG level in their own terms.
- If two rules name different versions, follow the newer one.
- If nothing applies yet, aim for WCAG 2.2 AA anyway. It’s what the next round of rules points to.

## Where to start with WCAG standards

I keep thinking about how much of WCAG is stuff designers already argue for. Visible focus, readable contrast, labels that say what a field wants, forms that don’t punish you for a typo. The standard makes those arguments testable, and that’s what turns them from one designer’s preference into something a whole team can plan for.

If I had to pick one starting point, it would be WCAG 2.2 AA and the four principles behind it. Go through your most important flow with only a keyboard, then with a screen reader turned on, and you’ll find most of what matters in an afternoon. The [accessibility guide](https://www.iteratorshq.com/blog/accessibility-app-that-actually-works-your-wcag-implementation-guide/) covers the testing tools and the mistakes worth avoiding, and a [UX audit](https://www.iteratorshq.com/blog/ux-audit-and-how-it-impacts-your-business/) or a round of [user testing](https://www.iteratorshq.com/blog/a-comprehensive-guide-on-fundamentals-of-user-testing/) with people who use assistive technology will show you the rest.

Which brings me back to that ticket at the bottom of the backlog. Teams rarely skip accessibility because they disagree with it. They skip it because nobody made it part of what “done” means.
