When to use
- Representing a user profile in collaboration features such as messaging, sharing, or comments.
- Providing a visual cue for accounts, teams, or organizations in collaborative interfaces.
- Signaling concepts or features such as an agent avatar.
When to use something else
- Decorative visuals for onboarding or Empty states: Use an illustration asset or icon instead of an Avatar.
Dos and don’ts
- Do size Avatars based on the context they are used in, i.e. use a Small Avatar when paired next to a Small Button.
- Do randomize colors when using the icon or initial icon types.
- Do mix image types with icon or initial types as needed.
- Don’t rely only on Avatars when a name is more useful for the context.
Behavior
- When space limits, use an overflow avatar with a dropdown Menu to indicate there are more users hidden.
- Avatars can be view-only or interactive, depending on the context.
- Avatars can display badge dots to indicate status or online presence.
Often used with
Badge (status dot), Tooltip (name or details), Menu for “+N” overflow stacks in collaborator lists.Accessibility
- Image alt text: Provide descriptive alt text (e.g.,
alt="Sarah Connor") when the avatar stands alone. Usealt=""andaria-hidden="true"if accompanied by visible adjacent text labels. - Fallback accessibility: Render plain text fallback initials inside the DOM with verified 4.5:1 contrast against the background container when images fail to load.