- Accessibility Compliance
- November 20, 2026
WCAG 2.2 AA Compliance: A Practical Business Guide With 9 Clear Steps
If your website, app or digital product serves the public, accessibility is no longer something you can leave for later. Customers expect it, buyers ask for proof of it and laws in the US, Europe and elsewhere increasingly require it. For most organizations, the practical target is WCAG 2.2 AA compliance.
This guide explains what WCAG 2.2 AA means in plain language, what changed from WCAG 2.1, which laws point to it and the practical steps a business can take to reach and maintain conformance. It reflects how the IAAP-certified accessibility team at D2i Technology helps organizations get there.
What Is WCAG 2.2?
The Web Content Accessibility Guidelines (WCAG) 2.2 are published by the World Wide Web Consortium (W3C). They describe how to make digital content usable by people with disabilities, including people who are blind or have low vision, are deaf or hard of hearing, have motor disabilities or have cognitive and learning disabilities.
WCAG 2.2 was published in October 2023. It builds on WCAG 2.0 and 2.1, so content that meets WCAG 2.2 also meets the earlier versions, with one small exception: the old 4.1.1 Parsing criterion was removed because modern browsers and assistive technologies handle it differently.
WCAG is organized around four principles. Content must be:
- Perceivable: users can see or hear it, for example through alt text and captions.
- Operable: users can navigate and interact with it, including by keyboard.
- Understandable: content and interactions are clear and predictable.
- Robust: it works with current and future assistive technologies.
What Does “AA” Mean?
Each WCAG success criterion has a level: A, AA or AAA. Level A covers the most basic requirements. Level AA adds important requirements such as color contrast, visible focus and consistent navigation. Level AAA is the highest level and is not usually required for whole sites, because some criteria cannot be met for all content.
WCAG 2.2 AA compliance means meeting all Level A and Level AA success criteria, 55 in total. AA is the level referenced by most laws, policies and procurement requirements.
What Is New in WCAG 2.2
WCAG 2.2 added nine success criteria. Six of them apply at Levels A and AA:
2.4.11 Focus Not Obscured (Minimum), Level AA
When an element receives keyboard focus, it must not be completely hidden by other content, such as sticky headers, cookie banners or chat widgets.
2.5.7 Dragging Movements, Level AA
Anything that can be done by dragging, such as reordering items or using a slider, must also be possible with a single pointer action like clicking, unless dragging is essential.
2.5.8 Target Size (Minimum), Level AA
Clickable targets should be at least 24 by 24 CSS pixels, or have enough space around them, with some exceptions. This helps people with tremors or limited dexterity.
3.2.6 Consistent Help, Level A
If help options such as contact details, a chat or a help page appear on multiple pages, they should appear in the same relative place each time.
3.3.7 Redundant Entry, Level A
Users should not have to re-enter information they already provided in the same process, unless it is necessary, such as for security.
3.3.8 Accessible Authentication (Minimum), Level AA
Logging in should not require a cognitive test, such as remembering a password or solving a puzzle, unless an alternative or assistance is provided. Allowing password managers and copy-and-paste usually meets this. Our article on accessibility gaps in OTP and two-factor authentication looks at a common problem area.
The other three new criteria, 2.4.12, 2.4.13 and 3.3.9, are at Level AAA.
Which Laws Point to WCAG?
Several laws and standards reference WCAG, though not all use version 2.2 yet:
- ADA Title II: the Department of Justice rule for state and local governments adopts WCAG 2.1 AA. Check ADA.gov for current compliance dates.
- ADA Title III: covers businesses open to the public. Courts and settlements commonly use WCAG 2.1 or 2.2 AA as the benchmark.
- Section 508: applies to US federal agencies and references WCAG 2.0 AA.
- European Accessibility Act: applies to many products and services sold in the EU, using standards based on WCAG.
Because WCAG 2.2 includes everything in 2.0 and 2.1, aiming for WCAG 2.2 AA compliance puts you in a strong position for all of them. Our pages on ADA compliance and the European Accessibility Act cover these in more detail.
Why WCAG 2.2 AA Compliance Matters for Business
- Legal risk: accessibility lawsuits and demand letters remain common in the US.
- Sales: enterprise, education and government buyers often require a VPAT showing WCAG conformance before they buy.
- Customers: a significant share of people live with a disability, and accessible design helps older users, mobile users and people in difficult conditions too.
- Quality: accessible sites tend to have cleaner code, clearer content and better SEO.
9 Steps to WCAG 2.2 AA Compliance
1. Define Your Scope
List the websites, apps, documents and third-party tools that are part of your customer experience. Prioritize the journeys that matter most, such as sign-up, checkout, booking or applying for a service.
2. Run a Baseline Audit
Combine automated scans with manual testing using keyboards and screen readers such as JAWS, NVDA and VoiceOver. Automated tools catch only part of the issues. A proper WCAG audit gives you an accurate picture.
3. Prioritize the Findings
Fix issues that block users from completing key tasks first, then serious barriers, then minor issues. Group similar issues, because one fix to a shared component can resolve many problems at once.
4. Fix Shared Components
Most sites are built from templates and components: headers, navigation, forms, modals and buttons. Fixing these once improves every page that uses them.
5. Address the New 2.2 Criteria
Check focus visibility with sticky elements, provide alternatives to dragging, review touch target sizes, keep help in a consistent place, avoid asking users to re-enter information and make sure logins work with password managers.
6. Fix Content and Documents
Review alt text, headings, link text, video captions and PDFs. Content authors need simple guidance and training so new content stays accessible.
7. Retest
Confirm that fixes work with assistive technology, not just that a scan no longer reports them.
8. Document Conformance
Publish an accessibility statement and, if you sell to organizations, prepare a VPAT or Accessibility Conformance Report. See our VPAT services.
9. Build It Into Your Process
WCAG 2.2 AA compliance is not a one-time project. Add accessibility to design reviews, definition of done, code reviews and QA, and retest major releases. Our guide to integrating WCAG 2.2 into agile development shows how.
Common WCAG 2.2 AA Failures
In our audits, the same issues appear again and again:
- Low color contrast on text and buttons.
- Images without meaningful alt text.
- Form fields without proper labels or clear error messages.
- Interactive elements that cannot be reached or used with a keyboard.
- Missing or invisible focus indicators.
- Modals and menus that trap or lose keyboard focus.
- Videos without captions.
- Small, tightly packed touch targets on mobile.
Our free color contrast analyzer can help you check one of the most common problems quickly.
Most of these failures are cheap to fix when they are caught in design or development. They become expensive when they are spread across hundreds of pages and discovered only after launch, which is why early testing pays off so well.
Who Is Responsible for WCAG 2.2 AA Compliance?
Accessibility often fails because everyone assumes someone else owns it. In practice, WCAG 2.2 AA compliance depends on several roles working together:
- Designers choose colors, layouts, focus styles and target sizes, and annotate designs for headings, landmarks and reading order.
- Developers use semantic HTML, label form fields, manage focus and make custom components work with keyboards and screen readers.
- Content authors write alt text, clear headings, meaningful link text and accessible documents.
- QA testers include keyboard and screen reader checks in every test cycle.
- Procurement teams check that third-party tools, such as chat widgets, booking systems and payment pages, are accessible before they are bought.
- Leadership sets the policy, funds training and makes accessibility part of how success is measured.
Naming an accessibility lead who coordinates these roles makes a real difference.
What About Mobile Apps?
WCAG was written for the web, but its principles apply to native iOS and Android apps too, and many organizations use it as the standard for their apps. Mobile testing uses VoiceOver and TalkBack, checks support for larger text sizes and screen orientation, and pays close attention to touch target sizes, which the new 2.5.8 criterion addresses directly.
Do Accessibility Overlays Provide Compliance?
No. Overlay widgets that claim to make a site compliant with one line of code do not fix the underlying problems in your code and content. Many disabled users find them frustrating, and their use has not prevented lawsuits. Genuine WCAG 2.2 AA compliance comes from fixing the site itself.
Final Thoughts
WCAG 2.2 AA compliance is achievable for almost any organization with a clear scope, an honest audit, a sensible plan and accessibility built into everyday work. The new 2.2 criteria mostly reflect good, user-friendly design, and meeting them makes your product easier for everyone to use.
If you need to understand where you stand today, D2i Technology can audit your site or app against WCAG 2.2 AA, fix what we find and document your conformance. Explore our accessibility services to learn more.
Frequently Asked Questions
Find Out How Close You Are to WCAG 2.2 AA
D2i Technology's IAAP-certified team audits your website or app against WCAG 2.2 AA with real assistive technology, fixes the issues and documents conformance. Tell us about your deadline and we will suggest a plan.