Overview

A Call to action is a styled link that directs a user to other pages or sometimes displays hidden content.

Sample Elements

Call to action component sample

Demos

View a live version of this component and see how it can be customized.

View the <rh-cta> demo in a new tab

Usage

Call to action links are best used to entice a user to make a selection. For example, use the Primary variant to bring attention to an important link or use the Brick variant to group links together in a grid.

Hierarchy

Call to action links are ordered by hierarchy from left to right (large screens) or left to right and top to bottom (small screens). They can be used multiple times in the same container except for the Primary variants.

Call to action component usage, hierarchy

Even though they look similar, call to action links and buttons have important differences. Call to action links are navigational elements whereas buttons perform actions.

Learn more

Visit the Button component page to learn more about how to use buttons.

  • Call to action links are used in layouts (like the home page) whereas buttons are used in components (like a Form).
  • Call to action link text labels are larger and thicker than button text labels.
  • Call to action links with containers include more padding than buttons with containers.
  • Call to action link colors have different meanings than button colors.

Content

Call to action links are navigational elements, so any text needs to accurately communicate the destination. Inconsistent experiences might lead to distrust, lessening the satisfaction of a user during their journey. Call to action link text labels should be action-oriented yet straightforward so a user will feel comfortable making a selection.

Warning

Call to action link text labels need to be written clearly in order to be understood, therefore write no more than four or five words per link.

Call to action component usage, content

Character count

Call to action link text labels should have fewer characters in order for their message to remain impactful for a user.

Warning

Do not write long text labels because they might break to two lines on small screens or weaken an impactful message.

Style Maximum characters
Primary 30
Secondary 35
Brick 25
Default 45

Variant grouping

Variants can be grouped together if there are different kinds of links that need to be displayed in the same container.

Helpful tip

If there are more than three links that can be grouped together in a grid instead, use the Brick variants.

Warning

Do not group more than three Primary, Secondary, or Default variants together otherwise a user might have trouble making a selection.

Call to action component usage, variant groups

Buttons

Do not use a call to action link to trigger an action, like submitting a form or changing a state.

Learn More

Visit the Button or Form pages to learn more about how to use buttons and forms.

Call to action component usage, buttons

Brick (icon)

When grouping Brick (icon) variants, different icons can be used to communicate different topics, but they all must be the same style, color, and height.

Call to action component usage, Brick (icon) variant

Primary (white)

The Primary (white) variant can be used if the red variant conflicts with other elements or violates accessibility standards.

Best practices

Changing styles

Do not modify the styles of any variant for any reason.

Call to action component, best practice 1

Do not group more than three variants together otherwise a user might have trouble making a selection if there are too many link choices.

Call to action component, best practice 2

Using multiple Primary variants

Do not use multiple Primary variants in the same group, use of that variant is reserved to represent the most important link.

Call to action component, best practice 3

Mixing variant groups

Do not group more than two variants together anywhere.

Call to action component, best practice 4

Mixing Bricks

Do not group different Brick variants together anywhere, use one only.

Call to action component, best practice 5

Changing hierarchy

Do not change the hierarchy when grouping, variants that are higher in hierarchy should go first.

Warning

Do not change the hierarchy when grouping unless the change is to accommodate right-to-left languages.

Call to action component, best practice 6

Stretching

Do not stretch any other variants to fit a container or grid, only the Brick variants can stretch.

Call to action component, best practice 7
© 2021-2023 Red Hat, Inc. Deploys by Netlify