Reshot

Record Overview

Records are the provenance and retention layer beneath Reshot's accessibility workflow. An accessibility program can retain the exact scoped evidence, criterion decisions, remediation history, conformance revision, and verifier material that supported a human decision. Delivery policy can optionally use the same mechanical evidence in CI; it is an output, not a separate workspace.

Record states what rendered and what mechanically decidable checks observed. It does not certify that a product complies with WCAG or any law.

Evidence lifecycle

  1. Scope the product version, complete processes, checkpoints, contexts, and evaluators in Conformance.
  2. Capture those experiences through hosted discovery, the recorder extension, or a customer-controlled runner.
  3. Resolve mechanical findings, guided human evaluations, exceptions, and remediation verification in the shared evidence graph.
  4. Approve an attributable, immutable conformance revision.
  5. During the private pilot, Reshot can seal the selected artifact checksums, provenance, template identity, and decisions into a deterministic record.
  6. A recipient can inspect the shared revision and verify the retained pack against independently obtained signer roots and timestamp authority trust.

Provenance is part of the artifact

  • independent means a trusted Reshot hosted worker performed an eligible public capture and the complete worker-to-storage custody chain verified.
  • customer-attested means the customer's browser or runner performed it, including recorder-extension and CI captures.

The value is inside the hashed manifest body. It cannot be relabeled after seal without changing the manifest hash. Unknown provenance defaults to customer-attested, never independent.

Evaluation and conformance records

Accessibility is the only GA evaluation preset. Mechanically decidable checks use ACT-style passed, failed, cantTell, inapplicable, and untested outcomes. Criteria that require human judgment use guided protocols and retained evidence; they are never asserted as machine-proven facts. Consent and dark-pattern evaluation are unavailable and are not part of the GA registry.

An Accessibility Conformance Record (ACR) is a revisioned human decision over explicit scope and evidence, not a summary inferred from one run. Every non-supporting criterion cites its context and evidence. New relevant evidence marks affected revisions stale rather than silently changing the old decision.

ACR versus evidence pack

An ACR is the accessible HTML, PDF, DOCX, JSON, or EARL-facing report. An evidence pack is the portable Record artifact: selected captures, criterion decisions, the embedded manifest, rule and template identity, origin signature, and time anchor. See Evidence Packs and the Manifest Spec.

Current availability

Record sealing remains contract-gated and private-pilot. There is no self-serve Record checkout. The application can publish and share an accessibility conformance revision without implying that production signing, timestamping, long-term retention, or independent capture are generally available. Promotion requires a live production capture → seal → anchor → meter → export → offline verification journey.

Next reads