How to Make a Website WCAG 2.2 AA Compliant
To bring a website to WCAG 2.2 Level AA, set the scope, run a first review with W3C's Easy Checks, then test every template with automated tools, a keyboard and a screen reader. Fix shared templates and components first, then content such as images, video and forms. Publish an accessibility statement and recheck after every change. W3C says no tool alone can determine conformance, so human testing is part of the job.
- WCAG 2.2 is organized under four principles: perceivable, operable, understandable and robust, with success criteria at levels A, AA and AAA.
- Level AA conformance means meeting the Level A and Level AA criteria.
- WCAG 2.2 added nine success criteria, six of them at Level A or AA, and removed 4.1.1 Parsing.
- Content that conforms to WCAG 2.2 also conforms to 2.1 and 2.0.
- Automated tools find part of the problem. W3C says knowledgeable human evaluation is required.
Free tool: Marketing ROI Calculator → Work out your cost per customer, return on ad spend and payback.
The Steps
- Set the target and the scopeWrite down the goal: WCAG 2.2 Level AA. List what is in scope: every page template, the checkout or booking flow, forms, PDFs, videos and any third-party widgets such as chat or scheduling.
- Run W3C's Easy ChecksUse the Easy Checks on your key pages for a first look: image alt text, page title, headings, color contrast, skip link, visible keyboard focus, page language, zoom, captions, transcripts, form labels and required fields.
- Test with tools, a keyboard and a screen readerRun an automated scanner on each template to catch the mechanical errors. Then unplug the mouse and tab through each page. Finish with a screen reader pass on the main tasks, such as requesting a quote or checking out.
- Fix templates and shared components firstRepair the header, navigation, footer, buttons, cards and form components before single pages. One fix to a shared component corrects every page that uses it.
- Fix keyboard and focus behaviorMake every link, button, menu and control reachable and usable by keyboard, with a visible focus indicator that is not hidden behind sticky headers or banners. Give any drag action a click or tap alternative.
- Fix content: images, video and documentsWrite alt text that says what each image shows or does. Add captions to videos and transcripts to audio. Use real headings in order, and make link text describe where the link goes.
- Fix forms and loginGive every field a visible label, mark required fields in text as well as color, and write error messages that say what to fix. Do not ask for the same information twice, and allow password managers and paste on login.
- Publish an accessibility statementState your commitment, the standard you apply, such as WCAG 2.2, and how to contact you if someone hits a problem. W3C lists these three items as the minimum.
- Build it into maintenanceRetest after each new page, plugin, theme update or redesign. Train whoever adds content to write alt text, use headings properly and caption video.
What WCAG 2.2 AA Conformance Means
WCAG, the Web Content Accessibility Guidelines, is the W3C's technical standard for accessible web content. The WCAG 2 Overview lays out the structure: four principles (perceivable, operable, understandable, robust), 13 guidelines in WCAG 2.2, and testable success criteria under each guideline at three levels, A, AA and AAA.
Level AA is the target most organizations use. It means your pages meet the Level A and Level AA success criteria. W3C encourages using the latest version, and because the versions are backwards compatible, a site that conforms to 2.2 also conforms to 2.1 and 2.0.
A note on words. WCAG uses "conformance" for meeting the standard. "Compliance" usually refers to a law. This guide is about the technical standard. It is not legal advice, and meeting WCAG is not a promise about any legal outcome. For the legal background, see does my website need to be ADA compliant.
What Changed in WCAG 2.2
If your site was built or audited against 2.1, these are the additions to check. W3C's What's New in WCAG 2.2 lists nine new success criteria. Six are at Level A or AA:
| Success criterion | Level | In plain terms |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | The item with keyboard focus is not entirely hidden by sticky headers, banners or pop-ups |
| 2.5.7 Dragging Movements | AA | Anything done by dragging can also be done with a single click or tap |
| 2.5.8 Target Size (Minimum) | AA | Clickable targets are at least 24 by 24 CSS pixels, or spaced so they do not crowd each other |
| 3.2.6 Consistent Help | A | Help options such as a phone number or chat appear in the same relative order on each page |
| 3.3.7 Redundant Entry | A | Information already entered in a process is filled in or selectable, not asked for again |
| 3.3.8 Accessible Authentication (Minimum) | AA | Login does not depend on a memory test or puzzle unless there is another way or assistance |
The other three are Level AAA. One older criterion, 4.1.1 Parsing, is obsolete and was removed. All of these have exceptions, so read the full text before you rule a page in or out.
How to Test: Three Layers
W3C's evaluation overview is direct about the limits of software: "no tool alone can determine if a site meets accessibility standards." Plan for three layers.
1. Easy Checks
W3C's Easy Checks are a first review anyone can do without special skills. They cover alt text, page titles, headings, contrast, skip links, visible focus, page language, zoom, captions, transcripts, audio description, form labels and required fields. W3C is clear that they "cover just a few accessibility issues" and that a page can pass them and still have significant barriers.
2. Automated scan
A scanner is fast at finding missing alt attributes, empty buttons, unlabeled fields and contrast failures. Run it on one example of every template, not just the home page.
3. Manual testing
This is where most real barriers show up. Put the mouse away and complete your main tasks with Tab, Shift+Tab, Enter, Space and the arrow keys. Can you see where you are at all times? Can you open the menu, close the pop-up, submit the form? Then repeat with a screen reader and listen to whether the page makes sense read aloud. W3C also recommends involving people with disabilities in evaluation throughout a project.
Fix in the Right Order
A long scan report is discouraging until you sort it. A workable order:
- Blockers on money pages. Anything that stops a person from calling, booking, buying or submitting a form.
- Shared components. Header, menu, footer, buttons, modals and form fields. Each fix repeats across the site.
- Templates. Heading structure, landmarks, page titles and the language attribute.
- Content. Alt text, link text, captions, transcripts and documents.
- Third-party widgets. Chat, booking, maps and review embeds. If a vendor's widget fails and cannot be fixed, replace it or provide another way to do the same task.
The site's build affects how hard this is. A custom theme you control can be fixed at the source. A page builder with dozens of plugins may fight you. If a rebuild is on the table anyway, it is often cheaper to build accessibility in than to patch the old site. See WordPress vs Webflow vs custom for the tradeoffs.
Keep It That Way
A site that passes today can fail next month after one new plugin or one uncaptioned video. Three habits hold the line:
- An accessibility statement. W3C's guide to developing an accessibility statement says it should contain at least a commitment to accessibility, the standard applied and contact information for people who run into problems.
- A content checklist for whoever publishes: alt text, real headings, descriptive links, captions.
- Scheduled retests after updates and redesigns, with the results kept on file.
If You Want Help
DR3AM Systems audits websites against WCAG 2.2 Level AA, fixes the code and content, retests and documents the work as part of its ADA website compliance service. We do not promise legal compliance or protection from claims. Audits and remediation are quoted after a free strategy call. Book a call to go over your site.
Sources and Further Reading
We link to the primary documentation so you can verify the details yourself.
- WCAG 2 Overview, W3C Web Accessibility Initiative (WAI)
- What's New in WCAG 2.2, W3C Web Accessibility Initiative (WAI)
- Evaluating Web Accessibility Overview, W3C Web Accessibility Initiative (WAI)
- Easy Checks: A First Review of Web Accessibility, W3C Web Accessibility Initiative (WAI)
- Developing an Accessibility Statement, W3C Web Accessibility Initiative (WAI)
Related Questions
What is the difference between WCAG Level A, AA and AAA?
They are three levels of success criteria. Level A covers the most basic requirements, AA adds more, and AAA is the most demanding. Conforming at AA means meeting both the A and AA criteria. Most organizations target AA, and it is the level named in the Department of Justice rule for state and local government websites.
If my site met WCAG 2.1 AA, what else do I need for 2.2?
Check the six new Level A and AA criteria: focus not obscured, dragging movements, target size, consistent help, redundant entry and accessible authentication. Everything from 2.1 still applies, except 4.1.1 Parsing, which was removed. A site that conforms to 2.2 also conforms to 2.1.
Can I test my site myself without a developer?
You can do a useful first pass. W3C's Easy Checks need no special skills, and tabbing through your own pages with the keyboard reveals a lot. W3C notes that these checks cover only a few issues and that a fuller assessment is needed to evaluate accessibility comprehensively, so treat your results as a starting list.
Do the videos on my site need captions?
Captions are part of accessible video. They appear in W3C's Easy Checks alongside transcripts and audio description, and ADA.gov lists videos without captions among its examples of website barriers. Auto-generated captions are a start, but review and correct them before you rely on them, especially names, prices and technical terms.
Should I wait for WCAG 3 before doing this work?
No. W3C describes WCAG 3 as an early draft of the W3C Accessibility Guidelines 3.0. WCAG 2.2 is the current published standard, and W3C encourages using the latest version. Work done against 2.2 fixes real barriers for visitors today.
