RatedWithAI
Accessibility scanner
WCAG Compliance: The Complete Guide for 2026
The Web Content Accessibility Guidelines (WCAG) are the global standard for web accessibility — and the technical foundation of every major accessibility law. This guide covers everything you need to know: WCAG versions, conformance levels, the POUR principles, a comprehensive compliance checklist, common failures, testing methods, and how WCAG connects to ADA, Section 508, and the European Accessibility Act.
In This Guide
What is WCAG?
WCAG — the Web Content Accessibility Guidelines — is a set of technical standards that define how to make web content accessible to people with disabilities. Published by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI), WCAG is the globally recognized benchmark for web accessibility.
WCAG covers accessibility for people with a wide range of disabilities: visual (blindness, low vision, color blindness), auditory (deafness, hard of hearing), motor (limited fine motor control, paralysis), cognitive (learning disabilities, attention deficit, memory limitations), and neurological (epilepsy, vestibular disorders).
While WCAG is technically a "recommendation" from the W3C — not a law itself — it has been adopted by reference into virtually every major accessibility law worldwide. The U.S. ADA, Section 508, Canada's Accessible Canada Act, the EU's European Accessibility Act, and Australia's Disability Discrimination Act all reference WCAG as their technical standard. Meeting WCAG is how you comply with the law.
The guidelines are technology-agnostic — they apply to any web technology including HTML, CSS, JavaScript, PDF, and mobile applications. They're organized around four principles (Perceivable, Operable, Understandable, Robust) and three conformance levels (A, AA, AAA).
WCAG Versions: 2.0 → 2.1 → 2.2
WCAG has evolved through several versions, each building on the previous one. Understanding the differences matters because different laws reference different versions:
WCAG 2.0
The foundation. Introduced the four POUR principles and three conformance levels. Contains 61 success criteria (25 Level A, 13 Level AA, 23 Level AAA). This version is still referenced by Section 508 and some older legal frameworks.
WCAG 2.1 ← Current Legal Standard
Added 17 new success criteria (5 Level A, 7 Level AA, 5 Level AAA) addressing three major gaps: mobile accessibility, low vision, and cognitive/learning disabilities. Key additions include orientation (1.3.4), text spacing (1.4.12), reflow at 320px (1.4.10), and target size (2.5.5). All WCAG 2.0 criteria are included — 2.1 is a superset.
WCAG 2.2
The latest version. Added 9 new success criteria (including 6 Level A/AA) focused on cognitive accessibility, consistent navigation, and reducing barriers for users with cognitive and learning disabilities. Key additions: Focus Not Obscured (2.4.11), Dragging Movements (2.5.8), Consistent Help (3.2.6), and Redundant Entry (3.3.7). Removed criterion 4.1.1 Parsing (now obsolete due to modern browsers). All WCAG 2.1 criteria are included.
For a detailed comparison of what changed between versions, see our WCAG 2.1 vs 2.2: What Changed and What It Means and WCAG 2.2 Complete Guide.
WCAG Conformance Levels: A, AA, AAA
WCAG defines three levels of conformance, each building on the previous:
Level A — Minimum Accessibility
The bare minimum. Level A criteria address the most fundamental accessibility barriers — things like providing text alternatives for non-text content (1.1.1), ensuring keyboard access (2.1.1), and avoiding content that flashes more than three times per second (2.3.1). A website that only meets Level A is still largely inaccessible to many users. Level A alone is not sufficient for legal compliance.
Level AA — The Legal Standard ✓
The target for legal compliance worldwide. Level AA includes all Level A criteria plus additional requirements like color contrast minimums (1.4.3), text resize support (1.4.4), multiple navigation mechanisms (2.4.5), and consistent identification of components (3.2.4). This is the level referenced by the ADA, Section 508, the EAA, and virtually every other accessibility law. This is the level you should target.
Level AAA — Enhanced Accessibility
The highest level of accessibility. Includes stricter contrast ratios (7:1), sign language interpretation for audio, extended audio descriptions, and reading level requirements. The W3C itself notes that "it is not possible to satisfy all Level AAA success criteria for some content." Level AAA is aspirational — excellent for specific content or features, but not required or expected as a site-wide conformance target.
Explore individual WCAG criteria in our complete WCAG criteria reference, which includes plain-language explanations and testing guidance for each success criterion.
The Four Principles: POUR
Every WCAG success criterion falls under one of four foundational principles. Understanding POUR gives you a mental model for thinking about accessibility:
Perceivable
Users must be able to perceive the information being presented
Information and user interface components must be presentable to users in ways they can perceive — it can't be invisible to all of their senses. This principle ensures that people who are blind can access visual content through text alternatives, people who are deaf can access audio through captions, and people with low vision can read text through sufficient contrast.
Key Requirements:
Operable
Users must be able to operate the interface
User interface components and navigation must be operable — users can't be required to perform interactions they're physically incapable of. This principle ensures that keyboard-only users can navigate the entire site, that users have enough time to read content, and that content doesn't cause seizures.
Key Requirements:
Understandable
Users must be able to understand the content and interface
Information and the operation of user interface must be understandable — the content or operation can't be beyond the user's comprehension. This principle ensures that pages declare their language, that navigation is consistent, that forms provide clear instructions and error messages, and that content is readable.
Key Requirements:
Robust
Content must work with current and future technologies
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. This principle ensures that your HTML is valid, that custom components have proper ARIA roles and states, and that status messages are programmatically communicated to assistive technologies.
Key Requirements:
WCAG 2.1 Level AA: The Standard for Legal Compliance
If you're working toward legal compliance — whether under the ADA, Section 508, or the European Accessibility Act — your target is WCAG 2.1 Level AA. This means conforming to all 50 success criteria at Level A and Level AA (30 Level A + 20 Level AA).
WCAG 2.1 AA is specifically named in:
- ADA Title II Final Rule (28 CFR Part 35) — Published April 2024, effective April 2026/2027
- EN 301 549 v3.2.1 — The EU standard that references WCAG 2.1 AA, mandated by the European Accessibility Act
- ADA Title III case law — Federal courts consistently apply WCAG 2.1 AA in private-sector lawsuits
- State laws — Colorado, California, and others reference WCAG in their accessibility statutes
The 17 criteria added in WCAG 2.1 (beyond 2.0) are particularly important because they address mobile accessibility and low-vision accommodations that weren't covered in the original standard:
WCAG Compliance Checklist (Organized by POUR Principle)
This checklist covers the most important WCAG 2.1 AA requirements organized by principle. Use it as a systematic guide for auditing and remediating your website:
Perceivable (7 Items)
Every image conveying information has descriptive alt text. Decorative images use alt="".
All pre-recorded video with audio has synchronized captions. Pre-recorded audio has text transcripts.
Content uses semantic HTML (h1-h6 in order, ul/ol for lists, th for table headers). Structure is programmatically determined.
Normal text: 4.5:1 ratio. Large text (18pt or 14pt bold): 3:1 ratio. Verified for all states (hover, focus, active).
Text can be resized up to 200% without assistive technology, and without loss of content or functionality.
At 320px CSS width (400% zoom on 1280px screen), content reflows into single column without horizontal scrolling.
Interactive components (buttons, inputs, icons) and meaningful graphics have 3:1 contrast against adjacent colors.
Operable (6 Items)
Every interactive element is reachable and operable via keyboard (Tab, Enter, Space, arrows). No keyboard traps.
A "Skip to main content" link appears first on every page, allowing keyboard users to bypass repeated navigation.
Every page has a unique, descriptive <title> that identifies its topic and distinguishes it from other pages.
Link text describes the destination. No "click here" or "read more" without context. Links make sense out of context.
All interactive elements show a visible outline/highlight when focused via keyboard. Never use outline:none without an alternative.
More than one way to find pages: navigation menu, search, sitemap, breadcrumbs, or links between related pages.
Understandable (5 Items)
The <html> element has a valid lang attribute (e.g., lang="en"). Language changes within content are marked with lang attributes.
Navigation menus appear in the same relative order on every page. Users can predict where to find things.
Components that perform the same function are labeled the same way across the site (e.g., "Search" is always "Search").
When errors are detected, the error is identified in text and the specific field is described. Not communicated by color alone.
Forms provide labels, instructions, and input format hints. Required fields are clearly indicated. Help text is available.
Robust (2 Items)
All UI components (links, buttons, inputs, custom widgets) have accessible names, appropriate roles, and programmatically determinable states/values.
Success messages, error alerts, loading indicators, and other status updates are communicated to assistive technologies via ARIA live regions or roles.
Most Common WCAG Failures
WebAIM's annual analysis of the top one million websites consistently reveals the same accessibility failures year after year. In 2026, the average home page has 56.8 detectable WCAG errors, and 96.3% of home pages have at least one WCAG failure:
The encouraging reality: these top failures are all fixable. Most are caused by missing or incorrect HTML attributes — not fundamental architectural problems. A knowledgeable developer can address the majority of violations in days, not months.
For detailed fix guidance with code examples, see our Top 10 WCAG Failures and How to Avoid Them and How to Fix Common WCAG Failures.
How WCAG Relates to ADA, Section 508, and EAA
WCAG is the technical specification; the laws are the legal mandates. Here's how they connect:
* Section 508 formally references WCAG 2.0 AA via the ICT Standards refresh, but is expected to update to 2.1 in the next revision.
The practical takeaway: if you achieve WCAG 2.1 Level AA compliance, you're effectively compliant with every major accessibility law globally. It's the universal standard. For deep dives into specific laws, see our guides on ADA Website Compliance, Section 508 Compliance, and European Accessibility Act.
Testing Tools and Methods
Effective WCAG compliance testing uses a layered approach. No single tool or method catches every violation.
Layer 1: Automated Scanning (Start Here)
Automated scanners test your pages against WCAG criteria that can be objectively verified by machine: color contrast ratios, presence of alt text, form label associations, heading structure, language declarations, and ARIA usage. They typically catch 30-40% of all WCAG violations — and they're fast enough to scan hundreds of pages in minutes.
RatedWithAI's free accessibility checker scans any URL against WCAG 2.1 AA and provides violation details with prioritized fix recommendations. Other popular automated tools include axe, WAVE, Lighthouse, and Pa11y.
Layer 2: Manual Testing
Manual testing catches the subjective criteria that automated tools can't evaluate — whether alt text is actually meaningful, whether tab order is logical, whether error messages make sense:
- Keyboard testing — Unplug your mouse. Tab through every page. Can you reach and operate every interactive element? Is the focus order logical? Does focus ever get trapped?
- Screen reader testing — Use VoiceOver (Mac, free), NVDA (Windows, free), or JAWS (Windows, paid). Listen to your pages. Does the content make sense when read aloud? Are headings, links, and form fields announced correctly?
- Zoom/reflow testing — Zoom to 200% and 400% in your browser. Does content reflow? Is anything cut off, overlapping, or lost?
- Content review — Check that link text is descriptive, heading hierarchy is logical, form instructions are clear, and error messages identify specific problems.
Layer 3: User Testing
Testing with real users who have disabilities is the gold standard. People who use assistive technology daily will find issues that no tool or testing protocol can uncover. If your budget allows, recruit 3-5 testers with different disabilities (blind, low vision, motor impairment, cognitive disability) to complete your most critical user workflows.
For a comprehensive testing methodology, see our Website Accessibility Testing Guide and Best Accessibility Checker Tools for 2026.
Check Your WCAG Compliance — Free
Run a free WCAG 2.1 AA compliance scan on any page. Get a detailed report with violation counts, severity ratings, and prioritized fix recommendations — in under 60 seconds.
WCAG Compliance for Different Industries
While WCAG requirements are the same regardless of industry, different sectors face unique challenges and different levels of legal exposure:
E-Commerce
Key challenges: Product images, complex filters, checkout flows, dynamic content updates
Healthcare
Key challenges: Patient portals, appointment scheduling, medical forms, HIPAA intersection
Education
Key challenges: LMS platforms, course content, student portals, PDF documents, multimedia
Banking & Finance
Key challenges: Account dashboards, transaction flows, financial documents, calculator tools
Government
Key challenges: Public services, forms, PDF documents, emergency alerts, ADA Title II deadlines
SaaS
Key challenges: Complex UI components, dashboards, data visualization, VPAT requirements
For industry-specific guidance, explore our ADA Compliance by Industry breakdown and individual industry pages.
VPAT Documentation
A VPAT (Voluntary Product Accessibility Template) is a standardized document that describes how your product conforms to accessibility standards — typically WCAG 2.1 AA and Section 508. VPATs are the universal "accessibility resume" for software products.
You need a VPAT if you:
- Sell to government agencies — Federal, state, and local government procurement increasingly requires VPAT documentation
- Pursue enterprise contracts — Large organizations routinely ask for VPATs during vendor evaluation
- Sell to educational institutions — Universities and school districts require VPATs for all software purchases
- Want to demonstrate compliance proactively — A VPAT shows you've evaluated your product against accessibility standards
The VPAT format is maintained by the Information Technology Industry Council (ITI). There are three editions: WCAG (international), Revised Section 508 (US federal), and EN 301 549 (EU). Most organizations use the "INT" (International) edition that covers all three standards.
Get started with our free VPAT template and guide.
Frequently Asked Questions: WCAG Compliance
What does WCAG stand for?
WCAG stands for Web Content Accessibility Guidelines. It's a set of technical standards published by the World Wide Web Consortium (W3C) through the Web Accessibility Initiative (WAI). WCAG defines how to make web content accessible to people with disabilities — visual, auditory, motor, cognitive, and neurological.
What level of WCAG compliance is legally required?
WCAG 2.1 Level AA is the standard referenced by most laws globally. The DOJ's ADA Title II rule explicitly requires WCAG 2.1 AA. The European Accessibility Act references EN 301 549, which maps to WCAG 2.1 AA. Level A alone is insufficient; Level AAA is aspirational but not legally required.
What's the difference between WCAG 2.0, 2.1, and 2.2?
WCAG 2.0 (2008) has 61 criteria. WCAG 2.1 (2018) added 17 criteria for mobile, low vision, and cognitive accessibility. WCAG 2.2 (2023) added 9 more criteria for cognitive accessibility and consistent help. Each version includes all criteria from previous versions.
How do I check my website for WCAG compliance?
Use a three-layer approach: 1) Automated scanning with tools like RatedWithAI to catch objective violations. 2) Manual testing including keyboard navigation and screen reader testing. 3) User testing with people who have disabilities. Automated tools catch 30-40% of violations; the rest require human evaluation.
What are the four principles of WCAG?
POUR: Perceivable (content can be perceived through sight, hearing, or touch), Operable (interface can be navigated and used), Understandable (content and interface make sense), and Robust (content works with assistive technologies).
Is WCAG compliance the same as ADA compliance?
They're closely related. ADA is the law prohibiting disability discrimination. WCAG is the technical standard for web accessibility. Meeting WCAG 2.1 Level AA is how you demonstrate ADA compliance for your website. ADA is the legal requirement; WCAG is the technical specification that satisfies it.
How much does WCAG compliance cost?
Initial remediation: $2,000-$10,000 for small sites, up to $200,000+ for enterprise. Ongoing monitoring: $29-$999/month. Small businesses can claim the Disabled Access Credit (IRS Form 8826) — up to $5,000/year. Proactive compliance is always cheaper than lawsuit settlements ($75,000+ average).
Can automated tools fully test WCAG compliance?
No. Automated tools test about 30-40% of criteria — objective, machine-verifiable items like contrast ratios and alt text presence. The remaining 60-70% requires human judgment: Is the alt text meaningful? Is navigation logical? Is content understandable? Automated testing is essential but not sufficient alone.
What is a VPAT and do I need one?
A VPAT (Voluntary Product Accessibility Template) describes how your product conforms to accessibility standards. You need one if you sell to government agencies, pursue enterprise contracts, or sell to educational institutions. VPATs are increasingly required in procurement across public and private sectors.
Should I target WCAG 2.1 or 2.2?
Target WCAG 2.1 Level AA as your baseline — it's what laws currently require. If resources allow, work toward WCAG 2.2 AA for best practice and future-proofing. WCAG 2.2 adds criteria around focus appearance, dragging movements, and consistent help that improve UX for everyone.
Start Your WCAG Compliance Journey Today
Run a free WCAG 2.1 AA compliance scan on your website. Get violation details, severity ratings, and step-by-step fix recommendations — in under 60 seconds.