Skip to content
UX Atlas
Plate FND·018 · UI foundationGrid C2 · Rev. 2026-08-14

Emphasis

Making one thing stand out, which only works if most things do not.

UI foundationCraft conventionFoundational

Definition

Emphasis is the deliberate promotion of a single element above its surroundings. It depends entirely on contrast with a consistent baseline, which makes it a limited resource within any one view.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this plate
  1. 1Definition
  2. 2Emphasis techniques, quietest first
  3. 3Emphasis techniques and what each costs
  4. 4In practice
  5. 5Local chart
  6. 6Continue from here

Reach for this when

  • Designing any screen with a primary action.
  • Reviewing a screen where the main action is being missed.

Common mistakes

  • Emphasis inflation across releases as each feature is promoted.
  • Colour-only emphasis.
  • Emphasising the business goal rather than the user goal.
  • Emphasising what the business wants rather than what the reader is looking for, which teaches people to ignore emphasis.

Emphasis techniques, quietest first

  • Increased weight, which is precise and cheap.
  • Increased size.
  • A background tint, which creates a region as well as emphasis.
  • A solid fill in the accent colour, which is the strongest static treatment.
  • Isolation in whitespace, which is quiet and often the most elegant option.
  • Motion, which overrides everything and should be reserved for change.

Do

  • Emphasise the action that matches the user's most likely goal.
  • Combine two levers at most.
  • Keep the baseline quiet so emphasis has somewhere to stand out from.

Do not

  • Use colour alone, which fails WCAG 1.4.1.
  • Emphasise more than one element per view.
  • Use animation to emphasise something that is not changing.

Emphasis techniques and what each costs

TechniqueStrengthCost
Extra space around itModerateLayout space. Costs nothing else
WeightModerateWears out if used widely
SizeStrongSpace, and it unbalances a grid
ColourStrongFails alone for many readers, and in greyscale
A filled containerStrongImplies the thing is an object or a control
MotionStrongestAttention, accessibility, and it cannot be used twice

In practice

  1. i.

    Two primary buttons

    A very common failure

    Save and Publish both styled as primary forces the user to read and decide where the design should have told them. Making one secondary costs nothing and answers the question.

  2. ii.

    The second primary button

    A budget, spent twice

    Two filled buttons side by side make the reader choose between two things that both look like the answer. Demoting one to a quieter style is the entire fix, and it is usually resisted for reasons that have nothing to do with the reader.

Local chart

FND·018 · Region II · Grid C2

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applied through

Where this shows up as a concrete interface decision.

Principles behind this

The reasoning this solution is an application of.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.