Results & findings

Every run writes result.json, validated against result.v1.schema.json (packages/spec). Top-level fields: version, tool, spec, startedAt, finishedAt, status, pages, findings, and optionally error, ai and notes (limits the run hit that are not findings, e.g. unscanned sitemap urls left unchecked).

Run status

Status	Meaning
passed	All checks ran, no findings.
issues_found	At least one finding.
execution_error	The tool or browser failed. Not a statement about your site.
timed_out	The run deadline was reached.

A finding

A real finding from a run against the bundled fixture site:

{
  "id": "f4",
  "check": "overflow",
  "code": "horizontal_overflow",
  "severity": "error",
  "url": "http://127.0.0.1:8080/de/produkte",
  "locale": "de",
  "viewport": "mobile",
  "message": "The page is 226px wider than the 390px viewport and scrolls sideways.",
  "provenance": "deterministic",
  "evidence": {
    "expected": "390px",
    "actual": "616px",
    "elements": [
      { "tag": "div", "selector": "body > div", "rect": { "x": 16, "y": 126, "width": 600, "height": 22 } }
    ]
  }
}

Field	Description
check, code	Rule identifier. See checks.
severity	error, warning or info.
url, locale, viewport	Where the issue was found. viewport is all when it occurs on every viewport.
pages	Only on a sitewide finding: the same defect with identical evidence (e.g. a dead link in a shared footer) on 3 or more pages is reported once. pages lists every page in scan order; url is the first. Findings whose evidence differs per page are never merged.
provenance	deterministic for rule-based findings. Findings from the optional AI step are marked for review.
evidence	Expected and actual values and the elements involved.

webauditlabs Cloud stores the same finding and adds project, run and review information around it; the finding fields do not change.