WCAG compliance means every full page and every complete process on your site passes all success criteria at your chosen level, usually AA, along with the five conformance requirements that W3C sets out. It is a yes or no state for each page, not a percentage, and it can slip the moment new content goes live.
W3C itself uses the word "conformance". Lawyers, procurement teams and search boxes say "compliance". On this page the two mean the same thing: content that meets the standard, proven by testing.
Quick facts
Usual target
WCAG 2.1 AA for most laws, 2.2 AA for new builds.
What it covers
Full pages and complete user journeys, including third party parts you publish.
Pass rule
All criteria at the target level and below. One failure means the page does not conform.
How it is shown
An audit report, an accessibility statement, and for vendors an ACR built on a VPAT.
Tool coverage
Automated scans catch about a third of issues. Manual testing is not optional.
What is WCAG compliance?
When someone says a site is "WCAG compliant", they are making three claims at once: a version number, a level, and the set of pages it covers. A claim that leaves out any of those is too vague to check.
In digital accessibility, WCAG compliance ensures that people using assistive technology, keyboards, zoom or captions can complete the same tasks as everyone else: read the content, fill in the form, pay, sign in. It does not mean every person will find the site easy. WCAG is a floor, not a ceiling.
| Phrase you hear | What it should mean |
|---|---|
| WCAG compliant | Meets every criterion at a stated version and level |
| WCAG conformance | The W3C term for the same idea, defined in the standard itself |
| Partially conformant | Most criteria met, some known failures, listed openly |
| Substantially compliant | Not a WCAG term; usually used in legal settlements |
| Accessibility score 98 | A tool vendor's metric, not a conformance result |
The five WCAG conformance requirements
Passing the success criteria is only part of it. WCAG lists five conformance requirements that every claim must satisfy. You can read the exact wording in the WCAG 2.2 specification under Conformance.
| Requirement | In plain words | Common trap |
|---|---|---|
| Conformance level | Pass everything at your chosen level plus all lower levels | Claiming AA while skipping some level A items |
| Full pages | The claim covers a whole page, not a part of it | Excluding the header, footer or a chat widget |
| Complete processes | Every step of a multi-step task conforms | An accessible cart with an inaccessible payment step |
| Accessibility supported technologies only | Rely only on ways of using technology that assistive tech can handle | A custom widget that works in one browser only |
| Non-interference | Extra technology must not block the rest of the page | Autoplaying audio or a keyboard trap in an embedded player |
Content you embed from others still counts. If a booking form or video player you chose fails, the page fails. You may note it in a statement of partial conformance, but you cannot leave it out of scope.
Which version and level to aim for
Pick the version and level before testing, because it changes the list of criteria.
| Situation | Sensible target | Why |
|---|---|---|
| Private business in the US | WCAG 2.1 AA | DOJ settlements and courts usually cite it |
| US state or local government | WCAG 2.1 AA | Named in the ADA Title II web rule |
| Selling to US federal agencies | WCAG 2.0 AA | Section 508 still points there, though newer is fine |
| Selling into the EU | WCAG 2.1 AA via EN 301 549 | The EAA and public sector directive rely on it |
| UK public sector | WCAG 2.2 AA | Government guidance now asks for 2.2 |
| New site with no legal driver | WCAG 2.2 AA | Covers every older version at once |
Because the 2.x versions build on each other, a site passing the newest AA set automatically passes the earlier AA sets too. The one quirk is the old parsing criterion, which W3C now treats as always met for HTML. More on this in the guide to the three levels.
How to become WCAG compliant, step by step
This is the process an auditor follows. A small team can run most of it in house.
- Define scope: the version and level, plus a sample of page types and the key journeys such as sign up, search and checkout.
- Scan each template with automated checkers and fix definite failures first.
- Test by hand against each criterion: keyboard only, 200 and 400 percent zoom, text spacing, contrast, captions.
- Run the key journeys with at least one screen reader and one mobile setup.
- Log every issue with the criterion number, severity and a suggested fix.
- Fix shared components so the repair spreads to every page that uses them.
- Retest, then write your accessibility statement with known gaps and a contact for feedback.
- Build checks into design reviews, code reviews and content publishing so compliance holds.
For an outside review, see what an accessibility audit involves.
WCAG compliance tools and their limits
No single product delivers WCAG compliance. A realistic toolkit has four layers, and each finds things the others miss.
| Tool type | What it finds | What it misses |
|---|---|---|
| Automated page scanner | Missing alt, empty buttons, low contrast in plain CSS, missing form labels | Whether alt text is accurate, logical order, keyboard traps |
| Browser extension checker | The same rules, on pages behind a login, with highlighting | Anything that needs human judgement |
| Contrast checker | Exact ratios for text and interface parts | Text on images and gradients without sampling |
| Screen reader and keyboard | Real experience: names, order, announcements, traps | Nothing on its own, but it needs skill and time |
Two of the most common failure areas have free tools here: the contrast checker and the image description audit tool.
Toolbar overlays that promise instant WCAG compliance cannot rewrite your markup or your content. Disabled users often switch them off, and regulators have not accepted them as a fix.
A small fix with a big effect
Many compliance gaps are small markup choices. Here is a typical one from a sign-up form.
Fails three criteria (1.3.1, 3.3.2, 4.1.2): the hint sits in a placeholder and nothing names the field.
<input type="email" placeholder="Email">Passes: a visible label tied to the field, plus autocomplete for 1.3.5.
<label for="em">Email address</label>
<input id="em" type="email"
autocomplete="email" required>Fixing the shared form component once repairs every form that uses it, which is why component fixes come first.
Proving compliance to buyers and regulators
Compliance you cannot show is hard to defend. Three documents carry the evidence.
- Audit report. Lists what was tested, how, and every issue by criterion and severity.
- Accessibility statement. A public page with your target, known gaps, the date of the last review and a way to report problems. UK public bodies must publish one.
- VPAT and ACR. Vendors complete a VPAT form, and the completed version is called an ACR (Accessibility Conformance Report). Many public and corporate buyers request one.
Keep test notes and retest results. If a complaint arrives, a record of steady work counts for more than a one-off badge. Ask a lawyer how this applies to your organisation; this page is not legal advice.
Questions people ask
What does WCAG compliant mean?
It means a page meets every success criterion at a stated WCAG version and level, such as 2.1 AA, and satisfies the five conformance requirements. A claim should always name the version, the level and the pages it covers.
Is WCAG compliance the same as WCAG conformance?
In everyday use, yes. Conformance is the formal W3C word defined inside WCAG. Compliance is the word used in laws, contracts and procurement, and it usually means conformance to a named version and level.
What are the WCAG requirements for a website?
For level AA under WCAG 2.2 there are 55 success criteria covering things like text alternatives, captions, contrast, keyboard use, focus, forms and status messages. Under 2.1 AA there are 50. On top of those come the five conformance requirements.
Can a website be 100 percent WCAG compliant?
A site can conform fully at a level on the day it is tested. Content changes, so it needs regular checks to stay that way. Be careful with anyone who promises permanent compliance from a tool or plugin.
Which tools are best for WCAG compliance?
Use a mix: an automated scanner, a browser extension checker, a contrast checker and real screen reader and keyboard testing. Free options are compared on our WCAG checkers page. No tool on its own can certify compliance.
Does WCAG compliance protect me from lawsuits?
It greatly reduces risk and shows good faith, but no standard makes a site immune from claims. Laws differ by country, so get advice from a lawyer who knows your market.