Free WCAG 2.2 AA scan
Check any page for accessibility issues
Paste a URL. We load it in a real browser, run the axe-core WCAG 2.2 AA rules, and show the most serious issues with the element, the severity and the fix. Add your email to get the full report.
✓ One page free ✓ Nothing installed ✓ Results in under a minute
WCAG 2.2 AA
Rule set
axe-core
Test engine
Section 508
US federal
EN 301 549
European
What you get back
Findings a developer can act on
Each issue names the element, the WCAG criterion it fails, and the change that fixes it. Repeated failures are grouped by root cause, so one fix clears many instances.
northwind-dental.com/contact
Sample
Free single-page scan
7 WCAG failures from 2 root causes
Plus 2 best-practice notes. This is what your results page looks like.
Critical
WCAG 1.3.1, 4.1.2 · label
3 elements
Form fields have no accessible label
<input type="email" placeholder="Your email">
FIX
Add a visible <label for> tied to each input. Placeholder text is not a label.
Serious
WCAG 1.4.3 · color-contrast
4 elements
Text contrast below 4.5:1
#9CA3AF
→
#6B7280
on #FFFFFF · 2.5:1 → 4.8:1
FIX
Change .footer-note to #6B7280. One CSS change clears all four.
How the scan works
From URL to fix list in three steps
Step 1
Load the page
A headless Chromium browser opens your URL and waits for JavaScript, so page builders and single-page apps are tested as visitors see them.
Step 2
Run WCAG 2.2 AA rules
axe-core tests the rendered page against the WCAG 2.2 AA criteria it can check automatically.
Step 3
Group and explain
Failures are grouped by root cause and sorted by severity, each with the element, the criterion and the fix.
What the scan checks
The WCAG failures machines can reliably detect
WCAG 1.4.3
Colour contrast
Text that's too faint against its background.
WCAG 1.1.1
Image alternatives
Images and icons with no text alternative.
WCAG 1.3.1, 3.3.2
Form labels
Inputs a screen reader can't identify.
WCAG 2.4.4, 4.1.2
Link and button names
Controls with no accessible name.
WCAG 1.3.1, 2.4.1
Headings and landmarks
Page structure that assistive tech relies on.
WCAG 4.1.2, 3.1.1
ARIA and language
Invalid ARIA attributes and missing page language.
The transparency pact
What a free scan can't tell you
Automated tools catch roughly 30–57% of accessibility issues. A clean result is a good sign, not a compliance certificate.
Automated limits
What automated rules miss
- Whether keyboard order and focus make sense
- Whether alt text actually describes the image
- Screen reader flow through menus, modals and checkouts
- Captions, audio descriptions and reading order
Compliance realities
No guarantee, no overlay
We don't claim a scan makes a site ADA or EAA compliant, and we never inject a widget to hide problems. For sites with legal exposure, the next step is a manual accessibility audit.
About manual auditsFree or paid
Scan one page free, or monitor every client site
Free scan
One page, one time
- WCAG 2.2 AA rules with axe-core
- Findings grouped by root cause
- The two most serious causes explained on screen
- Full report by email
Agency plans
Every client site, on autopilot
- Full-site crawls from the sitemap
- Scheduled scans and regression alerts
- Sites grouped by client
- White-label reports with your logo
- Client quote requests into your workspace
Free scan FAQ
Questions about the checker
Is this an ADA compliance checker?
It checks a page against WCAG 2.2 AA, the standard courts and regulators reference for ADA and EAA. No automated tool can confirm compliance on its own: automated scanning catches roughly 30–57% of issues. Sites with legal exposure need a manual audit as well.
Can I scan a whole website?
The free scan checks one page. Agency plans crawl the sitemap on a schedule and group every finding by root cause.
Do you install anything on my site?
No. We load the page in a browser on our side. Nothing is added to your site.
Get started today
Scan one page now. Monitor every client site next.
No overlays, no empty guarantees. Just the issues, where they are, and how to fix them.