When your content references a user interface (UI), consider whether you
need to include screenshots. Screenshots can be helpful when text alone
cannot adequately convey instructions, and users like screenshots and
find them useful. However, screenshots are difficult and time-consuming
to maintain, and present translation problems. Therefore, you should minimize
the use of screenshots within your content.

As an alternative to screenshots, use the correct names of the UI labels
with which the user must interact and the values that they must choose
or enter. Show the names of buttons, options, check boxes, menus,
windows, dialog boxes, and so on as they appear on the UI. For example,
for straightforward instructions like, "To open a file, select File >
Open," a screenshot is not required.

If you include a screenshot in a procedure, place it directly under the
step that it illustrates. Do not rely on the screenshot to show
information or values that the user must enter; always provide that
information in the text of the steps. However, ensure that the
screenshot accurately reflects the directions and values in the step
text.