When iconography is worth the effort

This is one of those topics that looks small until it costs you something. Iconography is not free, and pretending otherwise leads to bad decisions.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. Write the reasoning down alongside the decision, because the reasoning is what changes first.

When it is worth it

Icons without labels are guessed wrong more often than teams assume. The cost of getting this wrong is rarely visible on the day it happens. Doing this properly once is usually cheaper than doing it approximately three times.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. Where this goes wrong is almost never a lack of knowledge.

How to decide

Decorative icons should be hidden from screen readers. The reasoning matters more than the rule, because the rule has exceptions. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

How to tell if yours is fine

The measurable part of design is whether people can find what they came for and act on it without hesitating. Three things worth confirming about iconography before you move on:

• Someone can say what the current setup is without going to look
• Icons without labels are guessed wrong more often than teams assume — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.