This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung →
Measuring twice: why a varying finding isn't a finding
Every layout finding is collected twice per device profile. Only what both runs see gets reported. If a result varies between the measurements, that's exactly what the report states — instead of a finding nobody can reproduce.
- Layout measurements are time-dependent: fonts arrive, images get swapped in, scripts rebuild areas. Anyone who measures once occasionally gets a result that's gone on the next visit.
- The conservative evaluation is deliberate: a false positive costs the operator time searching for an error that doesn't exist, and damages trust in every other finding. A missed finding is annoying; a fabricated one is worse.
- For the same reason, undersized controls count by the smaller of the two measured numbers — what gets reported is what's certain.
FAQ
Why does the report say "finding varies"?
Because the two measurements had different results. That points to timing-dependent behaviour and needs a look on a real device — it isn't treated as a confirmed error.
Could this mean real errors get missed?
That's the price we deliberately accept. An audit service whose findings dissolve on closer inspection loses its value faster than one that occasionally misses an edge case.