How to propagate a criterion's status across samples to save time on repeated patterns.
What propagate status is
Propagate status copies the verdict of a criterion from one sample to every other sample where the same criterion is still Not tested. It targets the common case where one template, partial, or component drives the same outcome on many pages.
Example: lang="en" is set by the shared layout site-wide. Confirm it once, propagate Success to the rest, skip twenty repeat checks.
How it works
From any finding, propagate its current verdict to all samples where this criterion is still Not tested.
- Only Not tested findings are overwritten. Already-evaluated findings (Success, Failure, Not applicable, Derogation) are never silently changed.
- Problem text, solution text, and screenshots can optionally be copied along with the verdict.
When to use it
- Outcome is template-driven and the template is shared across samples (lang, skip link, footer landmarks, cookie banner, global header).
- The criterion is Not applicable by nature on every sample (e.g., no audio anywhere in the service).
When not to use it
- The criterion depends on per-page content (alt text, page title, headings, form labels). Evaluate individually.
- You haven't looked at the other samples yet. Faster, but undermines defensibility.
- The verdict is Failure but the failing element is page-specific.
When "it depends"
Think twice before propagating a Failure. The day the issue is fixed, you'll have to walk every sample back to Success by hand.
Why it saves time
Per-sample audit time decreases on larger audits because templates repeat. Propagate status turns that repetition into a shortcut: record once, propagate everywhere. The more consistent the codebase, the more time saved. See methodology / audit process.
Where it lives in the UI
- Finding editor — propagate action on each evaluated finding.
- Audit grid — quick propagate from the inline finding cell.