Common mismatches
Where a component and its content do not match, with examples
When a component means one thing and its content says another, users get a mixed message.
This can happen in 3 ways. The component can draw too much or too little attention for what is at stake. It can mean something the content does not back up. Or it can be used so inconsistently across a service that it stops meaning anything, or its labels disagree with what it holds.
| Mismatch | Where to check |
|---|---|
| Too loud and too quiet | How much attention it draws |
| Means the wrong thing | What a component means |
| Means too many things and labels do not match | Across your service |
The examples are made up, but each one is based on something we have seen more than once.
Too loud
A component draws more attention than the content needs.
An important banner carries routine news about phone line hours. On a contact page, that would be useful. On a claim page, missing it is minor, but the banner stands out more than anything else on the page.
Use instead: put routine news where it is relevant, such as the contact page, or leave it out.
What it costs the user: a moment of alarm, and less trust in the next banner they see.
Too quiet
A component draws less attention than the content needs.
We all want pages to look clean, so hiding content is a natural instinct. Every user needs to send these documents, but the list is inside details. Details tells users they can skip what is inside, so some will.
Inset text shows an error and how to fix it. Users can read straight past it, and screen readers do not announce it as an error.
Use instead: show content every user needs on the page itself. For errors, use an error summary and error message.
What it costs the user: they miss something they needed, and putting it right later costs them time, anxiety or money.
Means the wrong thing
The component means something the content does not back up.
Warning text means "There is a risk I need to act on". This is an eligibility decision, and the user has nothing to act on.
An important banner means "Something has changed that affects me". This one holds 2 different things: an estimate of what the user could get, and the status of their application. The banner can only mean one thing, so users misread at least one of them.
Use instead: a component that means what the content says. For an eligibility decision, use the results page from check a service is suitable.
What it costs the user: they misread what the content is, and may act on it.
Means too many things
One component is used for so many kinds of content that users stop seeing it as meaning anything.
On one page, inset text holds reassurance, an explanation of why a question is asked, and a link.
Use instead: put reassurance and purpose in the page text or hint text. Keep inset text for one kind of content across the service.
What it costs the user: they cannot tell which inset text matters, so they start to skip all of it.
Labels do not match
A component's heading, labels or actions contradict what it holds. This mismatch is easy to make with components that get their meaning from their parts.
A timeline headed "Address changes" lists a claim, an identity check and a decision. None of them is an address change.
One row says "Married" and the next says "Partner: No". Both can be true, because "Partner" here means a partner the user lives with. The label does not say so, so the user cannot tell which row to believe.
Use instead: give the component a heading that matches what it holds, and give each label enough detail to say what it means, such as "Partner living with you".
What it costs the user: they misread the record, and may change something that was right.
Something missing or does not belong here?
Tell us what you have found when choosing components, or anything this guidance does not cover. Let us know.