What WCAG is
WCAG stands for the Web Content Accessibility Guidelines. It is the international standard for making websites that disabled people can use.
That includes people who are blind or have low vision. It includes people who are deaf, cannot use a mouse, or have tremors. It also includes people who find busy pages hard to follow.
Up to 1 in 4 US adults have a disability, says the CDC, the US public health agency. Worldwide, the World Health Organization (WHO) puts it at about 1 in 6 people.
WCAG is written by the W3C, the group that looks after web standards. Nearly every accessibility law in the world points to it.
Four ideas hold it together
Content must be:
- PerceivablePeople can take it in.Images have text descriptions. Videos have captions. Text has enough contrast with its background.
- OperablePeople can use it.Everything works with a keyboard alone. Buttons and links are big enough to tap. Nothing traps or rushes the visitor.
- UnderstandablePeople can follow it.Forms explain their errors. Menus stay the same from page to page. The page states its language, so screen readers (software that reads pages aloud) say words correctly.
- RobustAssistive tools can read it.The code says what each control is. So a screen reader knows a button is a button.
Each idea breaks down into testable rules, called success criteria. A site that “meets WCAG 2.2 AA” passes every rule in version 2.2 at levels A and AA.
WCAG 2.1 and 2.2: what changed
Each version builds on the one before. WCAG 2.1 came out in 2018. It kept everything in 2.0. It added rules for phones, low vision and people who find complex pages hard to take in.
WCAG 2.2 came out in October 2023. It is the current version. It keeps everything in 2.1 and adds nine new rules, mostly about focus, touch targets and forms. “Focus” is the outline that shows where you are when you use a keyboard.
One old rule, about how browsers read code, was dropped. Modern browsers had made it unnecessary.
The key point: a site built to 2.2 AA also meets 2.1 AA. The newer version contains the older one.
These are the nine additions:
| New rule | Level | What it means in practice |
|---|---|---|
| Focus Not Obscured (Minimum) | AA | When you tab to an item, sticky headers or cookie bars never hide it completely. |
| Focus Not Obscured (Enhanced) | AAA | The item you tab to is never hidden at all, not even partly. |
| Focus Appearance | AAA | The keyboard focus outline is clear and big enough to spot. |
| Dragging Movements | AA | Anything you do by dragging, like sliders or reordering, also works with simple clicks or taps. |
| Target Size (Minimum) | AA | Buttons and links are at least 24 by 24 pixels, or spaced so people rarely tap the wrong one. |
| Consistent Help | A | Contact details and help links sit in the same place on every page. |
| Redundant Entry | A | Forms never ask for the same information twice in one process. |
| Accessible Authentication (Minimum) | AA | Logging in never relies on remembering or retyping something. Password managers and pasting must work. |
| Accessible Authentication (Enhanced) | AAA | The same rule, with fewer exceptions allowed. |
If your site already meets 2.1 AA, reaching 2.2 AA is usually days of work. Most of it is focus styles, target sizes and login forms.
The three levels: A, AA and AAA
Each rule has a level. Each level includes the one below it.
Level A: the floor
Failing it locks some visitors out completely. Think images with no descriptions, pages a keyboard cannot use, or videos with no alternative.
Level AA: the usual target
This is what almost every law, contract and buying checklist means by “accessible”. It adds minimum contrast, visible focus, error suggestions, consistent menus and text resizing.
Level AAA: the extra mile
Higher contrast, sign language for video and simpler language. Whole sites rarely claim it, and no major law requires it. Sensible teams adopt single AAA rules where they are cheap, and skip the rest.
In short: A means people can get in. AA means people can actually use it. AAA means you went further than the law asks.
When a client brief, a tender or a lawyer says “WCAG”, read it as AA unless it says otherwise.
The dates that matter
You do not need to learn the laws by heart. You need to know which ones name a version and a date. That is what buyers, insurers and purchasing teams check.
United States: state and local governments
The Department of Justice (DOJ) has a rule under Title II of the Americans with Disabilities Act (ADA). It says state and local government websites must meet WCAG 2.1 AA.
- Areas with 50,000 people or more
- Smaller areas
These deadlines were extended in April 2026. If you sell websites to a city, county, school district or public university, the rule reaches you too.
United States: groups funded by HHS
The Department of Health and Human Services (HHS) has a similar rule under Section 504. It covers groups that get HHS funding. They must also meet WCAG 2.1 AA.
- Groups with 15 or more staff
- Groups with fewer than 15 staff
United States: private businesses
No US rule names a WCAG version for private businesses. But when web access is challenged, courts and the DOJ have consistently pointed to WCAG as the standard.
At the time of writing, lawsuits against ordinary business websites are filed every week.
European Union
The European Accessibility Act (EAA) has applied since . It covers many products and services, including online shops selling to EU consumers.
Micro-businesses are exempt for services. That means fewer than 10 staff, and a yearly turnover or balance sheet of €2 million or less.
The EU’s technical standard is EN 301 549. Version 3.2.1 points to WCAG 2.1 AA. Version 4.1.1 lines up with WCAG 2.2.
- EAA applies
- EN 301 549 v4.1.1 published
The EU is expected to list version 4.1.1 in its Official Journal later. From then on, the reference moves to WCAG 2.2.
United Kingdom
Public sector websites have been regulated since 2018. At the time of writing, the government’s monitoring body tests them against WCAG 2.2 AA.
Elsewhere
Canada, Australia and other countries point to WCAG AA in their own rules. The pattern is the same everywhere: AA, with the named version slowly moving forward.
Notice the direction. Laws are settling on WCAG AA, and the named version only ever moves forward. That is the case for building to 2.2 AA today. Patching to 2.1 AA now just means patching again later.
This guide is general information, not legal advice. We are not lawyers, so legal questions belong with your own lawyer.
What to fix first on a business website
A few rules do most of the work for most visitors. If time or budget is short, fix these first, roughly in this order:
- Keyboard access. Every menu, form and pop-up works with Tab and Enter alone. You can always see which item has focus.
- Colour contrast. Body text has a contrast ratio of at least 4.5 to 1 with its background. At the time of writing, low contrast is the most common failure on the web.
- Names and labels. Every image has a description. Every form field has a label. Every button and link says what it does.
- Forms that explain themselves. Errors are announced and described in text. They tell the visitor how to fix the problem.
- Target size and spacing. Tap targets are at least 24 pixels. Links are not crowded together.
- Structure. Real headings in a sensible order. The page states its language. A skip link lets keyboard users jump past the menu on every page.
The problems we find most often
Each year, WebAIM scans the home pages of the top million websites. At the time of writing, well over 9 in 10 have WCAG failures that software can spot. The same few problems top the list every year. What we find matches that list:
- Text over images, or light grey text, that fails contrast.
- Images with no description, or a file name where the description should be.
- Links that say “click here” or “read more”, with nothing about where they go.
- Form fields with placeholder text instead of labels.
- Menus and carousels that only work with a mouse.
- No visible focus outline. It was usually removed on purpose, years ago, for looks.
- PDFs that are scans of paper. No screen reader can read them.
- Video or animation that plays by itself, with no way to stop it.
Most of these are cheap to fix once found. Finding all of them takes discipline. Software cannot test roughly a third of the rules at all, so a person has to check those.
What the work involves
Real accessibility work is a cycle. It looks the same whether we built your site or someone else did.
Audit
First, software scans every template. A template is a shared layout that many pages use. Then a person tests by hand.
They use only a keyboard, run a screen reader and zoom to 200%. They also fill in forms wrongly on purpose.
You get a list of failures. Each one is tied to the rule it breaks, and ranked by how badly it blocks a visitor.
Repair
Fixes go into the site’s own code and content, starting with the worst blockers.
On a typical business site, most of the work sits in templates. Fix one template and you fix hundreds of pages.
Verify
The same tests run again.
The results are written up, so you can show whoever asked: a customer, a buying team or a lawyer.
Maintain
Every edit your team makes can add a new problem. So accessibility is re-checked as content changes.
The statement page stays current, and new features are tested before launch. That is why our care plans include accessibility re-checks. The audit is not a one-off.
The baseline we recommend, and why
Clients ask us to just pick a standard for them. So here it is, with our reasons in the open.
Our recommendation
Build new work to WCAG 2.2 AA. If a law or contract names WCAG 2.1 AA, report against that too. Your work already covers it.
- Why AA and not A?
- Every law, tender and checklist that names a level names AA. Level A alone still locks visitors out, and it leaves buyers unhappy.
- Why 2.2 and not 2.1?
- Version 2.2 contains all of 2.1, and the additions are modest. Regulators are already moving to it. Building to the older version gains nothing. It just books a second round of work later.
- Why not AAA?
- No law requires it, and parts of it are impractical for most organisations. We adopt the cheap AAA habits, like strong focus outlines, and say so. We do not claim a level we could not honestly hold across a whole site.
- And for the long term?
- Treat accessibility like security. It is something you maintain, not a certificate you frame. Re-check when content changes. Keep the statement page honest. Put someone’s name on it.
For our own builds, this is not an extra. The standard is part of the quote. An accessibility statement comes with every site. Our 30 days of help after launch cover your editors’ questions about keeping new content accessible.
Need help with a site you already have? See our accessibility audits and fixes.
Check your site free
Our free checker reads a page. It lists common problems in plain language, with a fix for each. Each problem shows the WCAG rule it relates to. A few are good practice, not rules.
It is a first look, and we label it honestly. Software catches the mechanical problems. Rules that need human judgement still need a person.
Useful outside resources
- WCAG at a glance (opens in a new tab): the W3C’s own two-minute summary.
- How to meet WCAG 2.2 (opens in a new tab): the full checklist, which you can filter by level.
- WebAIM contrast checker (opens in a new tab): test any two colours in seconds.