What changed, and why.

Our own accessibility statement, and the legal set

We publish an accessibility statement for eaacompliance.org produced the same way our customers' are — including the problems we have not fixed yet. Alongside it: privacy notice, terms, data processing agreement and imprint.

• The statement names three real defects on our own site rather than claiming a clean sheet.
• Analytics are aggregate page counts with no cookies and no identifiers, so there is no consent banner to dismiss.

Status page and this changelog

Self-hosted status with ninety days of component history, and a public record of every change that touches your evidence, your documents or the API.

Client workspaces, pooled capacity and white-label documents

Agencies run each client as a separate evidence file — own domains, matrix, sign-offs and ledger — while capacity comes from one shared pool.

• Opening a client workspace writes an entry in that client’s ledger, every time.
• Settings: authorize colleagues by Google account, manage API keys and webhook endpoints yourself.

Enforcement tracker across the EU27 plus Norway

A living register of how each country actually enforces: the national instrument, the market surveillance authority, transposition status and the real enforcement route — private demand letters in Germany, injunctions in France, regulator sweeps in the Netherlands.

• Country files with a per-regime response timeline.
• Curated event feed rather than scraped noise.

Project opened: continuous evidence, not one-off audits

First commit on a platform built around a single premise — an accessibility audit is a photograph, and the European Accessibility Act asks for a film. Everything that follows is in service of a continuously maintained evidence file.