Use the following guidelines to determine when and how to use screenshots:
What to do
Use a screenshot to illustrate a complex task. The screenshot can alleviate the need for long and confusing steps.
Use icon images within procedures, so users can see exactly what to click in the UI.
Consider including navigational screenshots in end user content to provide context and help to orient the user. For example, at the beginning of a chapter about the chat feature, add a screenshot showing the chat module in the UI. Including a screenshot at the beginning of a chapter or section might also reduce the need for screenshots within procedures.
Add accessibility or alt text for each screenshot and for icon images without a name. When you update an image, you might also need to revise the associated alt text.
What to avoid
Do not use screenshots for simple steps. The user usually has the application open, so screenshots for straightforward steps do not add value.
Do not use screenshots to repeat the text in a step. Use text to explain the tasks that the user performs and the purpose of these tasks.
Do not use screenshots for aesthetic purposes. For example, do not use screenshots to break up long passages.
