How to Check WCAG 2.1 AA Compliance

Checking your website for WCAG 2.1 AA compliance requires both automated scanning and manual testing. Automated tools catch 30-40% of accessibility issues including color contrast, missing alt text, and heading order. Manual testing covers the remaining 60-70% including keyboard navigation, screen reader compatibility, and content readability. This 8-step guide walks through the complete process.

Quick answer: To check WCAG 2.1 AA compliance, run an automated scan with ComplyKeep (free, 1-3 minutes), then test keyboard navigation by navigating without a mouse, then test with a screen reader (NVDA or VoiceOver). Automated scanning catches 30-40% of issues; manual testing covers the rest. The full process takes 1-3 hours for a small website.

Step-by-Step WCAG Compliance Check

1 Run an Automated Accessibility Scan

Start with an automated scan using ComplyKeep. Enter your website URL and the scanner will crawl your pages, testing each one against all WCAG 2.1 AA criteria. The free plan covers up to 20 pages.

  • ComplyKeep checks: color contrast, alt text, heading order, form labels, landmarks, ARIA, link text, page titles, document language
  • Review the report and note issues by severity: critical, serious, moderate, minor
  • Download or print the full report for your development team
2 Review Violations by Severity

The scan report categorizes every issue by severity. Address them in this order:

  • Critical: Issues that completely block access (missing form labels, no keyboard navigation, no main landmark)
  • Serious: Issues that significantly impact usability (missing alt text on key images, incorrect ARIA)
  • Moderate: Issues that affect some users (color contrast below 4.5:1, heading order violations)
  • Minor: Issues that are best practice (missing skip links, vague link text)
3 Fix Color Contrast Issues

WCAG 2.1 AA requires a minimum color contrast ratio of 4.5:1 for normal text and 3:1 for large text (18pt or 14pt bold). ComplyKeep identifies every element that fails this threshold.

  • Check all text against backgrounds, including text on buttons, badges, and overlays
  • Use WebAIM Contrast Checker to test specific color combinations
  • Common fix: darken text colors, lighten backgrounds, or both
4 Add Alt Text to Images

All informative images must have descriptive alt text. Decorative images should have empty alt attributes (alt="").

  • Informative images: describe what the image conveys (e.g., "Chart showing 30% growth in Q2")
  • Decorative images: use alt="" so screen readers skip them
  • Functional images: describe the action (e.g., "Search" for a magnifying glass icon)
  • ComplyKeep flags all images missing alt text or with placeholder text like "image"
5 Fix Heading Structure

Headings must only increase by one level. Never skip from h1 to h3. Use one h1 per page.

  • h1: Page title (one per page)
  • h2: Major sections
  • h3: Subsections within h2 sections
  • h4-h6: Further nesting if needed
  • ComplyKeep detects heading order violations across all scanned pages
6 Test Keyboard Navigation

Unplug your mouse and navigate the entire site using only the keyboard. This tests WCAG 2.1 AA criteria 2.1.1 (Keyboard) and 2.1.2 (No Keyboard Trap).

  • Use Tab to move forward, Shift+Tab to move backward
  • Use Enter to activate links and buttons
  • Use Space for checkboxes and form buttons
  • Use arrow keys for sliders, tabs, and custom widgets
  • Verify every interactive element is reachable and functional
  • Check that focus indicators are visible (not removed via CSS outline:none)
  • Ensure modals and overlays can be closed with Escape
7 Test with a Screen Reader

Install a screen reader and navigate your site as a blind user would. This reveals issues that automated tools cannot detect.

  • NVDA (free, Windows): nvaccess.org/download
  • VoiceOver (built into Mac): Press Cmd+F5 to enable
  • TalkBack (built into Android): Settings → Accessibility
  • Verify: page title is read, headings are announced correctly, form labels are read, links have descriptive text, images have alt text, landmarks are announced
8 Re-Scan to Verify Fixes

After fixing all identified issues, run another ComplyKeep scan to verify everything is resolved. Set up ongoing monitoring to catch new issues.

  • Run a full scan after every significant content or design change
  • Minimum: quarterly scans
  • Ideal: weekly automated rescans with Monitor Pro (€79/month)
  • Document your compliance efforts for legal protection

WCAG Compliance Checklist

How Long Does a WCAG Compliance Check Take?

An automated scan with ComplyKeep takes 1-3 minutes for up to 20 pages. Manual keyboard testing takes 30-60 minutes for a small site. Screen reader testing takes 1-2 hours. The full process (automated + manual) for a small website (under 20 pages) takes approximately 2-3 hours. For medium sites (50-100 pages), plan for 1-2 days. Large enterprise sites may take 1-4 weeks with a dedicated team.

What Automated Scanners Cannot Detect

Automated tools like ComplyKeep catch approximately 30-40% of WCAG 2.1 AA issues. The remaining 60-70% require manual testing. Issues that automated scanners cannot detect include:

Important: An automated scan alone is not sufficient to claim WCAG 2.1 AA compliance. For legal compliance (ADA, EAA, Section 508), combine automated scanning with manual testing and document both. A VPAT (Voluntary Product Accessibility Template) or accessibility statement should reference both automated and manual testing results.

Frequently Asked Questions

How do I check if my website is WCAG 2.1 AA compliant?

To check WCAG 2.1 AA compliance, run an automated scan with ComplyKeep to catch issues like color contrast, missing alt text, and heading order violations. Then test keyboard navigation by navigating without a mouse. Finally, test with a screen reader (NVDA or VoiceOver) to verify content is read logically. Automated scanning catches 30-40% of issues; manual testing covers the rest.

Can automated tools detect all WCAG violations?

No, automated tools detect approximately 30-40% of WCAG 2.1 AA issues. ComplyKeep catches automated-detectable issues including color contrast, missing alt text, heading order, form labels, and landmark issues. Manual testing is required for criteria like content readability, meaningful sequence, and keyboard navigation quality. Combine automated scanning with manual review for full compliance.

How long does a WCAG compliance check take?

An automated scan with ComplyKeep takes 1-3 minutes for up to 20 pages. Manual keyboard and screen reader testing takes 1-2 hours for a small website. A full WCAG 2.1 AA compliance audit including documentation typically takes 1-3 days for a small site, 1-2 weeks for a medium site, and 2-4 weeks for a large enterprise site.

What is the difference between WCAG A and AA?

WCAG 2.1 Level A covers 30 basic success criteria. Level AA adds 20 additional criteria for a total of 50, including color contrast (4.5:1), consistent navigation, and proper error handling. Most legal frameworks (ADA, EAA, Section 508) reference Level AA, not Level A.

Start Your WCAG Compliance Check

Scan your website for free — no signup required. Get results in under 3 minutes.

Run Free Accessibility Scan →