Important instructions appear only in screenshots. The useful response is a targeted correction with an observable acceptance check. That keeps the repair tied to the problem instead of turning it into an open-ended redesign.
Find the likely cause
The text assumes everyone can interpret the image.
Treat this as an explanation to verify against the actual work. Look at the input, the relevant decision, and the final result together. If the evidence does not support this diagnosis, investigate the mismatch before applying a convenient but unrelated fix.
Make the targeted correction
Write the required action and use the screenshot as supporting context.
Accessible content communicates its structure and meaning in ways that work across different reading and interaction needs.
Check that the repair worked
Complete the task using the text instructions alone.
Repeat the check on the final version that the reader or customer will encounter. An approved draft, a preview, and a published result can differ; the acceptance decision should concern the version people actually use.
Prevent the next related failure
A separate issue to watch for is this: content relies on color to communicate status. Add text labels or another clear indicator.
Monitor the useful outcome
Track unresolved accessibility defects and successful completion of representative reading tasks.
Keep a short record of the original symptom, the evidence behind the diagnosis, and the result of the acceptance check. That record makes the solution reusable when the same condition appears again, without assuming that every superficially similar problem has the same cause.
Official reference for the platform or standard discussed: W3C WAI: image alternatives.