Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

WCAG Crawler review

Free#83 of 129 in Website Accessibility ToolsAccessibility Testing Software

A focused self-hosted crawler for whole-site WCAG 2.0 and 2.1 CI scans.

3.0/10Editor score
WCAG Crawler3.0 Visit WCAG Crawler

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

WCAG Crawler is an open-source accessibility scanner for developers, web agencies, government organizations, and enterprise teams that need whole-site coverage. It crawls pages within a domain and checks programmatically detectable issues against WCAG 2.0 and 2.1 criteria using axe-core. The product is designed for teams that prefer self-hosted tooling and want accessibility checks inside development workflows rather than a browser-only review process.

Its strongest capability is the combination of site-wide crawling and issue organization. Shared-component issue deduplication can group repeated findings from common elements, while duplicate-page detection helps distinguish genuinely different pages from repeated content. Real-time scan progress, severity filtering, and before-and-after code-fix suggestions give teams a clearer path from discovery to remediation. The GitHub Action supports CI/CD accessibility testing, and the REST API covers scan and report operations. Docker-based self-hosting rounds out the deployment options for teams managing their own environment.

WCAG Crawler fits buyers who want an open-source, developer-oriented scanner with focused whole-site coverage and CI support. It is less suitable for teams seeking a broad accessibility platform with scheduling, browser-extension workflows, or a wider integration ecosystem. Its automated findings target programmatically detectable criteria, so teams still need manual accessibility evaluation alongside scans. Choose it when self-hosting, GitHub-based workflows, and WCAG 2.0/2.1 crawling matter most; consider an alternative when verified WCAG 2.2 coverage or broader product integrations is a priority.

WCAG Crawler pros and cons

  • Where it wins
    • Crawls full domains and tests WCAG 2.0 and 2.1 criteria
    • Deduplicates shared-component issues and detects duplicate pages
    • Supports GitHub Actions, REST API access, and Docker self-hosting
  • Where it doesn't
    • Automated scans do not replace manual accessibility evaluation
    • No verified WCAG 2.2 testing is provided
    • Broader integrations, scheduling, and browser-extension support are absent

WCAG Crawler fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update