Manifest Specification

The accessibility conformance pack begins with:

Text

RESHOT-CONFORMANCE-PACK-V1\n

The remainder is canonical JSON. Binary entries use canonical base64 and the inventory covers the decoded bytes.

Signed body

JSON

{
  "formatVersion": 1,
  "body": {
    "formatVersion": 1,
    "recordKind": "accessibility-conformance",
    "statementId": "statement_…",
    "revision": 3,
    "templateHash": "<sha256>",
    "recordHash": "<sha256>",
    "provenance": "customer-attested",
    "contentCommitment": "<sha256>",
    "timestamp": {
      "authority": "rfc3161:…",
      "responsePath": "tsa/record.tsr",
      "imprintHash": "<same content commitment>"
    },
    "artifactInventory": []
  },
  "packHash": "<sha256 of canonical body>",
  "signerKeyId": "<registry key id>",
  "signature": {},
  "keyRegistry": {},
  "anchor": {},
  "signerTimestamp": {},
  "entries": {}
}

Canonicalization recursively sorts object keys, preserves array order, rejects non-finite numbers, and uses standard JSON encoding.

Inventory

Inventory roles are conformance-record, evidence, verification-report, and tsa-response. Each item includes path, media type, SHA-256, and decoded size. Evidence items additionally include the stable artifact ID, content address, and provenance. Missing, duplicate, uninventoried, size-mismatched, or checksum-mismatched entries fail verification.

record/conformance.json must match the signed statement ID, revision, template hash, and record hash. The content commitment covers this record and every evidence inventory item except the timestamp response. The RFC-3161 response, signed body, origin signature, and signer timestamp bind the complete handoff without a circular hash.

Trust boundary

The registry embedded in the pack is historical context, not a trust root. Strict verification requires signer roots, a current root-signed registry, and TSA trust material obtained independently of the pack. Provenance says who captured the bytes; it does not turn a mechanical or human decision into certification.

The verifier also understands the older capture Evidence Pack V2 format. That format is distinct from this accessibility conformance record and is not used to imply that legacy screenshot-review artifacts are accessibility evidence.