Bloomlight University · Accessibility

What is WCAG?

The accessibility standard behind audits and the law: its versions, its A, AA and AAA levels, and the success criteria you'll meet most.

WCAG, the Web Content Accessibility Guidelines, is the standard the world uses to decide whether a website works for people with disabilities. It's what accessibility audits test against, and what most accessibility laws point to. Here's how it's put together, what the levels mean, and where to start.

Who writes it

WCAG is published by the World Wide Web Consortium (W3C), the body behind web standards like CSS, through its Web Accessibility Initiative. It's written in the open, with input from browser makers, disability organizations, governments and accessibility experts, and it's free to read at w3.org/WAI.

The versions

  • WCAG 1.0 (1999) was the first version. Nobody tests against it anymore.
  • WCAG 2.0 (2008) set the structure every later version keeps.
  • WCAG 2.1 (2018) added criteria for phones, low vision and cognitive disabilities, including contrast for buttons and icons, and pages that work zoomed in.
  • WCAG 2.2 (2023) is the current version. It added criteria for keyboard focus, the size of tap targets, and sign-in steps that don't rely on memory or puzzles. It's also an international standard, ISO/IEC 40500.

Each 2.x version builds on the one before, so a site that meets WCAG 2.2 also meets 2.1 and 2.0. W3C is also working on WCAG 3, a larger rewrite that's still a draft. Until it's finished, WCAG 2.2 is the one to aim for.

The four principles

Everything in WCAG hangs off four principles, often shortened to POUR:

  • Perceivable: people can see or hear the content, whatever their senses. Images have text alternatives, videos have captions, and text has enough contrast to read.
  • Operable: people can use the site however they get around it. Every control works from a keyboard, nothing flashes in a way that can cause seizures, and people get enough time to finish what they started.
  • Understandable: the content and the interface make sense. The page says what language it's in, forms explain what they need, and errors say how to fix them.
  • Robust: the site works with the browsers and assistive technology people use, like screen readers. In practice, that means using HTML the way it was meant to be used, so every control has a name and a role a screen reader can announce.

Guidelines and success criteria

Under the principles sit guidelines, such as "Distinguishable" or "Keyboard Accessible". The guidelines aren't testable on their own. Under each one sit the success criteria, and those are what an audit checks. Each success criterion has a number, a name and a level, and is written so that a page either passes it or fails it. WCAG 2.2 has 86 of them.

The number tells you where a criterion sits. 1.4.3 Contrast (Minimum) is the third criterion under guideline 1.4, Distinguishable, under principle 1, Perceivable. When an audit or a finding quotes a WCAG number, that's what it means.

Levels A, AA and AAA

Every success criterion has one of three levels. A page meets a level when it passes every criterion at that level and every level below it.

  • Level A is the floor. Missing one of these usually locks someone out completely: an image button with no text, or a menu that only opens with a mouse.
  • Level AA is the target. It's the level laws, contracts and audits almost always ask for, and it includes the contrast ratios most designers know: 4.5:1 for body text.
  • Level AAA is the strictest. W3C doesn't expect whole sites to meet it, because some content can't. It's worth reaching for where you can, like long passages of body text.

The success criteria you'll meet most

You don't need to memorize 86 criteria. A handful cause most of the problems on real websites:

  • 1.1.1 Non-text Content (A): images that carry meaning need alt text. Decorative images need an empty one, so screen readers skip them.
  • 1.3.1 Info and Relationships (A): headings, lists, tables and form labels are marked up as what they are, not just styled to look like them.
  • 1.4.3 Contrast (Minimum) (AA): text needs a contrast ratio of at least 4.5:1 against its background, or 3:1 for large text.
  • 1.4.10 Reflow (AA): pages work at 320 CSS pixels wide, the width of a desktop browser zoomed to 400%, without scrolling sideways.
  • 1.4.11 Non-text Contrast (AA): buttons, form fields and icons that mean something need a contrast ratio of at least 3:1 against what's next to them.
  • 2.1.1 Keyboard (A): everything that works with a mouse works with a keyboard too.
  • 2.4.4 Link Purpose (In Context) (A): people can tell where a link goes from its text and its surroundings. A page full of "Click here" fails it.
  • 2.4.7 Focus Visible (AA): keyboard users can see which element they're on.
  • 2.5.8 Target Size (Minimum) (AA): new in WCAG 2.2. Buttons and links are at least 24 by 24 CSS pixels, or spaced out enough that a finger won't hit the wrong one.
  • 3.1.1 Language of Page (A): the page says what language it's in, so screen readers pronounce it properly.
  • 3.3.2 Labels or Instructions (A): form fields have labels that say what goes in them.
  • 4.1.2 Name, Role, Value (A): custom controls tell assistive technology what they are, what they're called and what state they're in.

Color contrast, in detail

Contrast is one of the most common accessibility failures, and one of the easiest to fix. WCAG measures it as a ratio between the relative brightness of two colors, from 1:1 (the same color on itself) to 21:1 (black on white). Three success criteria use it:

  • AA, normal text: 4.5:1.
  • AA, large text: 3:1. Large means at least 24px, or at least 18.66px in bold.
  • AAA: 7:1 for normal text, 4.5:1 for large text.
  • Buttons, fields and icons: 3:1, at level AA.

Logos, text in disabled controls, and text that's purely decorative are exempt. The free color contrast checker shows the ratio for any pair of colors, and when a pair fails, it finds the nearest shade that passes without changing the hue.

WCAG and the law

WCAG isn't a law itself, but many laws and regulations point to it, usually at level AA. A few you may run into:

  • United States: Section 508 requires WCAG 2.0 AA for federal agencies' websites. In 2024, the Department of Justice adopted WCAG 2.1 AA as the standard for state and local government websites under the Americans with Disabilities Act. Courts also hear ADA lawsuits about businesses' websites, and WCAG is the yardstick those cases use.
  • European Union: the European Accessibility Act has applied since June 2025 to many products and services sold to consumers, including online shops and banking. Websites are measured against the European standard EN 301 549, which uses WCAG 2.1 AA. A new version that moves to WCAG 2.2 was published in 2026.
  • United Kingdom: public sector websites must meet the Public Sector Bodies Accessibility Regulations, which the UK government measures against WCAG 2.2 AA.

Laws change, and which ones apply depends on where you are, who your customers are and what you sell. Check with a lawyer for your own situation. Whatever applies, WCAG 2.2 AA covers the earlier versions those laws name.

How to check your site

Automated checks are the place to start. They're fast, they cover every page, and they catch the common problems: missing alt text, low contrast, missing labels, the wrong language. But a tool can't tell whether alt text describes the image well, or whether a page makes sense to someone using a screen reader. For that, try your pages yourself:

  • Put the mouse away and get through your main tasks with only the Tab, Enter, Space and arrow keys. Watch for places where you lose track of where you are.
  • Zoom your browser to 200%, then 400%, and check that nothing gets cut off or overlaps.
  • Turn on the screen reader built into your computer or phone, VoiceOver on Apple devices or Narrator on Windows, and listen to a page from the top.

How Bloomlight helps

Bloomlight runs an accessibility audit on your key pages every day and sweeps the rest of your site as capacity allows. Each problem it finds becomes a finding that says what's wrong, where it is on the page, and how to fix it. Contrast findings open the same tuner as the free checker, already set to the failing colors. Turning findings into fixes walks you through working the list.

Start watching your site — free, today.

Two minutes to add your domain. First report in your inbox within the hour.