WCAG Toolkit: two free tools to test your website against WCAG
WCAG Toolkit is free tooling from accessibility audit agency Proper Access. Every audit report has findings that sit in the content: an alt text that doesn't describe the image, headings that skip a level, a link called “read more”. These two tools point them out while you are working on the page.
- 29 checks free
- no account
- works behind a login
- sends nothing
900+audits carried out since 2019
Among others for
- Rijksmuseum
- NRC
- Province of North Holland
- Province of South Holland
- Dutch Museum Association
- Plus
- Jumbo
Two tools, built out of our audit work.
Across more than 900 audits we kept track of which mistakes came back and where people got stuck once they started testing themselves. That is where these two come from.
WCAG Radar
Content writing · design · development
Test the page you are working on right now, in your own browser. You see per theme what is wrong. Works behind a login and on a staging site too.
- alt text
- headings
- link text
- contrast
- focus
- tab order
Accessibility scan
A first picture of a whole site
Give us a public address. We walk up to 10 pages, give a score from 0 to 100 and email you the report with the findings per page.
Where tooling stops.
A machine finds 30 to 40 percent of the problems on a page. The rest is something no tool establishes for you, ours included.
A machine establishes this
- button without a nameerror
- contrast 3.1:1, requirement 4.5:1error
- tabindex="5"error
- html lang="en"good
- decorative image, alt emptygood
Measurable, in milliseconds, and exactly what you shouldn't have to walk through by hand.
A person reads this back
- Does the alt text describe the image, or repeat the file name?
- Does the error message explain what to do?
- Is this form workable when you cannot see the screen?
- Does the sentence read aloud match what is on the screen?
No tool answers these. The Radar does line them up for you, so you can judge them.
Why this site exists.
The tools here come out of our audit work. Across more than 900 audits we kept track of which questions came back and where people got no further once they started testing themselves. Those notes became the Radar's list of checks, split by role: an editor has different questions than a developer.
The articles that go with them are on properaccess.nl. The Radar links to them per check.
Anyone who can do it themselves needs us less often. We do it anyway.
A site that goes well while it is being built is cheaper than an audit afterwards, and we would rather work on the hard cases than on buttons without a name.
An auditor reads that back.
From here Proper Access takes over
The report is ordered per element, the way your site is built. Every finding starts with a user story from a visitor with a disability, so whoever fixes it knows straight away what it is about.
- Ordered per element, the way your site is built. The rest of the market orders by success criterion.
- One user story per finding, from a visitor with a disability
- We don't build websites ourselves, so we never audit our own work
- Direct access to the senior auditor who wrote your report
Need help with interpretation?
Don't follow a finding, or unsure which fix suits your setup? Every check has a link to an auditor at Proper Access. One credit is one question about one topic, and follow-up questions in that same conversation cost nothing extra. If you have a report from us, you talk to the senior auditor who wrote it.
Last updated: