Accessibility of this site and WCAG Radar
WCAG Toolkit is built by Proper Access, an audit firm for digital accessibility in Amsterdam. We measure client sites against WCAG 2.1 and 2.2 at level AA. This page is about what that same measurement returns when we point it at our own tools.
The audit is done. It produced 23 findings and all of them have been resolved. The retest report is linked below.
Last updated:
What this statement covers.
Four parts, all built and run by Proper Access. They share one codebase and one server in Helsinki.
- wcagtoolkit.com
- The English site, including the portal where you manage your licence and the pages where you pay.
- testtoegankelijkheid.nl
- The Dutch site. Same pages, same code, different language.
- WCAG Radar
- The bookmarklet and the browser extension for Chrome and Firefox, including the panel, the options page and the report you can save.
- The scan
- The form where you enter an address, and the report you get back.
properaccess.nl is not covered here. That is a separate site at its own address.
What we measure against.
WCAG 2.1 and 2.2, level AA. The same standard we apply at clients, and the standard the European norm EN 301 549 points to for websites and apps.
The success criteria are in the W3C WCAG 2.2 Recommendation.
Where we are.
No verdict goes on this page without a report behind it. That report is here now.
| Part | Audit | Report |
|---|---|---|
| The two websites and WCAG Radar | Completed | 22 August 2026 |
The report is on the Proper Access site: retest of wcagtoolkit.com, August 2026.
Nothing on this page goes beyond what is in the report. The audit covered the sample listed in it, so that is what the outcome holds for. A conformance claim without a report behind it is exactly what we tell clients not to do.
Known problems.
Nothing from the audit of August 2026 is still open. All 23 findings were resolved and tested again in the retest. If a later audit turns something up, it appears here, with per finding:
- What fails, in plain language
- Which success criterion it touches
- Who it affects, described from the visitor
- What you can do in the meantime
- When we have fixed it
How we audit this.
An auditor walks it through
With a keyboard only and with a screen reader. The question each time is whether the reading order holds, whether every element has a name that says something, and whether focus can always move on.
With tools alongside
axe-core and WCAG Radar itself run along to catch what a machine can determine. Those two find 30 to 40 percent of the problems, so they do not decide the outcome.
Ordered per element
The same ordering as in our client reports: the way the site is built, with a user story from a visitor with a disability at every finding.
The extension too
The Radar runs in its own panel on top of someone else's site. That panel is tested for keyboard operation, contrast, and the order a screen reader reads it in.
Run into something?
Tell us, also when you are not sure it is us. Describe what you were trying to do, on which page, and which browser or assistive software you use. That saves us reproducing it.
You get an answer within two working days from someone who can judge it. If we cannot fix it straight away, you hear what the alternative is and when we will.
If you and we do not get there
You can report a digital channel that is not accessible to the Dutch Authority for Consumers and Markets (ACM). It supervises the accessibility rules for online shops and communication services. Report it to ACM ConsuWijzer. That form is in Dutch.
emailinfo@properaccess.nl
phone+31 85 5055 890
AddressProper Access B.V.
Keizersgracht 520 H
1017 EK Amsterdam, NL
What this statement is not.
This is not an accessibility statement under the Dutch government accessibility decree. That decree applies to public sector bodies, and Proper Access B.V. is a company. We publish this statement voluntarily.
Dutch public sector bodies publish theirs in the register at toegankelijkheidsverklaring.nl. If you have to write one and get stuck on the evidence, give us a call.