WCAG 2.1 Requirements Checklist
WCAG 2.1 AA includes 50 success criteria across four principles. Use this checklist to understand each requirement and automate the ones machines can test.
No signup required. Results in under 60 seconds.
WCAG 2.1 AA: The Complete Requirements Overview
The Web Content Accessibility Guidelines (WCAG) 2.1 at the AA conformance level comprise 50 success criteria organized under four principles — Perceivable, Operable, Understandable, and Robust. Each criterion describes a specific requirement that web content must meet to be accessible. Understanding the full scope of requirements is essential for planning remediation, because many organizations underestimate the breadth of WCAG. Here is a summary by principle:
- Perceivable (28 criteria at A+AA): Content must be presentable to all users. This covers text alternatives, time-based media, adaptable content, and distinguishable elements (contrast, resize, spacing, reflow)
- Operable (15 criteria at A+AA): Interface must be navigable. This covers keyboard access, enough time, seizure prevention, navigability, and input modalities
- Understandable (5 criteria at A+AA): Content and UI must be understandable. This covers readable text, predictable behavior, and input assistance
- Robust (2 criteria at A+AA): Content must work with assistive technologies. This covers parsing and name/role/value for UI components
Key WCAG 2.1 AA Requirements by Category
While all 50 criteria matter, some are more frequently violated and more impactful than others. Here are the requirements most often flagged in audits:
- 1.1.1 Non-text Content (A): All images, icons, and media need text alternatives. The most common violation is
<img>tags withoutaltattributes - 1.4.3 Contrast Minimum (AA): Normal text needs 4.5:1 contrast; large text needs 3:1. Found on 81% of homepages
- 1.4.10 Reflow (AA): Content must reflow at 320px width without horizontal scrolling — critical for mobile
- 2.1.1 Keyboard (A): All functionality available via keyboard. Custom dropdowns, modals, and tabs frequently fail this
- 2.4.7 Focus Visible (AA): Keyboard focus must have a visible indicator. CSS
outline: nonewithout replacement breaks this - 3.3.2 Labels or Instructions (A): Form inputs need programmatically associated labels, not just placeholder text
- 4.1.2 Name, Role, Value (A): Custom UI components must expose their name, role, and state to assistive technology via ARIA
Which Requirements Can Be Tested Automatically?
Of the 50 WCAG 2.1 AA success criteria, automated tools can fully test approximately 15-20 and partially test another 10-15. Here is how they break down:
- Fully automatable: Contrast ratios (1.4.3), missing alt attributes (1.1.1), missing form labels (3.3.2), duplicate IDs (4.1.1), language of page (3.1.1), ARIA validity (4.1.2 partially), heading hierarchy (1.3.1 partially), link purpose from text (2.4.4 partially)
- Partially automatable: The tool can flag potential issues but a human must verify. For example, alt text presence is automatable but alt text quality is not. Tab order can be flagged but logical correctness requires human judgment
- Manual only: Meaningful sequence (1.3.2), captions for live audio (1.2.4), audio description (1.2.5), error suggestion quality (3.3.3), consistent navigation across pages (3.2.3)
CompliScan automates everything in the first two categories, giving you a head start on the most common and most impactful violations before you invest in manual review.
Using CompliScan to Check Your WCAG Requirements
Instead of working through a 50-item checklist manually, let CompliScan automate the machine-testable requirements. Here is how to use the two together:
- Run a free scan on your most important page (usually your homepage or main conversion page). CompliScan tests against all automatable WCAG 2.1 AA criteria and returns a prioritized violation list
- Review results by WCAG criterion: Each violation is mapped to its specific success criterion number (e.g., 1.4.3, 2.1.1). Cross-reference with this checklist to understand the requirement
- Apply AI fix suggestions: CompliScan generates specific code changes for each violation — copy, adapt, and deploy
- Manual review: Use this checklist to test the criteria that automated tools cannot cover. Focus on keyboard navigation flow, screen reader experience, and content clarity
Paid plans add continuous monitoring: Shield ($49/mo) for weekly scans of 3 sites, Shield Pro ($149/mo) for daily scans with PDF reports, and Agency ($299/mo) for 50-site coverage.
Frequently Asked Questions
How many WCAG 2.1 AA success criteria are there?
WCAG 2.1 at the AA conformance level includes 50 success criteria total: 30 at Level A (the minimum) and 20 additional at Level AA. To conform at Level AA, you must meet all 50 criteria. WCAG 2.1 added 17 new criteria beyond WCAG 2.0's 38 (at A+AA), primarily addressing mobile accessibility, low vision, and cognitive disabilities.
Is there an official WCAG 2.1 AA checklist from W3C?
W3C publishes a 'How to Meet WCAG' quick reference (w3.org/WAI/WCAG21/quickref) that can be filtered by level and technology. It is the authoritative source. This page summarizes the requirements in a more actionable format and pairs them with automated testing via CompliScan. For the definitive specification, always refer to the W3C source.
What is the difference between WCAG 2.0 and 2.1 requirements?
WCAG 2.1 includes everything in WCAG 2.0 plus 17 new success criteria. The additions address gaps in mobile accessibility (orientation, touch target size), low vision support (reflow, text spacing, content on hover), and cognitive accessibility (timeouts, animation control). If you meet WCAG 2.1 AA, you automatically meet WCAG 2.0 AA as well.
Do I need to meet every single criterion for compliance?
WCAG conformance requires meeting all criteria at your target level for all pages in scope. However, in practice, courts and regulators look at good-faith effort and substantial compliance. Having a documented testing process, actively remediating issues, and monitoring for regressions demonstrates due diligence even if you have not achieved 100% conformance.
How do I prioritize which requirements to fix first?
Start with critical and serious violations that affect the most users and pages: color contrast (affects readability for everyone), keyboard access (blocks users who cannot use a mouse), form labels (blocks form completion), and alt text (blocks screen reader users from understanding images). CompliScan's severity ratings help you prioritize — fix critical issues first, then serious, then moderate.
More Free Tools
Check Your Website Now
Enter your URL below and get a free accessibility report with AI-powered fix suggestions in under 60 seconds.
No signup required. Results in under 60 seconds.