Blog Post
WCAG Compliance Checker: What Automated Tools Miss (And How to Actually Get Compliant)
A WCAG compliance checker evaluates web pages against the Web Content Accessibility Guidelines. Automated checkers catch 30-40% of WCAG issues. Full compliance requires layering automated scanning with design QA review and manual assistive technology testing. This guide covers how checkers work, what they miss, and how to build a compliance workflow.
What Is a WCAG Compliance Checker?
A WCAG compliance checker is software that evaluates web pages against the Web Content Accessibility Guidelines. These guidelines define success criteria across four principles: Perceivable, Operable, Understandable, and Robust. Most regulations reference WCAG 2.1 Level AA as the standard. WCAG 2.2, published October 2023, adds nine new criteria and is fully backward-compatible.
The 30-40% Detection Ceiling
The UK Government Digital Service found that automated scanners catch only 30-40% of known WCAG issues. Automated tools reliably catch missing alt text, insufficient contrast ratios, empty buttons and links, missing form labels, and missing document language. They miss contrast in context, focus indicator quality, touch target sizing, meaningful reading order, keyboard traps, ARIA pattern completeness, and content on hover or focus.
Best WCAG Compliance Checkers Compared (2026)
Tools compared: axe DevTools (Deque), WAVE (WebAIM), Google Lighthouse, Pa11y, Siteimprove, Microsoft Accessibility Insights, and OverlayQA across automated scanning, design QA, and AI visual analysis layers.
What WCAG 2.2 Changed
WCAG 2.2 added nine new success criteria: Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size Minimum (2.5.8), Consistent Help (3.2.6), Redundant Entry (3.3.7), and Accessible Authentication (3.3.8). Most new criteria require human judgment and cannot be fully automated.
The Six Most Common WCAG Violations
The 2026 WebAIM Million found six violations account for 96% of detected errors: low contrast text (83.9%), missing alt text (53.1%), missing form labels (51.0%), empty links (46.3%), empty buttons (30.6%), and missing document language (13.5%). 95.9% of the top million websites had detectable failures.
Beyond Automated Checking: Three Layers of Compliance
Layer 1: Automated Scanning
Run axe-core, WAVE, or Lighthouse on every page. Integrate into CI/CD. Catches structural violations at scale.
Layer 2: Design QA and Visual Accessibility Review
Catches visual accessibility issues automated tools miss: contrast against complex backgrounds, focus indicator visibility, touch target sizing, and whether accessible design survived implementation. OverlayQA fills this layer by combining axe-core scanning, keyboard testing, and AI visual analysis in a single audit.
Layer 3: Manual Testing with Assistive Technology
Screen reader testing, keyboard-only navigation, and screen magnification validate that the experience works for people with disabilities.
The Cost of Skipping WCAG Compliance
3,117 federal web accessibility lawsuits filed in 2025, up 27% from 2024. Average settlements: demand letters $5K, out-of-court $30K, court judgments $85K, class actions $400K. 22.6% of lawsuits targeted sites using overlay widgets. The FTC fined accessiBe $1M for false compliance claims.
How to Build a WCAG Compliance Workflow
Every build: automated scan in CI/CD. Every sprint: design QA review. Every release: assistive technology testing. Quarterly: comprehensive WCAG 2.2 AA audit with conformance documentation.
Frequently Asked Questions
What is the best free WCAG compliance checker?
axe DevTools (browser extension) is the most comprehensive free automated checker. WAVE is a strong alternative for non-technical team members.
Can a WCAG compliance checker guarantee compliance?
No. Automated checkers catch 30-40% of issues. Full compliance requires human evaluation of visual presentation, interaction quality, and assistive technology compatibility.
What is the difference between WCAG 2.1 and 2.2?
WCAG 2.2 adds nine new success criteria covering focus visibility, target sizing, dragging alternatives, and cognitive accessibility. It is fully backward-compatible with 2.1.
How often should I run WCAG compliance checks?
Automated scans on every build. Design QA review every sprint. Assistive technology testing every release. Comprehensive audit quarterly.
Do overlay widgets count as WCAG compliance?
No. Overlays modify presentation without fixing underlying markup. 22.6% of 2025 lawsuits targeted sites using overlays.