You need an auditor whose report your team can fix from, and whose findings hold up when a regulator asks
Proper Access audits websites and apps for digital accessibility, against WCAG 2.2 and EN 301 549, for companies that serve consumers in the Netherlands and must comply with the European Accessibility Act, and for public sector bodies. Our clients are in the Netherlands, Sweden and Germany. We report in English or Dutch at no extra cost.
Audited for, among others
Who you are dealing with
Ten people, trained in house, working on accessibility full time
We have been WAS-certified by the International Association of Accessibility Professionals (IAAP) since 2023, which means our knowledge of the technique and of the standard has been tested against an external bar. Four in ten clients come back for a second audit. Every week we research how browsers and assistive technology behave, and that research goes into the next audit.
The six-eyes principle
- A senior auditor runs the audit
- A second auditor does the internal review
- Every report is checked by three people before it reaches you
We audit and advise. We do not build, and we never mark our own work
We do not build websites and do not manage content, so there is no conflict of interest in what we report. Our own software, the WCAG Radar, is a checker your team uses in the browser; it does not change your site. It is built and hosted in the EU, like everything else we run.
How we test
- Screen readers: NVDA, VoiceOver, TalkBack
- Keyboard only
- Zoom up to 400% and large system text
- Real iPhones, iPads and Android devices for apps
One user story per finding, then the fix
Every finding starts with a user story written from the perspective of the visitor with a disability. One from a recent report: “As a visitor who navigates with a screen reader, a keyboard, a screen magnifier, or who relies on a predictable reading flow, I need dynamically inserted content to appear in the DOM directly next to the element it relates to, because only then does the screen reader announce it in context and does keyboard focus reach it at the expected moment.” Below that come the technical explanation, the code example and the screenshot, so the developer who has to fix it no longer has to guess why it matters. See an example report.
Who you talk to
- Before delivery: a relationship manager
- After delivery: the senior auditor who wrote your report
- Questions run through accessibility credits: one credit is one question, follow-ups in the same thread are free
Send us your URL and you get a project estimate, with no obligations
Use the contact page, e-mail [email protected], or schedule a video call. We reply within one business day.
Amsterdam
- Keizersgracht 520 H, 1017 EK Amsterdam, the Netherlands
- Phone or WhatsApp: +31 85 5055 890
- Chamber of Commerce (KVK): 95350985
Get clarity on your digital accessibility, without the stress
Schedule an introductory meeting. No commitments, just a concrete picture of your risks and opportunities.
Schedule an introduction
