Design Principles
Norman: Signifiers
Signifiers are the visible cues that tell users where and how an action can be taken.
Where it comes from
Don Norman introduced the term to fix a confusion in his own earlier work. Having popularised 'affordances', he found designers using the word for what he really meant by signifiers — the perceptible signals that reveal where and how to act.
Why it matters for your website
Affordances are what's possible; signifiers are how users find out. Norman draws the distinction sharply: a thing can be clickable, swipeable, or draggable, but unless a visible cue says so, users won't know. Hidden interactions with no signifier are invisible interactions — and invisible interactions don't get used.
A signifier is the advertisement for an action. A swipe, a long-press, a drag may all be possible, but without a visible cue announcing them, they may as well not exist — undiscovered interactions don't get used. The richer and more gestural an interface, the more it depends on signifiers to be discoverable.
This is why minimalist, 'clean' interfaces can quietly fail: in stripping away visual cues, they often strip away the signifiers that told users what they could do. Flat designs that remove button edges, underlines, and affordance hints trade discoverability for tidiness.
Wrong vs right
A gallery that's swipeable but shows no dots, arrows, or peek of the next image — users never learn they can swipe.
Visible cues — pagination dots, a partial next slide, an arrow — that signify the swipe is available.
A flat 'button' with no border or fill, indistinguishable from text, so its tappability is hidden.
A clear signifier of interactivity — a button shape, an underline, a colour convention — that announces the action.
A hidden long-press menu with no indication it exists, so only power users ever find it.
A visible affordance cue or hint that the long-press action is there to be discovered.
Understanding Norman: Signifiers
Signifiers are the perceptible cues that tell users where an action is possible and how to perform it. Norman drew the distinction from affordances deliberately: an affordance is what an object can do, while a signifier is the signal that communicates it. The two are easily confused, but the design lesson lives in the signifier — because an affordance no one can perceive does the user no good.
On screen, every interaction needs a signifier to be discoverable. A link needs to look like a link, a draggable element needs a handle, a swipeable carousel needs dots or a peeking next slide. The interaction can be technically present, but if nothing announces it, users won't find it — and an undiscovered feature is, functionally, no feature at all.
This is the hidden cost of over-minimal design. Stripping away borders, underlines, and visual affordance cues in the name of cleanliness often strips away the signifiers that made the interface usable — leaving a tidy page whose actions are invisible. Good design makes possibilities perceptible. It connects to affordances, the law of similarity, and self-evident design.
How Kweri checks it
Kweri can catch some signifier failures it can observe — interactive elements with no visual cue of their interactivity, or gestural interactions (swipe, drag) presented with no on-screen hint. What it can't fully assess is whether a given cue is *discoverable enough* for your users, which depends on their familiarity and the context. So Kweri flags likely cases where an action lacks a visible signifier, and prompts you to make interactions perceptible, while the finer discoverability calls come from watching real users try to find them.
FAQ
What is a signifier in design?
A signifier is a perceptible cue that tells users where and how an action can be taken — an underline signifying a link, a handle signifying something draggable. Norman coined it to distinguish the signal of an action from the action's mere possibility (the affordance).
What's the difference between affordances and signifiers?
An affordance is what an object makes possible; a signifier is the visible cue that communicates it. An element can be clickable or swipeable (the affordance), but unless a signifier announces it, users won't know — so the signifier is what makes it usable.
Why are hidden interactions a problem?
Because an interaction with no signifier is effectively invisible. A swipe, long-press, or drag that nothing announces will only be found by accident, so most users never use it. Discoverability depends on perceptible cues.
Can minimalist design hurt usability?
It can, when it removes signifiers along with clutter. Stripping borders, underlines, and affordance cues for a cleaner look often hides what users can do, trading discoverability for tidiness. Minimalism has to preserve the cues that communicate function.
How do I add signifiers to an interface?
Make actions perceptible: style interactive elements distinctly, add handles to draggable items, show dots or arrows for swipeable content, and use hints for gestural interactions. Every possible action should have a visible cue announcing it.
Related principles
An element's appearance should signal how to use it — buttons should look clickable, links like links.
Always tell users what's happening, with clear feedback delivered in good time.
Users follow the strongest-smelling trail toward their goal — they click links whose labels and context suggest the destination will be relevant, and abandon paths that go cold.
Attribution & sources
Identified by Don Norman. Catalogued from Don Norman — Signifiers, Not Affordances (jnd.org).
Norman's refinement of the affordance concept; the linked article is the primary source.
See Norman: Signifiers on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →