Secondary and text buttons carry parallel and exit actions

What it is

A secondary button and a text button (tertiary) hold lawful actions that are not the recommended path. Secondary treatments—outline or light fill—host a parallel option that should remain available but not win: save draft versus publish, maybe later versus subscribe now. Text buttons carry almost no mass and host exit or downgrade moves: cancel, skip, see details. They are not faded copies of the primary. They play different roles in the task: one keeps an alternative forward path, the other provides a way out of the recommendation.

Why it happens

People read a control’s visual mass as strength of commitment. A filled block feels like a door being pushed open; an outline still looks like a door; plain text reads more like a sidenote. Filling Cancel tells the motor system it is as worth lunging toward as Submit. Setting a real alternative path in plain text lets it vanish from the scan, leaving only the primary visible. The split is about action role. A parallel action must still be found as a button without winning the competition; an exit must be findable without becoming the default under time pressure. Outline preserves a clickable boundary; text drops visual mass until the label is read, which matches cancel and skip as deliberately deprioritized choices.

Studying it

Use a speeded forced choice (“leave now, pick a control”) and an untimed browse (can cancel or skip still be found). Compare encoding exit as filled, outlined, or plain text.

Independent variables: visual role of exit versus parallel actions, size relative to the primary, proximity to the primary. Dependent variables: accidental exits, abandonments when exit cannot be found, hesitation, and whether people call Cancel “the main button” in talk-alouds.

Keep “visible” separate from “read as recommended.” A text button that is seen but not chosen in a speeded task is often the intended result. Count it as a discoverability failure only when someone who intends to cancel still cannot find it.

Where it stops holding

A toolbar of outlined icon controls is a set of parallel tools, not a secondary-button family; nothing is “exiting a main path.” On a mobile sticky bar with only two actions, a text Cancel may be too weak for a thumb; use an outline secondary, still without primary fill. “Learn more” as a text button is the wrong role if that step is actually the gateway to conversion—promote it. Screen-reader users do not take role from fill; name and order have to carry the distinction as well.

Applying it

• Tag every action as recommended-forward, parallel-alternative, or leave/downgrade; map those roles onto filled, outlined, and text treatments.
• Put cancel, skip, and back on text buttons; put save-draft and alternative methods on secondary buttons.
• Do not give an exit the same mass and fill as the primary, even when the law requires it to appear.
• Verify with a timed “finish as fast as you can” task and a contrast task “I changed my mind, leave.” The first should not hit exit; the second should find exit within three seconds without describing it as the main action.

Related

• Within the group: E1.01.1 A view should contain only one primary button · E1.01.3 Hierarchy is carried by visual weight rather than position · E1.01.4 Several equal-weight buttons erase the recommended path
• Adjacent: E1.06 Button labels · E1.10 Button order · H3.04 Undo over confirmation
• Search terms: secondary button · tertiary button · text button