This translation has not been editorially reviewed yet. The German version is authoritative. German version →
ContentsScreening in ongoing operation
Screening in ongoing operation
A website is not finished after the relaunch. Every update, every extension, every new piece of content can create a finding. A repeat audit measures the same pages against the same rule set and shows the change.
What is measured
These audit areas carry the topic. Each leads to its checks with explanation, measurement path and remedy.
- CurrencyDetected CMS, extensions and libraries past their maintenance end, determined passively, without credentials.5 articles
- Loading performanceLoading behaviour, responsiveness, layout stability, measured rather than estimated.8 articles
- Accessibility (WCAG 2.2 AA)Measured in a real browser across three device profiles. A substantial share of these criteria cannot be decided by a machine; those stay visibly open until a human auditor has ruled on them.86 articles
- Data protection & cookiesWhat loads before any consent, whether pressing “reject” actually stops it, cookies set before a choice was made, remotely loaded web fonts, and the presence of a privacy notice.15 articles
What a repeat audit delivers
- The same scope and the same rule set as the first run; the measured scope is billed.
- The history in the audit file: findings that stay, that disappear, that are added.
- On renewal the subscription discount, if the operator has set it up.
Why seals expire
The seal shows its audit date. After twelve months it expires because websites and technology change. The verification page shows that, as well as a revocation.
Software currency as early warning
The audit area software currency detects CMS, extensions and libraries past their maintenance end from the delivered page, without credentials. Whoever measures it regularly sees maintenance needs before they become an incident.
Photo: Alan Levine, CC BY 2.0
