WCAG Compliance: The Complete Guide to Conformance in 2026
WCAG compliance explained — POUR principles, conformance levels A/AA/AAA, version differences, and which laws require it. The global standard behind ADA, EAA, Section 508, and more.
What WCAG actually is
The Web Content Accessibility Guidelines (WCAG) are a set of technical standards published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI). They define how to make digital content — websites, apps, PDFs, multimedia — usable by people with disabilities.
WCAG is not a law. It is a technical specification. But it has become the global reference point for digital accessibility legislation. When a law says “accessible,” it almost always means WCAG compliant at Level AA.
The four POUR principles
All WCAG success criteria are organized under four high-level principles, collectively known as POUR. Every criterion under WCAG is assigned to one of these four:
- Perceivable: Information and UI components must be presentable in ways users can perceive. Nothing invisible to all senses. Examples: alt text for images, captions for video, sufficient color contrast.
- Operable: All functionality must be operable by a keyboard, not just a mouse. Nothing that traps keyboard focus. No time limits that cannot be extended.
- Understandable: Content and UI behavior must be understandable. Consistent navigation, clear error messages, readable language.
- Robust: Content must be robust enough for current and future assistive technologies to interpret it. Clean, valid, semantic HTML.
Conformance levels A, AA, AAA
Each WCAG success criterion is assigned a conformance level: A, AA, or AAA.
- Level A: The minimum. Failing these criteria makes content inaccessible to most assistive technology users. 30 criteria in WCAG 2.2.
- Level AA: The practical and legal standard. Builds on Level A. Addresses the most common real-world barriers. 20 additional criteria in WCAG 2.2.
- Level AAA: The highest level. Aspirational, not required by any law. Some criteria are impossible for all content types to meet simultaneously.
When any law, policy, or procurement requirement says “WCAG compliant,” it means Level A + Level AA together. You cannot skip Level A and only do AA.
WCAG versions explained
| Version | Released | Total Criteria (AA) | Status |
|---|---|---|---|
| WCAG 2.0 | 2008 | 38 | Still referenced by Section 508 and AODA |
| WCAG 2.1 | 2018 | 50 | Current legal minimum in most jurisdictions |
| WCAG 2.2 | 2023 | 56 | Current best practice; cited in new US court cases |
| WCAG 3.0 | TBD | TBD | In development; not yet legally referenced |
WCAG versions are backward compatible. Meeting WCAG 2.2 AA means you also meet 2.1 AA and 2.0 AA.
Which laws require WCAG
| Law | Jurisdiction | Required Standard |
|---|---|---|
| ADA Title II (DOJ Rule) | US — State & Local Gov | WCAG 2.1 Level AA |
| ADA Title III | US — Private Sector | WCAG 2.1/2.2 AA (court-set) |
| Section 508 | US — Federal | WCAG 2.0 Level AA |
| European Accessibility Act (EAA) | EU | EN 301 549 / WCAG 2.1 AA |
| AODA (Web Standard) | Ontario, Canada | WCAG 2.0 Level AA |
Common WCAG violations
These are the failures that appear on virtually every automated audit and drive most accessibility lawsuits:
- Missing or inadequate alt text on images
- Insufficient color contrast (below 4.5:1 for normal text)
- Interactive elements not reachable by keyboard
- Form inputs without associated labels
- Audio or video with autoplay and no pause control
- Videos without captions
- Links with non-descriptive text such as “click here” or “read more”
- No skip navigation link for keyboard users
- Missing page language declaration
How to become WCAG compliant
There is no shortcut, but there is a clear process:
- 1. Audit your site — Run an automated scan to surface the most obvious issues. Zylyn's free scan takes 90 seconds.
- 2. Prioritize Level A failures — Fix these first. They represent the highest user impact and greatest legal risk.
- 3. Address Level AA — Work through contrast, labels, keyboard traps, and timing issues.
- 4. Test with assistive technology — Screen readers (NVDA, JAWS, VoiceOver) will catch what automated tools miss.
- 5. Document your conformance — Maintain an accessibility statement and, for B2B contexts, a VPAT or ACR.
- 6. Establish a remediation cycle — Run audits on every major release and at least quarterly.
Wondering where your site actually stands?
Drop in a URL. Zylyn scans against WCAG 2.2 in 90 seconds, with issues grouped by severity.
How Zylyn gets you compliant.
Three tools, one platform. Use the audit to find what's broken, the widget for instant user-facing relief, and the reports to track real progress in code.
Free WCAG Audit
Scan any URL against WCAG 2.2 in 90 seconds. Issues are grouped by severity with code-ready fix suggestions and direct links to the relevant criterion.
Start a free scan- Most Popular
Accessibility Widget
User-first controls for text size, contrast, motion, font, and cursor. One-line install. Gives real users immediate relief while you fix the underlying code.
See the widget Audit Reports
Export findings to PDF or CSV. Schedule re-scans, track progress over time, and push remediation tasks into your existing workflow tools.
See a sample
Put WCAG knowledge into practice
These services help you meet WCAG 2.2 AA in your codebase.
- ServiceWeb Accessibility Testing
Full WCAG 2.2 AA evaluation — automated scan plus manual expert review with real assistive technology.
- ServiceAccessibility Audit
Prioritised findings report with every issue tagged by WCAG criterion, severity, and a code-ready fix.
- ServiceAccessibility Remediation
Code-level fixes for every WCAG failure — HTML, ARIA, contrast, keyboard, forms, and media.
Real teams, real results.
Companies use Zylyn to cut manual testing time, ship accessibly, and stay ahead of demand letters.
“We've reduced manual accessibility testing time by over 70%. Zylyn flags issues in real-time and suggests fixes. Our audit process is now faster and more reliable than anything we had before.”
Frequently asked questions
Common questions about WCAG conformance and what it means for your organization.
Meeting the Web Content Accessibility Guidelines, the global standard for digital accessibility, so people with disabilities can use your content.
No. WCAG is a technical standard. But most accessibility laws reference it, making it the de facto requirement.
Level AA. Nearly every accessibility law requires Level A and AA success criteria together.
WCAG 2.2 adds nine criteria for cognitive, low-vision, and mobile users and is backward compatible. Meeting 2.2 means you meet 2.1.
WCAG 2.1 Level AA is the current de facto standard in most laws, though Section 508 and AODA still reference 2.0.
Perceivable, Operable, Understandable, and Robust, known as POUR.
Yes. WCAG applies to mobile apps, documents, multimedia, and most digital content, not just websites.
No. Automated tools catch only a minority of issues. Manual and assistive-technology testing is essential.
Find out where your site stands — in 90 seconds.
One URL. One scan. A prioritized list of what to fix and how, sent straight to your inbox.
Keep reading
Recent guides from the Zylyn Knowledge Hub.

