From checks to reports: communicating compliance to the institutions being assessed – AVAILABLE

Topics: web development, data visualisation, human-computer interaction, transparency

Technologies: javascript, web development, python (for the underlying checker output)

Tldr; take the raw output of a compliance checker and turn it into an institutional report that the organisation being assessed can actually read, understand, and act on.

Motivation: A scan that produces a wall of pass or fail results helps no one. For a compliance checker to change behaviour, its findings have to be communicated to the institution in a form that explains what was checked, what was found, why it counts, and what to do about it, without overstating the machine’s confidence. This is a design and communication problem as much as a technical one, and it is where a checker either earns trust or loses it. This project designs, builds, and evaluates the reporting layer that sits on top of the checker.

Implementation: You will take the structured output of the compliance checker and design an institutional report format that presents findings clearly across the nine categories, distinguishes deterministic results from AI-assisted judgements, shows the evidence behind each finding, and communicates uncertainty honestly rather than hiding it. You will build the report as a web interface, and you will evaluate it, ideally with people who work in the kind of institution being assessed, on whether they understand the findings and know what action to take. The deliverable is a working reporting interface and an evaluation of how well it communicates.

What you will learn: (i) how to present technical compliance findings to a non-technical institutional audience; (ii) web interface design and development; (iii) how to communicate uncertainty and the limits of automated assessment; (iv) how to run a lightweight evaluation with real users; (v) how presentation affects whether findings are trusted and acted upon.

References: 

[1] dotPublic compliance checker prototype: https://dotpublic.org/checker 

[2] Web Content Accessibility Guidelines (WCAG): https://www.w3.org/WAI/standards-guidelines/wcag/