What Is Iconography?
Learn how icons form a visual language, and how meaning, labels, metaphors, visual rules, controls, access, testing, rights, and ownership keep the set clear.

Iconography is the use of visual symbols and the rules that give them meaning. In a brand or product, the word can also mean the full set of icons and the system that keeps them clear.
An icon may stand for an action, object, file, place, status, or idea. A familiar symbol can help people scan. An unclear one can slow them down or send them to the wrong place.
Put It in Plain Words
A magnifying glass often means search. A tray may mean an inbox. A question mark may point to help.
The shape alone is not enough. Its label, place, code, state, and past use all shape what people think it means.
Icons are not a universal language. The same mark can mean different things across tools, places, age groups, and cultures.
Start With Meaning, Not Style
Write the action or idea before drawing the icon. "Search the site" is a clearer brief than "make a clever magnifying-glass icon."
Use a known symbol when it fits the task and the setting. A new metaphor asks people to learn a new rule. That may be worth it for a distinct brand feature, but it needs a strong reason and a test.
Do not use one symbol for two jobs in the same product. A magnifying glass should not mean search in one place and zoom in another. If two icons look alike, their actions should not surprise the user.
GOV.UK's images and icons guidance warns that one icon can hold several meanings. It recommends visible labels in most cases and says a single icon should not stand for more than one thing.
Labels Are Part of the System
An icon and its label work as one unit. The label can remove doubt, help people scan, and make a risky action clear.
Use text when the meaning is not certain. Keep text for actions such as Delete, Pay, Send, or Cancel when a wrong choice would matter. A bin icon may be known to some people, but the word "Delete" states the result.
A label can be visible, available to assistive tools, or both. The choice depends on the icon's job:
A decorative icon can be hidden from assistive tools.
An icon beside a full visible label may not need a second spoken name.
A stand-alone icon button needs a clear accessible name.
An image used as a link needs text that states the target or action.
W3C's guide to functional images says the text alternative should state the action, not merely describe the picture. "Print this page" is more useful than "printer icon."
Build a Visual Family
Once the meanings are clear, define the parts that make the set feel related:
Grid and base sizes.
Stroke or fill logic.
Line weight and corner style.
Key shapes and safe area.
Detail level at each size.
Optical balance, not just exact math.
Light, dark, and high-contrast use.
Motion rules when icons move.
Adobe Spectrum's icon guidance uses shared shapes, stroke weight, spacing, and clear metaphors to form one family. It also notes that icons which try to say too much can become busy and fail at small sizes.
Do not scale one file down and assume it still works. A 16-pixel icon may need fewer lines and wider gaps than a larger version. Check the true size on the real screen.
Design the Full Control, Not Only the Glyph
An icon in a product is often part of a button, link, menu item, field, or status. The control needs a real role, name, focus state, hit area, and response.
Show the state through the whole control. That may include rest, hover, focus, pressed, selected, busy, and disabled. The icon can support the change, but it should not carry every state by itself.
The W3C button pattern separates a button from a link and explains names, keyboard use, toggle state, and focus. It also says that a control's look and role should match what it does.
This matters when a link is styled like a button or an icon is placed inside a clickable box. The code and the visual cue should tell the same story.
Test Meaning Before Polish
Show the icon in its real setting, not as a clean grid with no labels or nearby content. Ask people what they think it means and what they expect to happen.
A small test can record:
Icon name and intended meaning.
The screen, task, and nearby labels.
The answer each person gives.
Their confidence and first expected action.
Errors, delays, and labels that helped.
The fix and a second test.
Test likely users, languages, and places when those factors matter. Include new users as well as people who know the product. A symbol can feel obvious to the design team because they have seen it for months.
Also test at true size, 200% zoom, light and dark themes, keyboard focus, and with a screen reader when the icon is interactive.
A Hypothetical Support-Portal Example
In this hypothetical example, a support portal uses a magnifying glass with the visible label "Search." A tray appears beside "Inbox," and a question mark appears beside "Help." The icons share one grid, weight, corner style, and size.
The Delete action keeps its word label. It uses a clear button, focus state, and confirmation step. The team does not replace the word with an unlabeled bin merely to make the toolbar look clean.
During testing, one icon that was meant to show "Archive" is read as "Download." The team changes the metaphor and keeps the label. That result is more useful than defending the drawing because it fits the style.
Keep a Record and Change Path
Each icon should have a name, meaning, label, owner, and status. Record the metaphor, audience, grid, sizes, states, code part, source, license, version, and test notes.
Keep the source rights with the file. A public icon set may still require credit, a notice, or limits on how the work can be changed. A logo or brand mark may have separate rules.
When an icon changes, note which product parts use it. Retire old assets so that two forms do not drift through the system. If the old meaning changes, plan the release and test the transition.
Icon vs. Illustration
An icon is a compact symbol for one action, object, state, or idea. An illustration is usually a richer image used to explain, tell a story, set a mood, or add context.
A pictogram can sit between them. The name matters less than the job. Decide from the size, detail, label, interaction, and access need.
Common Mistakes
Drawing a new symbol when a known one works.
Removing labels only to make the page look clean.
Mixing filled, outline, and line weights with no rule.
Scaling one asset to every size without review.
Styling a link like a button while keeping the wrong code role.
Using a licensed or brand icon outside its terms.
Frequently Asked Questions
Are icons a universal language?
No. Some symbols are common in a given setting, but meaning changes with culture, product, age, ability, and past use. Test and label when doubt matters.
Should every icon have alt text?
No. A decorative icon can be hidden from assistive tools. A stand-alone control or meaningful image needs a name or text that fits its actual job.
Can iconography be part of a brand?
Yes. Shape, weight, motion, metaphor, and use can support a distinct visual system. Brand style should not make a key symbol hard to know or use.
Use Visual Identity vs. Brand Identity for the wider visual language and What Is a Design System? for product governance.
Need an icon system with clear meaning, labels, visual rules, real states, access checks, rights, and owners?
Book a free Brand and Tech Assessment to map the current problem, evidence, constraints, and practical next step.







