WCAG 2.1 AA & 2.2 Compliance Checklist (2026)

WCAG 2.1 AA & 2.2 Compliance Checklist (2026)

A WCAG checklist turns complex accessibility guidelines into clear, actionable steps. This guide gives you a complete, testable checklist covering WCAG 2.1 AA - the global baseline for accessible web design - and the additions introduced in WCAG 2.2, all organized around the four POUR principles. Use it to assess a site, brief developers, or build accessibility into your workflow. For the conceptual deep-dive on the new 2.2 criteria, see our complete WCAG 2.2 guide.

TL;DR: Work through the POUR checklist below to meet WCAG Level AA. WCAG 2.1 AA is the foundation; WCAG 2.2 adds nine criteria on top (focus visibility, target size, dragging alternatives, accessible authentication). A checklist is for ongoing self-assessment - pair it with a professional accessibility audit for full validation.

Understanding WCAG 2.1 AA and Why It Matters

The Web Content Accessibility Guidelines (WCAG) are developed by the World Wide Web Consortium (W3C) as part of its Web Accessibility Initiative (WAI). The goal is to make web content more accessible to individuals with disabilities, including those with visual, auditory, cognitive, and physical impairments.

WCAG 2.1 AA is the standard most accessibility laws reference worldwide. Meeting it makes your site usable for people with disabilities, improves UX and SEO, strengthens your brand, and reduces legal risk. Because WCAG 2.2 is backward-compatible, the 2.1 AA checklist remains your foundation - WCAG 2.2 simply layers additional criteria on top.

Why WCAG 2.1 AA Compliance Is Essential

Legal Protection

Many countries, including the U.S., UK, and EU members, have adopted WCAG as part of their accessibility legislation. Non-compliance may lead to lawsuits, fines, or reputational damage.

Inclusive User Experience

By meeting WCAG 2.1 AA standards, websites become accessible to millions of users who rely on assistive technologies such as screen readers or keyboard navigation.

SEO and Performance Benefits

Accessibility overlaps with SEO best practices, improved structure, clear alt text, and faster load times can enhance your visibility on search engines.

Brand Reputation

Demonstrating a commitment to inclusion strengthens brand credibility and loyalty among users and partners.

WCAG Checklist: Key Principles and Success Criteria

WCAG is structured around four principles - Perceivable, Operable, Understandable, Robust (POUR) - each with testable criteria.

1. Perceivable

Information must be presented in a way that users can perceive.

• Text alternatives: provide alt text for images and non-text content.
• Time-based media: offer captions and audio descriptions for video.
• Adaptable content: use semantic HTML so assistive technologies can interpret content.
• Contrast ratio: maintain at least 4.5:1 contrast between text and background (check pairs with the WCAG contrast checker).
• Resize text: content must stay readable and functional when text is resized up to 200%.

2. Operable

Users must be able to interact with all elements easily.

Checklist highlights include:

• Keyboard accessibility: all interactive components must work via keyboard, with helpful skip links.
• Enough time: give users control over time limits.
• No flashing content: avoid anything that flashes more than three times per second.
• Consistent navigation: menus and navigation should appear consistently across pages.
• Target size (WCAG 2.2): interactive targets should be at least 24x24 CSS pixels or adequately spaced.

3. Understandable

Users should be able to comprehend both the content and interface.

Key success criteria from the WCAG checklist:

• Clear labels and instructions on all form fields.
• Error identification and help that explains what went wrong and how to fix it.
• Predictable interactions - no unexpected context changes.
• Consistent help (WCAG 2.2): place help mechanisms in the same relative location across pages.

4. Robust

Content must be compatible with current and future user agents, including assistive technologies.

Checklist items:

• Valid, semantic markup and correct ARIA so content works with current and future assistive technologies.
• Accessible authentication (WCAG 2.2): don't rely on cognitive-function tests for login without an accessible alternative.

How to Use This Checklist

Using a WCAG checklist during web design and development ensures accessibility is built into the process rather than treated as an afterthought.

1. Run each page through the POUR items above, noting pass/fail and WCAG level.
2. Fix Level A blockers first, then close Level AA gaps.
3. Validate judgment-based items manually with a keyboard and screen reader, and baseline with the WCAG checker and broader testing tools.
4. Re-test after every redesign or feature launch.

Below are actionable steps for implementing WCAG 2.1 standards effectively.

Step 1: Conduct an Accessibility Audit

Use automated and manual testing to identify issues. Tools like Axe, WAVE, and Lighthouse can perform initial scans, but human review ensures full compliance.

Step 2: Prioritize Issues

Fix high-impact accessibility barriers first, such as missing alt text, keyboard traps, or low contrast. These issues most directly affect usability.

Step 3: Apply Semantic HTML

Structure content logically with proper use of headings, lists, and landmarks. Semantic coding is fundamental to passing a WCAG AA checklist evaluation.

Step 4: Improve Navigation

Enable intuitive navigation using breadcrumbs, descriptive links, and visible focus states. This supports both keyboard and screen reader users.

Step 5: Enhance Multimedia Accessibility

Add closed captions for video, transcripts for audio, and clear descriptions for visual media.

Step 6: Validate Compliance

Use multiple testing methods, automated tools, keyboard-only navigation, and screen readers like NVDA or JAWS.

Accessibility isn't just a one-time effort; it's a continuous process requiring regular monitoring and updates.

The Relationship Between WCAG 2.1 AA and Usability

While accessibility focuses on removing barriers for users with disabilities, usability ensures a pleasant and efficient experience for everyone.

Achieving WCAG 2.1 AA compliance often improves overall usability, benefiting all visitors, not just those with impairments.

For instance:

• Clear typography enhances readability for everyone.
• Simplified navigation aids both users with cognitive challenges and mobile users.
• Proper color contrast improves visibility in bright environments.

Thus, accessibility and usability go hand in hand in delivering a superior digital experience.

Practical Benefits of Following a WCAG 2.1 AA Checklist

Organizations that adhere to WCAG 2.1 AA gain tangible advantages:

• Broader Audience Reach – Accessible websites engage users across demographics and abilities.
• Improved SEO Ranking – Search engines reward semantic, structured content.
• Reduced Legal Risks – Compliance mitigates potential lawsuits.
• Increased Conversions – A frictionless, user-friendly interface drives engagement.
• Corporate Social Responsibility – Promotes inclusivity and ethical digital practices.

Common Mistakes When Using Accessibility Checklists

• Treating a checklist as a one-time task instead of an ongoing practice.
• Relying only on automated checks and skipping manual testing.
• Checking the homepage but not templates, forms, and dynamic components.
• Ignoring the new WCAG 2.2 criteria (focus visibility, target size, authentication).

Accessibility is about consistency, not one-time compliance but ongoing optimization.

WCAG Checklist vs. Accessibility Audit

A checklist is a self-assessment tool; an audit is a professional evaluation. Use a checklist for ongoing compliance and development workflows. Use an accessibility audit when you need detailed issue reports, full WCAG mapping, and expert recommendations. The two are complementary: the checklist keeps you on track day to day; the audit validates thoroughly.

How to Maintain Compliance Over Time

Accessibility drifts as sites change. Move from checklist-based, point-in-time compliance to continuous improvement: automate scanning to catch regressions, train your team, and use an accessibility widget with ongoing monitoring to scale accessibility across many pages.

Frequently Asked Questions

What is a WCAG compliance checklist?

A structured list of accessibility requirements derived from WCAG that turns complex guidelines into actionable steps, helping you identify gaps and meet Level AA.

What is the difference between a WCAG checklist and an accessibility audit?

A checklist is a self-assessment tool for ongoing compliance and development; an audit is a professional evaluation providing detailed reports, WCAG mapping, and expert recommendations.

What is the difference between WCAG 2.1 AA and WCAG 2.2?

WCAG 2.2 includes everything in 2.1 and adds nine new criteria (focus visibility, target size, dragging, accessible authentication) while removing 4.1.1 Parsing. Meeting 2.2 means you also meet 2.1.

What WCAG level should my website target?

Level AA - it's the practical target for most sites and the level most laws require. Level A is the minimum; Level AAA is for specialized content.

How do I maintain WCAG compliance over time?

Re-check after adding content or features, automate scanning to catch regressions, train your team, and move from one-time checklists to continuous monitoring.

Conclusion

A good WCAG checklist makes accessibility manageable: work through the POUR criteria, target Level AA, add the WCAG 2.2 items, and validate with a real audit. Treat it as an ongoing practice rather than a one-time exercise, and your site stays accessible, compliant, and welcoming to every user. For the full breakdown of the new 2.2 criteria, read our WCAG 2.2 guide.