Free WCAG accessibility scanner using Playwright and axe-core.
Paste a public http/https page we can reach and get machine-checkable accessibility issues grouped by WCAG rule, affected elements, and axe/Deque guidance, usually in about 30 seconds.
Scan one public http/https page we can reach. No crawl, no signup, no certification claim.
How it works
Scan
Paste a public http/https page we can reach. We load it in a real browser and run axe-core, the engine behind most accessibility tooling.
Prioritized issues
Violations grouped by rule and ranked critical to minor, each mapped to its WCAG success criterion.
Triage with guidance
Every issue shows the affected elements, axe failure notes and a link to the full Deque rule docs.
Monitoring - testing demand
The paid monitoring product is not live yet. Planned directions include weekly re-scans, deploy regression alerts, and lightweight CI checks.
Frequently asked questions
What does AxeGuard check?
We load your page in a headless browser at desktop size and run the open-source axe-core rule engine, the same checks behind browser accessibility devtools. Issues are reported against WCAG success criteria with severity ratings, axe failure notes and Deque rule docs.
Will it catch every accessibility issue?
No. Be wary of any tool that claims otherwise. Automated checks reliably detect a subset of WCAG issues (commonly cited as roughly a third to a half). Things like meaningful alt text, logical focus order and caption quality need human review. AxeGuard finds the verifiable issues fast so your manual effort goes where it matters.
Is this legal advice, or proof my site meets a standard?
No. Results are informational findings from automated checks, not legal advice, and not a guarantee or certification of conformance with WCAG, the ADA, or any other standard or law.
What's coming next?
I am testing demand for paid monitoring before building it. The likely first version is weekly re-scans and email alerts for new automated issues. CI checks and client summaries are still product hypotheses, not live features.
What data does a scan use?
AxeGuard stores the submitted URL, scan status, axe result summary and validation events. Rate limiting uses a salted hash of the requester IP rather than storing the raw IP. Email is optional and only used for monitoring early access.