CONSENTVEIL EDITORIAL · 17 NOVEMBER 2026

A score is compact. A technical result is not. Before using a number to make a decision, look at what was tested and what was left outside the assessment.

Coverage comes before the number

Monitor calculates its score from passes, failures, warnings and inconclusive results. Unsupported and not-requested results are excluded from the fraction.

That means a high score can coexist with limited coverage. If one eligible test passes while the other tests are unsupported or not requested, the score is 100. That does not establish that the site has been comprehensively checked.

An inconclusive result is useful information

A timeout or an undetected control can prevent a test from completing. Treating that as a pass would hide an important limit. Monitor keeps inconclusive results visible and includes them as non-passes in the score.

The useful question is what prevented the observation, and whether a more specific configuration or a further investigation is needed.

Confidence and severity answer different questions

Severity describes the technical weight assigned to a test. Confidence describes how certain the measurement is. A high-severity finding with low confidence is an invitation to investigate carefully, not a legal conclusion.

Read the report as a record of a run

Check the pages, browsers, locales, time and methodology version. Then examine the findings and evidence. Comparisons across unrelated sites or different configurations can make the score appear more meaningful than it is.

The report is a technical observation, not a compliance certificate. See an illustrative finding and read the status definitions.