Skip to main content
Delivery policy is an output of the accessibility program. It is not a product track, workspace, or substitute for the barrier and conformance workflows.

​
Begin advisory

Connect the repository only after representative experiences and rule behavior have been reviewed. Advisory status reports the new evidence and links to the affected barrier without blocking a merge.

​
Enforcing policy

An enforcing policy may fail only for a newly introduced result that is:
  • mechanically supported by a frozen rule contract
  • inside the approved project, experience, context, and branch scope
  • above the configured severity threshold
  • calibrated as sufficiently high confidence
  • not covered by an active approved exception
Human-review findings, advisory or AI output, cantTell, untested, worker failure, unavailable services, and billing or active-flow overage never become a false accessibility failure. Exceeding the active-flow allowance never blocks CI. GitHub, GitLab, and Azure DevOps receive equivalent status semantics through their native provider protocols. Delivery is idempotent and retry-safe. A provider outage remains an integration failure, not an accessibility verdict.

​
Review the result

Follow the status link to the execution, retained evidence, durable barrier, and policy explanation. Remediate and rerun the affected experience. Closing a barrier requires new post-remediation evidence; changing repository status does not rewrite the accessibility history.