Use a summary:

• when you need to show a list of instructions, tasks or benefits

Don't use a summaryr:

• if you need to give users positive or negative instructions (use instruction instead)

Adding a status is optional. There are 3 status types you can add.

• Keep the same structure for all the summaries in a list — start all titles with verbs, or all with nouns, but don’t mix and match.

• Don't use more than 6 summaries in a list — any more and it gets hard to scan and difficult to take in information.
• Don’t use the info button for critical information as users might not click on it.
• Don't use an info button for too many items in a list — try to stick to one per list at the most.

• Use a status when you need to show the user the status of an action.
• Use a description if you need to expand on the information in the title, and surface important information on the screen.
• Include an action if you need to redirect the user to a related, secondary task — for example, to give the user an opportunity to amend a previous action, like editing an address they’ve already confirmed.

The only interactive parts of the summary are the info button and the action.

Be mindful of how frequently you use the info button — too many info buttons add visual noise to the screen, increasing the cognitive load.

You can use an optional status to indicate the state of items that require action — this will add an appropriate aria label for screenreader users, and for some statuses, an icon.

If you do choose to use a status, don't rely on the aria label or icon alone to communicate it. Make sure this information is clear from the title, too. For example:

• 'Verify your address' would match a not done status

• 'We’re verifying your address' would match a pending status

• 'Your address is verified' would match a done status

Statuses are optional as not all summary items are actionable — but if you use a status for one item, you should use a status for all items.