Findings, owners and verified rechecks
Move from an observation to a reviewed fix and compatible verification.
How to use this guide
Open the affected URL and evidence before assigning priority, owner, due date and work status. Observation history is separate from manual completion. A developer handoff describes the intended change; it does not authorize repository access or publication.
Review the result and limitations
After the approved change is live, preview the affected pages and allowance, then confirm an eligible targeted recheck or new audit. Only compatible successful evidence can verify a fix. Failed, redirected or absent pages stay unverified; a later return is recurrence. Rechecks do not rewrite the original audit score.
Current sources and related guidance
Current reference: audit methodology and live plan catalog.
Feature availability depends on permissions, plan, workspace policy and configured services. About availability