Accessibility audits your developers will finish
2,184 accessibility errors. 12 fixes.
CauseScan crawls your site, runs the WCAG 2.1 AA rules, and groups every violation by the component that causes it. Your team fixes the cause once instead of chasing the same symptom page by page.
- Free while in beta
- Read-only, honours robots.txt
- Results in minutes
- Fixes to make
- 12
- Violations they clear
- 2,184
- Top 3 clear
- 88%
- Icon buttons in the site header have no accessible namecritical
- Footer links fail colour contrast (3.1:1, needs 4.5:1)serious
- Product card images are missing alt textcritical
Why the list is short
Thousands of symptoms. A handful of causes.
Sites are built from templates and components. One unlabelled button in a shared header is reported on every page that uses it. Other checkers list every copy; CauseScan traces them back to the component and lists it once.
How it works
From a URL to a fix list
- 01
Crawl
Give us a URL. We follow same-site links, honour robots.txt and read pages in a real browser without changing anything.
- 02
Test every page
Each page runs the axe-core WCAG 2.1 A and AA rules, the open-source engine behind most accessibility tooling.
- 03
Group by cause
Violations are fingerprinted by rule and by the component they sit in, so the same broken header counts once, not once per page.
- 04
Fix in order
You get a short list ranked by reach: an example of the failing HTML, its selector, and every page the fix will clear.
Who it’s for
For the people who have to do the fixing
Agencies & freelancers
Turn “are we accessible?” into a scoped piece of work. A ranked fix list is something a client can approve and a team can estimate.
Product & front-end teams
Legal flagged it, Lighthouse shows 900 issues, nobody knows where to start. Start with the dozen components that cause them.
Public sector & education
Work through WCAG 2.1 AA site by site, and re-scan to show the backlog shrinking.
Why now
WCAG 2.1 AA is becoming the law
Automated testing is where an accessibility programme starts, not where it ends. It finds the repeated, mechanical failures fast, so your people can spend their review time on what only people can judge.
- European Accessibility Act
- Has applied since 28 June 2025 to many products and services sold in the EU, including e-commerce and banking.
- ADA Title II
- The US Department of Justice requires state and local government sites to meet WCAG 2.1 AA, with deadlines from April 2026.
- Section 508
- US federal agencies and their suppliers must meet WCAG 2.0 AA.
Pricing
Free while in beta
$0 during the beta
- 20 scans a month
- Up to 50 pages per scan
- Full grouped report with affected pages
Paid plans for teams and agencies are on the way.
Questions
Is this a compliance certificate?
No. Automated rules catch only a subset of WCAG 2.1 AA failures — things like keyboard traps, reading order and the quality of alt text need a person. CauseScan reports violations it found; conformance needs a manual review by a qualified assessor.
Do you change my site or inject anything?
No. We only read pages, the way a visitor would. There is no script to install and no widget. Fixes happen in your source code.
How is this different from an accessibility overlay?
Overlays add a widget that tries to patch the page in the browser, and many disabled users find them get in the way. CauseScan points your developers at the components to fix, so the fix ships to everyone.
Why group by component instead of listing every error?
Most sites are built from templates. A header with an unlabelled button shows up on every page, so a 50-page crawl reports it 50 times. Grouping shows it once, with the 50 pages it affects.
Which pages will you scan?
Pages on the same site as the URL you enter, found by following links from it. We skip anything robots.txt disallows and never scan private or internal addresses.