Skip to main content

Solutions

Products

Recommended products

Questions? We are here to help.
Contact us

Purchase

Questions? We are here to help.

Resources

Content guidelines for Help and Support

Screenshots

Screenshots can be a great visual aid for sighted people to understand what the written instructions are conveying.
Key considerations:
  • Use only the area of the screen necessary. Some screenshots don't need the entire window captured, which can lead to unnecessary real estate and a larger cognitive load in determining what in the screenshot is relevant to the end-user.
  • Resize and compress large images to optimize storage.
  • Don't just add an image to have an image. If it helps an end-user accomplish their task, that's good!

Adding markup to screenshots

To call attention to a particular part of a screenshot, use the following guidelines:
  • Use a red box with corners that are not rounded.
  • The box thickness should be set to 3 with 100% opacity.
  • The box should have a drop shadow set to the bottom middle.
  • Don't use yellow or any color highlighting.
  • Don't use numbering stamps on the screenshot.
  • Don't use arrows to point to things in the screenshot.

Providing screenshots to use in articles

When providing screenshots, attach the original image file to the ADO ticket (aka "Content Request").
Image files provided in a Word doc or PDF file to us lose image quality and become grainy or fuzzy when they are made available on Help and Support.
Provide the image in an appropriate size. We are unable to resize images.
Give the file a descriptive name, using 50 characters or less (not including the file extension). Don't use "image-1" as name - instead, use something like "import-wizard-step-1".

This article applies to:

Related Content