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 Skeptic
Anonymous two-way dialogue runs on a system-generated report ID and a self-chosen password with no email address, the form is available in up to 26 languages with optional DeepL translation, QR-code entry is documented, and spoken reports are recorded in the browser — the vendor states it operates no telephone hotline and implements the oral report under section 16(3) that way, fully anonymously. Accessibility is addressed through a WCAG 2.1 AA and EN 301 549 self-assessment rated "largely compatible", uploads and voice messages can be stripped of author and GPS metadata, and the pages state no logs are written that could identify a reporter. The self-assessed rather than audited accessibility and the pay-per-use translation keep this just below the top level. 15 16 11 2 19