Prepare accessibility concerns without claiming a completed audit

State which evidence supports the concern

A screenshot can show overlapping text or an obscured control. It cannot establish focus order, accessible names, keyboard behavior, or screen-reader output. Describe the concern at the level the evidence supports. If a qualified reviewer has tested the interaction separately, preserve those findings in the normal accessibility record rather than implying the screenshot performed that test.

Capture the relevant visual state

Use supported media with safe sample data and enough surrounding context to locate the affected element. For an error banner covering a submit action, show the form and validation state. Review the candidate findings in Retick and remove claims that overstate certainty. Add the tested build, viewport, zoom conditions, and any independently verified interaction details manually.

Define the approved correction carefully

Ask the appropriate owner to approve an outcome such as keeping the message readable and the action reachable under the reported conditions. Keep technical accessibility requirements tied to the tests and expertise that establish them. Review selected findings before exporting to Trello or downloading a file. A generated suggestion is not an authoritative interpretation of a standard or a compliance determination.

Verify using appropriate methods

After a change, inspect the visual state and run the relevant keyboard, assistive-technology, and automated checks your process requires. Have a qualified reviewer assess the result where appropriate. Retick does not certify accessibility compliance, run a complete audit, or establish that every user can operate the interface through media analysis. It can help organize evidence and a handoff while the actual assessment remains independent.