One-sentence brief
A usability or accessibility finding has little value if it cannot be reproduced, tied to an exact revision, propagated to dependent content, and re-tested after correction.
EVIDENCE REVIEW WORKBENCHES
A version-bound method for recording what was tested, what failed, what changed, who owned the remedy, and which evidence must be repeated before a route or revision can be relied upon.
ORIENTATION
A usability or accessibility finding has little value if it cannot be reproduced, tied to an exact revision, propagated to dependent content, and re-tested after correction.
WORKING BRIEF
Record the release, route, content or interface fingerprint, browser and device class, language, access mode, test fixture, and date. A result for one revision does not silently transfer to a changed one.
Observed task events, participant statements, assistive-technology output, timing, and errors should be distinguishable from the evaluator's interpretation, severity, and proposed remedy.
A material issue needs a stable identifier, reproduction steps, affected evidence or task, severity rationale, owner, status, and links to every route or record that may inherit the defect.
The correction record states what changed, what did not change, which risks remain, whether static parity or rollback was used, and which previous evidence is superseded rather than deleted.
Re-test the failed task and the nearby regression risks, including access paths and low-bandwidth or reduced-motion alternatives. Automated regression can confirm code behavior but cannot substitute for human task evidence where the defect was human-facing.
Public correction notes can describe the affected route, issue, remedy, date, and remaining limitation without exposing participant identity, sensitive accommodations, raw recordings, or private review details.
COMPLETE DOSSIER
Terms are defined for this site’s evidence method, not as universal legal or clinical definitions.
| Stage | Required record | Authority limit | Reopening trigger |
|---|---|---|---|
| Plan | Task, coverage, comparator, measures, privacy, stop rule | Not evidence that testing occurred | Material scope or risk change |
| Observe | Version-bound task and access-mode evidence | Observation is not final interpretation | Reproduction failure or missing context |
| Decide | Scoped severity, owner, remedy, rollback, exclusions | Decision applies only within stated authority | New evidence or conflict |
| Correct | Exact change and propagation record | Change is not proof of resolution | Regression or dependent-route change |
| Re-test | Repeated failed task and adjacent regression evidence | Pass is not universal certification | Later material revision |
Can the evidence be tied to the exact tested route and revision?
Pass condition: Release, route, configuration, language, task, and access mode are recorded.
Can another accountable evaluator reproduce the finding?
Pass condition: Observation, steps, expected behavior, actual behavior, and evidence references are distinct.
Did the remedy reach every affected public and protected derivative?
Pass condition: Content, templates, rules, UAI records, docs, tests, sitemap, and manifests are updated together where applicable.
Was the failed task and nearby regression risk repeated after correction?
Pass condition: The result is bound to the corrected revision and residual limitations remain visible.
RESEARCH EDITION
This page follows the public method for provenance, confidence, source independence, alternative accounts, limitations, review state, and visible correction.
CONTINUE