React release worksheet

Trace a dynamic journey from patch to live result

A source change can be correct while a route transition, form error, or dialog still fails in the released app. This worksheet separates three evidence stages, so a finding stays open until the actual interaction has been checked on the live build.

Three independent checkpoints

Source: identify the exact HTML, JSX or TSX file and element. Review the proposed patch rather than assuming a scan result contains the solution.
Release: record the approved branch and deployed build. A code review is not a production deployment.
Journey: repeat the original interaction on the live route. Use keyboard access and, where appropriate, assistive technology to check focus, labels, messages and the next action.

Build a release check note

Affected live route State-changing action Deployed build or release identifier

Evidence actually observed Exact source file and element reviewed Approved patch present in deployed build Original journey repeated on live route Keyboard focus and changed messages checked

Record the route and observed evidence first.

The React source repair and live verification workflow distinguishes an Agent in the shared app shell from reviewed permanent source patches, normal deployment, and a live result check. It also notes that dynamic user journeys, content meaning and keyboard behavior still need appropriate manual testing. The W3C evaluation overview explains why tools alone cannot establish accessibility. This page records a test plan; it does not test or certify a site.