Screenshots Standard
Summary
This standard defines currency, sanitization, accessibility, and review requirements for screenshots.
Audience
- Documentation authors
- Documentation reviewers
Reference Content
Use screenshots only when visual orientation is necessary and prose cannot communicate the task efficiently.
- Capture the smallest relevant area at a readable resolution.
- Use approved test data and a neutral test environment.
- Remove or obscure personal data, credentials, tokens, tenant identifiers, URLs, notifications, and unrelated applications.
- Do not rely on a screenshot as the sole source of an instruction.
- Provide meaningful alternative text and a caption when context is needed.
- Avoid decorative borders, annotations, and compression that reduce readability.
- Record the source version or review context outside the image when currency matters.
- Revalidate screenshots after relevant interface changes and during the page review cycle.
A screenshot that cannot be safely sanitized must not be published.
Related Articles
See Also
Keywords
- Screenshots
- Image sanitization
- Alternative text
Revision Information
- Last reviewed: 2026-07-14
- Owner: documentation-team
- Status: Approved