Website Accessibility Quick Scanner
Website accessibility checker
Enter a public URL. The scanner checks the page in a desktop and a mobile view and groups repeated issues by the fix they need.
Free: 1 page, 3 scans a dayPro: €12.99/month for up to 100 pages
- Issues ranked urgent, important or worth improving
- Desktop and mobile view of every scanned page
- HTML report, PDF summary, issues CSV and technical JSON in one ZIP
EXAMPLE RESULTSample data
Pages · 6 · both views
88
Form labels missing7
Contrast too low18
Grouped worklist · not a certificate
- Pages
- 6
- Desktop + mobile views
- 12
- Issue groups
- 5
Formats, limits & file handling
- Works with
- Public HTTP or HTTPS URL
- Free
- 1 page per scan in a desktop and a mobile view · 3 scans a day · free account needed
- Pro
- Scans of up to 100 pages · up to 200 jobs a day · €12.99/month or €89.99/year
- Maximum per scan
- 100 HTML pages · 200 views · 25 minutes
- You receive
- HTML report, PDF summary, issues CSV and technical JSON in one ZIP
- File handling
- Full report 24 hours · comparison baseline 30 days
A scan starts only after you sign in, because the scanner visits other websites on your behalf. Failed scans are never counted. Cancel Pro anytime.
THREE CLEAR STEPS
From a public website to a usable result.
- 01Enter a public URL
HTTP or HTTPS. Sign in with a free account to start the scan.
- 02Review the result
Repeated findings are grouped by action, in the desktop and the mobile view of each scanned page.
- 03Download the report
HTML report, PDF summary, issues CSV and technical JSON in one ZIP, kept for 24 hours. Failed scans are never counted.
Interactive sample report
See what the report gives you.
Run a prepared example for a fictional shop. The displayed address is never sent anywhere.
✓
Sample data onlyNo real website is scanned
Automated score — not a compliance certificateHuman review is still needed.
88/ 100
Accessibility health
Sample report ready
6 pages · 12 views checked across desktop and mobile.
What to do firstAdd programmatic labels to checkout fields, then retest the shared form component.
Compared with the previous matching scan+6 points · 3 fixed · 1 new
Three simple steps
From one URL to a clear worklist.
No installation, site access or setup project.
Enter the public URL
The requested page is checked first. Safe internal links and the sitemap can extend coverage.
Let both views run
Up to 100 pages are rendered on desktop and mobile without submitting forms or pressing action buttons.
Fix the important issues
Repeated findings are grouped, explained and delivered with evidence and a manual-review list.
Prioritised findings
Urgent, important and lower-impact issues in plain language.
Useful evidence
Affected pages, desktop or mobile view and up to 20 marked screenshots.
Shareable report
Accessible HTML, executive PDF, protected CSV and optional technical JSON.
Scan limits and technical safeguards
Automated checks
Supported axe-core A/AA rules plus overflow, touch target, skip-link and focus checks.
Human checks stay separate
Meaning, reading order, complex keyboard flows, captions and instructions never affect the automated score.
Bounded scan
Public pages only · 100 pages · 200 views · 25-minute maximum · reports expire after 24 hours.
Isolated browser
Private targets are blocked. The scanner cannot reach application data, production secrets or internal services.
Does an automated scan prove WCAG compliance?
No. The report is an automated accessibility health review, not a WCAG, EAA/BFSG, ADA or legal compliance certificate. Human evaluation remains necessary.
Does the scanner need access to my website or a browser extension?
No. It checks only publicly reachable HTTP and HTTPS pages, without credentials, cookies or an extension. You do need to be signed in to WoluTools to start a scan, because the scanner visits other websites on your behalf.
What does the scanner do on the website?
It uses safe GET navigation only. It does not submit forms, press action buttons, make purchases or download files.
How far does a single scan reach?
Up to 100 HTML pages rendered in both a desktop and a mobile view, inside a 25-minute budget. If the budget runs out you receive a clearly marked partial report naming the pages and views that finished.
Why are findings grouped instead of listed page by page?
Because the same template defect usually repeats across a site. Grouping by the correction needed turns a long list into a shorter worklist, and every group still names the pages it affects.