The decision that matters
Decide what the reader needs from the screenshot. If nearby text already gives complete instructions, a short identification may be enough; if the image contains essential information, provide that information in text. Decorative images should not create unnecessary repetition for assistive technology. Avoid using file names as descriptions and do not hide critical instructions only inside an image.
A practical scenario
A screenshot showing the approved state of a document could use a description such as “Document review showing Approved and the reviewer’s name.” The surrounding paragraph should explain how to reach that state. A complex dashboard chart may need a longer adjacent explanation of the data, rather than an overlong alternative text string that attempts to narrate every label.
Before you ship
- Identify the image’s purpose before writing its description.
- Keep essential instructions available as text.
- Review decorative and informative images differently.
A useful next step
Hide the images temporarily and read the page in order. If the workflow still makes sense, the text is doing its job. If an important result disappears, add a concise explanation near the image and choose alternative text that complements it.
Primary reference & further reading
This guide combines general engineering recommendations with an illustrative scenario. Provider behavior can change; check current documentation before applying it. Read our editorial approach.