Call to Action

Examples include buttons or links for purchasing, contacting, registering, downloading or starting a task. Clear labels should describe the action rather than rely only on decoration. In practical terms, Call to Action belongs to the structure and interaction layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use Call to Action as if it also meant Affordance. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Make the action specific and place it where the visitor has enough context to decide, rather than repeating generic buttons everywhere.

In day-to-day work, Call to Action matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

“Request a quote” is a CTA when it clearly presents the next action after someone understands the service. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.