# Position actions at decision moments

ID: cmp-contextual-action. Sources: [S06](https://design.google/library/expressive-material-design-google-research), [S24](https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html).

Teach actions as a reasonable next step with accurate labels and destinations. Placement and nearby evidence can provide emphasis. Use supported inquiry, call, visit, detail, or real booking behavior.

Application A: a service scope ends with an inquiry carrying the relevant service choice. Application B: a visit page keeps contact options beside hours and location.

Counterexample: repeated action pairs interrupt every paragraph; a sticky button hides the facts needed to decide. An inquiry must not promise confirmed scheduling.

Mobile: test target spacing, focus, and overlap. Preserve explicit project preferences while labeling accessibility authority accurately.

Storyboard: reuse action fields; add a located observation for significant placement decisions. Review: locate, understand, and execute the action. Distinguish mocked local success from a live integration outcome.

## Authority and use

This is an original design-teaching hypothesis. It is advisory and does not change factual, accessibility, or functional requirements. Adapt it to verified business evidence and inspect the current render before accepting an outcome. The applications above are contrasting examples, not copyable site presets.
