Reporting channels & reporter experience
How this is scored
The intake side: how a reporter actually submits — web form, anonymous dialogue, phone or voice message, languages, accessibility — and whether anonymity survives first contact.
0 — Not a reporting channel; a general contact or survey form with no anonymous route and no way to reach the reporter afterwards.
3 — A web form that accepts anonymous reports, with a case number or access code the reporter can use to check the report later.
5 — Anonymous two-way dialogue through a protected mailbox or access code, the reporting page in several languages, and use on mobile devices without an app or account.
8 — Several channels (web, voice message or phone hotline, in-person meeting requests, QR or intranet entry points), broad language coverage with translation of messages, accessibility addressed, and voice distortion or another anonymity measure for spoken reports.
10 — Intake engineered around the frightened reporter: every channel usable anonymously, dozens of languages, WCAG conformance stated, no app or account required, and the vendor documents how the reporter's identity is kept out of the channel itself.
The Compliance Officer
Intake is engineered for the frightened reporter: anonymous reporting with a system-issued report ID and a self-chosen password with no email address required, browser voice messages implementing oral reports under section 16(3) of the Whistleblower Protection Act without any voice service provider, QR-code entry, and the form in up to 26 languages with DeepL translation available. The vendor documents that no IP addresses or system log files that could identify a reporter are written and that author and GPS metadata can be stripped from uploads and voice messages. I hold back a point only because the WCAG 2.1 AA claim rests on a self-assessment rated 'largely compatible', and the vendor itself states it operates no telephone hotline, substituting the browser voice message for spoken intake. 15 16 2 19 11