A button and its context form the sentence together

What it is

Button-context compositional meaning means a label combines with an adjacent heading, object name, current selection, description, and state to express the complete action. “Archive” in a list row can take its object from that row's title. The design unit is the action area rather than an isolated string, but critical meaning must not rely on a cue that can collapse, scroll away, update, or be found only as “above” or “to the right.”

Why it happens

Composition reduces repetition and keeps controls scannable: a stable heading supplies the object, a selection summary the quantity, and the button the action. The sentence breaks when elements are no longer perceived together—a responsive layout moves the heading, a screen-reader button list bypasses visual context, validation changes the selection, or scrolling removes the object from view. Screen position is not a dependable semantic relation because layout, reading direction, and zoom change it. Programmatic association, persistent object information, and a self-sufficient accessible name preserve the composition across presentations.

Studying it

Test the action area across real states: single and bulk selection, empty selection, scrolling, narrow screens, zoom, translation expansion, asynchronous updates, and screen-reader control navigation. Ask participants to restate action, object, scope, and result, then identify whether their evidence remains perceivable. Compare object repetition in the label, an adjacent summary, and the accessible name, balancing scanning burden against wrong-target actions. Do not validate only the default desktop mockup.

Where it stops holding

Adjacent context may carry information that the button does not repeat. Critical consequences such as payment, authorization, irreversibility, or hidden side effects must remain visible before activation, be programmatically associated with the button, and be available to assistive technology; they cannot depend on cues that collapse, scroll away, or exist only through visual position. Icon buttons still need accessible names, and a tooltip cannot be the only name. A table row may supply an object for a row action, but moving the control into a bulk toolbar requires a new selection scope. High-risk confirmation rules additionally state the specific object and consequence; compositional semantics asks whether the elements together form an understandable action.

Applying it

• Draft the full semantics first: “[action] [object or selection], producing [result].” Distribute it across heading, summary, description, and button, marking which parts must remain visible.
• Bind the button structurally and programmatically to its heading, description, row, or selection summary. Its accessible name should still distinguish action and object outside visual position.
• Protect scrolling, collapse, responsive reflow, dynamic refresh, and error states. If the key object disappears, let the label or persistent summary take over; synchronize selection changes.
• Run context-removal and assistive-technology tests. If hiding any fragile element makes the action ambiguous, move critical meaning into the button or a persistent adjacent region.

Related

• Same group: T2.01.1 Button text should describe the specific action that will happen · T2.01.2 Generic words prevent users from predicting outcomes · T2.01.4 Confirm and cancel wording must be opposed and clear
• Adjacent: T1.02.3 Verbs must be specific enough to judge consequences · T2.06.1 State the specific object and irreversibility scope
• Search terms: button context · accessible name · selection summary