Text evidence can make a screen problem easier to share

Keep the words that identify the issue

The exact error text, app name, screen heading and observation time give support a useful starting point. Replace any secret value with a clear removed-value marker. Do not paraphrase the error so heavily that it becomes a different message. If translation is needed, label the translation and retain the original wording privately where relevant and safe.

Separate observation and interpretation

“The app displayed this date” is an observation. “The renewal failed” is a conclusion that may require the account relationship and seller confirmation. A text report can make this distinction explicit. That is useful when a screenshot from an old profile looks similar to the current one. The record should identify what support needs to confirm rather than ask the image to establish ownership and payment at once.

Use accessible structure

Short labelled fields can work well: action attempted, displayed result, expected result and question. W3C writing guidance supports clear instructions and meaningful alternatives to images. Do not turn the report into a large form if the case needs only three facts. The format should reduce effort for the customer and the next authorised agent.

Add layout evidence when it matters

If a button is hidden or two fields appear under an unexpected heading, a redacted image may add information text alone does not convey. Keep the relevant labels visible and remove credentials, complete connection links and unrelated notifications. The typed caption remains useful to someone using assistive technology and to a colleague searching the case later.

Preserve a focused result

When the provider answers, record the confirmed account fact and any remaining display question. Keep the original observation linked to the answer without spreading secret-bearing attachments. Text evidence is not automatically stronger than an image; it is another way to preserve the useful fact. Selecting it deliberately can make an account case easier to understand while exposing less private material.

For a multi-step case, label each observation with the action that preceded it. A single list of error phrases without sequence can be hard to interpret. Keep the record short enough to follow and preserve the exact wording where useful. The next agent can then distinguish a new observation from a repeated report of the same screen.

Questions about this guide