esc
  • WorkflowsPages
  • Case studiesPages
  • Machine Learning FoundationsLearn
  • AI EngineeringLearn
  • AI Guardrails & Red TeamingLearn
  • UI/UXLearn
  • Design SystemsLearn
  • Production System DesignLearn
  • Book a callContact
  • Download ResumeContact
Let’s talk

I’ll build the agent for it.

Avatar: The Shared Person Picture That Stays Readable When Photos Are Missing

How a design system defines avatars: photo, initials, or icon, fixed sizes, fallback rules, and accessible labels.

In short

An avatar is a shared person picture in a design system, shown as a photo, initials or an icon, with fixed sizes, fallback rules and accessible labels.

12 min readFree

What you will learn

Almost every app shows people as small pictures or letters beside their names. In a design system, that small picture is a shared part called an avatar. This lesson explains what goes inside an avatar, what it shows when a photo is missing, how to keep its text readable, and how to make it work for people who use screen readers.

Key words

Avatar
A small visual that stands for a person, a team, or an organization.
Design system
A shared set of parts and rules that a product team reuses across its screens.
Fallback
The backup content shown when the first choice is missing or fails to load.
Initials
The first letters of a name, such as the letters for a first name and a last name.
Presence indicator
A small dot that shows whether a person is active, away, or not online.
Stack
Several avatars placed in an overlapping row, often with a count such as +3 for the ones that do not fit.
Alt text
A short written description of an image. Screen readers read it aloud.
Screen reader
Software that reads the content of a screen out loud for people who cannot see it well.
Contrast
How clearly text stands out from the color behind it.

By the end, you should be able to choose the right content for an avatar, write the fallback rules, and explain when a screen reader should skip the picture.

What is an avatar made of?

At its simplest, an avatar is a container with content inside it. The container is a shape, and the content is the picture, letters, or symbol that fills it. A design system defines this once, so every screen that shows a person uses the same parts instead of a new one each time. The Uber design system describes the same basic idea: a circle container with either a photo or a fallback inside it.

The three content types

  • Photo

    The person's own picture. It is always the first choice when one exists.

  • Initials

    Letters taken from the name. The SAP design system makes initials the default when no photo is available.

  • Icon placeholder

    A generic symbol. It is used when neither a photo nor initials fit, such as for a system account or an anonymous user.

Shapes and the size scale

Most systems use a circle for people. SAP, for example, says to use a circle for people and a square for product or business images. Sizes should come from a fixed list, not from any number a designer likes. The lists differ, but both systems stop designers from stretching an avatar to a random size. A size scale is a named list of allowed sizes, such as small, medium, and large.

Optional extras

  • Status indicator

    A small dot in one corner. It shows whether the person is active or away. Slack places its dot in the lower-right corner of the photo.

  • Group or stack

    Several avatars placed in an overlapping row. Designers use it when a team, a project, or a list of people needs one compact spot on screen.

  • Border or ring

    A thin outline that separates the avatar from a busy background. It is optional and should follow the system's shape rules.

Tip

Do not make extras mandatory. Add a status dot only where the reader needs to know presence, such as in a chat. Good avatars often have no dot at all.

What should you show when content is missing?

A fallback is the backup the avatar shows when its first choice cannot appear. This is the hardest part of avatar design, because many people will not have a photo. The SetProduct guide puts it plainly: an avatar without an image should show initials or a placeholder. A blank circle breaks the layout and tells the reader nothing about who it is.

When the photo is missing or fails

Two situations need a fallback. The first is when no image was added. The second is when the image link is broken or the picture will not load. In both cases the avatar should show initials, an icon, or a neutral placeholder. Keep the same size and shape while it does this. A DEV Community article on profile avatars warns that a fallback which changes size can make a list jump when a photo loads or fails, so the same shape is the safer choice.

How initials are built

  1. 1

    Find the first word of the name

    ActiveCampaign's system takes the first character of the first word in the name. Middle names are skipped.

  2. 2

    Find the last word of the name

    The same system takes the first character of the last word. For a family name, that is the last word in the list.

  3. 3

    Put the two letters together

    Write them as capital letters, one after the other. Use the letter only, not the whole word.

  4. 4

    Stop at two characters

    This keeps the text readable inside a small circle.

  5. 5

    Switch to an icon for a one-word name

    If a name has only one word, initials will not identify the person well. ActiveCampaign's system shows an icon instead in that case.

Tip

Initials can be unclear across languages and cultures. SAP warns that initials may be ambiguous in multilingual settings, and it advises against them when they do not identify the person clearly. Test your rule with real names from your users.

Choosing background colors

Colors help readers tell generated avatars apart from real photos. The Design System Checklist adds that the avatar should be able to fall back to a different image, icon, or text when needed. Color should support the name, not carry the whole meaning. The DEV article makes this point: keep the name visible beside the avatar, and treat color as a secondary cue.

Choose background colors from a set palette, and check the letters against each background. If the text is hard to read, the system's color pair fails, even when the color looks pretty.

Quick check

A new teammate has no profile photo. Their name is Maria del Carmen Lopez Garcia. Your design system's avatar is a 40px circle. What should it show, and which rule decides that?

Where do avatars appear, and how do you make them accessible?

Avatars show up in many places. Each place needs its own size, and the design system should say which size to use there. Small sizes suit dense lists, where many people appear in a short space. Larger sizes suit profile headers and menus, where the picture should be easy to see. The SAP guidance uses the same idea, giving different sizes for app headers, menus, and cards.

  • Comments

    A small avatar beside each reply, so the reader sees who wrote it at a glance.

  • Lists

    A compact avatar in each row, such as a list of team members or pending requests.

  • Profile menus

    A clear avatar at the top of a menu, showing which account is signed in.

  • Tables

    A small avatar inside a cell, so an owner or assignee is easy to spot next to a name.

Alt text and screen readers

Alt text is a short text description that a screen reader can read aloud. The New York State design system says to give initial avatars the person's full name as alt text, but only if the name is not already shown beside the avatar. A stand-alone photo with no name next to it needs a real description, such as the person's name.

When a name is already written next to the avatar, the picture is repeating the same information. The GitLab system says the image should then use an empty alt value, so a screen reader skips it. Its guidance is that the image should be ignored by assistive technology. The 21st.dev guide says the same thing in plain words: an avatar beside the name should get an empty alt, not the name again. Otherwise the reader hears the name twice.

Tip

Never use generic words such as avatar or user photo as alt text. The Fragments system says alt text should describe the person, not the picture. If the avatar is a stand-alone identity, the name belongs in the alt text.

Contrast for initials

Initials are text, so they need enough contrast against their background. The New York State system asks teams to meet the WCAG 2.1 contrast ratio for the text of initial avatars. WCAG is the widely used web accessibility guideline. The Create UI documentation says the same kind of check applies to generated avatars. The GitLab system adds that small text should aim for the WCAG AA level, which is the common target for most products.

Status dots need care too. The SetProduct guide says status indicators should have high contrast. A pale green dot on a pale background can disappear. Also avoid relying only on color.

Quick check

A comment thread shows each reply with a small avatar and the author's full name in bold beside it. A designer asks what the image's alt text should be. What is the right choice?

Worked example: a Slack-style profile and presence dot

This example walks through a Slack-style screen. It uses Slack to show a photo and a presence dot. The initials and the +3 stack show the pattern a design system would define for them. They are not a claim about exactly how Slack draws those states, so treat them as the system's rules at work.

  1. 1

    Show the photo when there is one

    Slack shows a person's photo as a small circle. In the design system, this is the first content choice: a real photo wins over everything else.

  2. 2

    Fall back to colored initials

    When no photo exists, the system switches to initials. It takes the first and last word of the name, uses a palette color behind the letters, and checks that the letters are easy to read.

  3. 3

    Add a presence dot in the corner

    Slack places its status icon in the lower-right corner of the photo. A solid green dot means active. A hollow dot means away. Slack sets away automatically after 10 minutes without activity on a desktop computer.

  4. 4

    Swap the dot for a call icon during a call

    When someone is in a huddle or a call, a small headphones icon appears over the photo in place of the usual dot. The system sets this as a rule, so every avatar in a call looks the same.

  5. 5

    Stack the team in a document header

    In a shared document header, show a few avatars overlapping in a row. Then add a count such as +3 for the people who do not fit. The count must be reachable, for example as a button that opens the full list or a tooltip that names the three people.

Tip

Presence is visual only. A screen reader will not announce the dot, so the screen should also state the status in text, such as a line that says the person is active. The Create UI guide says presence should be conveyed in text elsewhere for assistive technology.

Quick check

A shared document header shows five avatars in a stack. Three are hidden behind a +3 count. Your team's design rule says the count must be clear for everyone. A teammate proposes making +3 plain text that cannot be clicked. What should you do?

Common mistakes to avoid

  • Scaling avatars to any size

    Stretching a photo or making a one-off size breaks the shared scale. Use only the sizes the system lists.

  • Leaving the fallback empty

    A blank circle wastes space and gives no clue about who the person is.

  • Changing shape when the photo fails

    A fallback that is a different shape or size makes lists jump. Keep the same container.

  • Using too many letters

    Long initials become unreadable in small circles. Keep to two letters at most.

  • Using color alone for status

    A dot that only uses color can be missed by color-blind readers. Add a shape, such as a hollow dot, or a text label.

Tip

Before you finish an avatar, test it with a short name, a long name, a name with a middle name, and a missing photo. If all four look clear at your smallest size, the design is ready for the system.

Key takeaways

  • Define it once

    An avatar is a shared part with a fixed shape, fixed sizes, and clear content types: photo, initials, or icon.

  • Plan the fallback

    Write the rule for missing or broken photos, the initials method, and the color rule before you design screens.

  • Make it readable and labeled

    Check text contrast, avoid color-only meaning, and use alt text only when no visible name sits beside the picture.

Sources

How is this lesson?

Last updated on 17 November 2026

Learn with me

Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.