WCAG-tagged findings
Issues are grouped by rule with WCAG level tags where available so teams can prioritise A, AA, or AAA gaps.
WCAG 2.2 AA
Free WCAG checker & audit tool
Test up to 5 pages against WCAG 2.2 Level A and AA, free and with no login.
- Every issue mapped to a WCAG 2.2 criterion
- Grouped by severity, from critical to minor
- Report by email, no account needed
Need more than 5 pages? See audit plans
Live demo
dummy-store.com
Discovering pages...
Discovering pages0 found
- dummy-store.com/
- dummy-store.com/about
- dummy-store.com/contact
- dummy-store.com/pricing
- dummy-store.com/blog
- dummy-store.com/checkout
Free checker
One free scan, up to 5 pages
Enter a website and email, then choose the pages you want to scan. Log in or create an account when you need more scans.
Email required1 free scan per visitor5 page guest limit
Need monthly quotas, dashboard history, PDF exports, or AI fix credits? Compare accessibility scan plans.
WCAG 2.2 oriented
Standard
1 scan / 5 pages
Guest limit
Not required
Login
How it works
How to run a free WCAG audit in four steps
Use the same Inclusense scan engine behind dashboard audits — with a focused guest limit for no-login testing.
Enter website and email
Start a public WCAG-oriented scan without a dashboard account. Email links the report to you.
Discover pages
Inclusense checks your sitemap first, then discovers URLs so you can pick representative pages.
Select up to 5 pages
The guest scanner focuses on a small set of URLs for a fast WCAG compliance snapshot.
Review the report
View scan progress, scores, WCAG-oriented issue groups, and a preview of findings when complete.
What it checks
Which WCAG 2.2 criteria can a WCAG checker test?
An automated scan can flag failures of 17 of the 55 Level A and AA criteria. The other 38 need manual testing with a keyboard and screen reader.
- 1.1.1 Non-text ContentA
- 1.3.1 Info and RelationshipsA
- 1.3.5 Identify Input PurposeAA
- 1.4.1 Use of ColorA
- 1.4.3 Contrast (Minimum)AA
- 1.4.4 Resize TextAA
- 2.1.1 KeyboardA
- 2.2.1 Timing AdjustableA
- 2.2.2 Pause, Stop, HideA
- 2.4.1 Bypass BlocksA
- 2.4.2 Page TitledA
- 2.4.4 Link Purpose (In Context)A
- 2.5.8 Target Size (Minimum)2.2AA
- 3.1.1 Language of PageA
- 3.1.2 Language of PartsAA
- 3.3.2 Labels or InstructionsA
- 4.1.2 Name, Role, ValueA
“Can flag” means the scan catches common failures, not every one. Work through all 55 criteria with the interactive WCAG 2.2 checklist.
Results
What your WCAG scan report includes
Get enough visibility to prioritise fixes. Dashboard plans unlock full audits, history, and exportable reports.
Severity scoring
Critical, Serious, Moderate, and Minor groupings help you focus on barriers that affect users most.
Page-level detail
See which URLs are affected, expand elements, and review HTML snippets before deeper manual testing.
Accessibility score
A summary score gives a quick signal on whether selected pages need urgent remediation work.
Sample report
See what a WCAG scan report looks like
The same overview you get after a scan — score, severity, WCAG levels, and grouped issues.
Scan report — Overview
0
Pages scanned
0
Total violations
0
Unique issues
0%
Avg score
0% score
Accessibility score
Strong foundation with priority fixes available.
5 critical12 serious
Issues by WCAG level
Unique rules grouped by highest WCAG tag
WCAG A8
WCAG AA12
WCAG AAA4
Best practice6
Issues by severity
Unique rules by impact level
Critical5
Serious12
Moderate18
Minor8
Top issues found
SampleseriousWCAG 2.1 AA
Elements must meet minimum color contrast ratio thresholds
14
Elements
6
Pages
criticalWCAG 2.1 A
Images must have alternative text
9
Elements
4
Pages
criticalWCAG 2.1 A
Form elements must have labels
6
Elements
3
Pages
moderateWCAG 2.1 A
Links must have discernible text
11
Elements
5
Pages
What is WCAG 2.2?
WCAG (Web Content Accessibility Guidelines) is the international standard for making web content more accessible to people with disabilities. WCAG 2.2 builds on earlier versions with updated success criteria for focus appearance, target size, dragging movements, and other common barriers. A WCAG checker or WCAG scanner helps teams find patterns that may fail these guidelines before manual review. For every Level A and AA criterion in plain English, see our WCAG 2.2 checklist and quick reference.
Inclusense maps automated findings to WCAG-oriented rules so you can prioritise fixes by level and severity. Not technical? The free website accessibility checker explains results in plain English. For recurring audits, use Accessibility Scans in the dashboard. If your goal is U.S. legal risk specifically, see how to run an ADA compliance audit. To help visitors adjust contrast, text, and reading tools on live pages, add the Accessibility Widget.
Perceivable
Information and user interface components must be presentable to users in ways they can perceive. That includes text alternatives for images, sufficient colour contrast, captions for media, and content that adapts to different presentations.
Operable
Interface components and navigation must be operable. Users need keyboard access, enough time to read and interact, clear focus indicators, and controls that do not rely on complex pointer gestures alone.
Understandable
Information and the operation of the user interface must be understandable. Pages should behave predictably, forms should include clear labels and instructions, and errors should be explained in plain language.
Robust
Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies. Valid markup, correct ARIA usage, and consistent name, role, and value help future-proof accessibility.
Scanner vs dashboard
Start with a WCAG snapshot
When you need recurring scans, larger quotas, or formal audit exports, move into the Inclusense dashboard.
| Feature | Free WCAG scanner | Dashboard audits |
|---|---|---|
| Best use | Quick WCAG issue snapshot | Ongoing WCAG audit workflow |
| WCAG coverage | Automated rules on selected pages | Broader scans, history, and exports |
| Page limits | One guest scan, up to 5 pages | Monthly quotas with paid upgrades |
| Remediation | Public results preview | AI fix guidance, PDF, and shareable reports |
WCAG scanning expectations
Automated WCAG checks are directional, not certification
WCAG scanners can miss issues behind login walls, dynamic content, or complex interactions. They help prioritise violations but do not on their own prove ADA, EAA, Section 508, or full WCAG 2.2 conformance. Pair scans with manual review and remediation.
FAQ
WCAG accessibility scanner FAQ
What is a WCAG audit?
A WCAG audit reviews your website against Web Content Accessibility Guidelines — usually WCAG 2.1 or 2.2 Level AA. Inclusense runs automated WCAG-oriented checks on selected pages and highlights common violations such as contrast, labels, keyboard access, and ARIA issues.
What is a WCAG accessibility scanner?
A WCAG accessibility scanner runs automated checks against Web Content Accessibility Guidelines patterns on your website. Inclusense flags common WCAG 2.2 violations such as contrast, labels, keyboard access, and ARIA issues on the pages you select.
Does this WCAG scanner check WCAG 2.2?
Yes. Inclusense maps findings to WCAG 2.0, 2.1 and 2.2 rules and tags, including 2.5.8 Target Size from WCAG 2.2. Most other new 2.2 criteria, such as focus not obscured and dragging movements, can only be tested manually.
Is the WCAG scanner free?
You can run one free guest scan without logging in. The guest scan allows up to 5 selected pages and delivers a public preview of results by email.
Can a WCAG checker prove full compliance?
No. Automated WCAG scanners are useful for finding and prioritising issues, but they do not replace manual testing, assistive technology review, or a formal accessibility audit.
How is this different from the Inclusense dashboard?
The dashboard supports recurring scans, audit plan quotas, full issue lists, AI-assisted fixes, and Pro or Agency reporting. The public WCAG scanner is a no-login starting point.
Which WCAG criteria can a WCAG checker test automatically?
Automated checkers can flag some failures of about a third of the 55 WCAG 2.2 Level A and AA criteria, such as contrast, missing alt text, form labels, page language, link names and target size. The rest, including keyboard traps, focus order, captions and most of the new WCAG 2.2 criteria, need manual testing.
How do I test my website for WCAG compliance?
Start with an automated WCAG compliance test: scan your key pages to catch issues like low contrast, missing alt text and unlabelled forms. Then test manually: use only a keyboard, check that focus is always visible, and try your forms and checkout with a screen reader. Work through every Level A and AA criterion with a checklist and fix issues in your code.
What is the difference between a WCAG checker and a WCAG audit?
A WCAG checker is an automated tool that scans pages and flags issues it can measure. A WCAG audit is a fuller review that combines automated scans with manual testing using a keyboard and screen readers, and covers every success criterion.
What are the four WCAG principles?
WCAG is based on four principles: Perceivable, Operable, Understandable, and Robust. Together they describe how digital content should work for people with diverse abilities.