The Complete WCAG 2.2 Checklist for Business Owners
WCAG 2.2 contains 87 success criteria organized under four principles: Perceivable, Operable, Understandable, and Robust. For Level AA compliance — the standard courts and regulators reference — you need to meet all Level A and Level AA criteria. Here are the key areas business owners need to understand.
Perceivable means users must be able to perceive the information being presented. This includes: providing text alternatives for non-text content (images, videos, audio), providing captions and audio descriptions for multimedia, creating content that can be presented in different ways without losing meaning, and making it easy for users to see and hear content.
Operable means users must be able to operate the interface. All functionality must be available from a keyboard. Users must have enough time to read and use content. Content must not cause seizures or physical reactions. Users must be able to navigate and find content. Input must be possible through various modalities beyond just keyboard.
Understandable means users must be able to understand the information and operation of the user interface. Text must be readable and understandable. Web pages must appear and operate in predictable ways. Users must be helped to avoid and correct mistakes, especially in forms.
Robust means content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies. This primarily means using valid, semantic HTML and ensuring custom widgets properly communicate their role, state, and value to assistive technologies.
New in WCAG 2.2 are criteria addressing focus visibility, dragging alternatives, minimum target sizes, consistent help mechanisms, and accessible authentication. These additions reflect the growing importance of mobile accessibility and cognitive accessibility.
Need help finding an ADA-compliant agency?
Compare verified agencies in our directory — no overlay vendors listed.
Browse the Directory →Authoritative sources & further reading
This page aligns with the standards and guidance published by the following authorities. We cite them so you can verify every compliance claim independently.
- What Is the ADA? — Plain-Language Primer (opens in a new tab)
WhatIsADA.com. A plain-language explainer on the Americans with Disabilities Act — who it covers, the three titles, and how it applies to physical and digital access.
- Guidance on Web Accessibility and the ADA (opens in a new tab)
U.S. Department of Justice — ADA.gov. The DOJ’s official position that the ADA applies to the websites of state/local governments (Title II) and businesses open to the public (Title III), and that WCAG is the practical conformance standard.
- Introduction to Web Accessibility (opens in a new tab)
W3C Web Accessibility Initiative (WAI). The W3C WAI overview of what web accessibility is, why it matters, and how WCAG (the Web Content Accessibility Guidelines) defines conformance.
- Examples of ADA Compliant Websites (opens in a new tab)
AccessibilityChecker.org. Worked examples of accessible sites and the patterns — semantic structure, contrast, keyboard support — that make a website ADA compliant in practice.
- How to Make Websites Accessible (opens in a new tab)
Government of Ontario (AODA). Ontario’s practical, WCAG-aligned guidance issued under the AODA — a useful cross-jurisdiction reference for the same conformance targets used in U.S. ADA work.
Frequently Asked Questions
How many WCAG 2.2 criteria do I need to meet for AA compliance?
WCAG 2.2 Level AA requires meeting all 57 Level A and AA success criteria. This includes all Level A criteria (the baseline) plus additional Level AA criteria for color contrast, text resizing, and other enhanced accessibility features.
What is the difference between WCAG Level A, AA, and AAA?
Level A is the minimum level addressing the most critical barriers. Level AA addresses the most common barriers and is the standard for legal compliance. Level AAA is the highest standard and includes criteria that may not be achievable for all types of content.
How often should I audit for WCAG 2.2 compliance?
Conduct a comprehensive audit annually, with automated monitoring running continuously. Any time you make significant changes to your website (new features, redesign, new content types), conduct a targeted accessibility review of the changed areas.