Check answers
Let users check their answers before submitting information to your service.
When to use this pattern
Use this pattern at the end of a multi-step form or application process. It allows users to:
- review all their answers in one place
- spot and correct any mistakes
- feel confident before submitting
How it works
Use the summary list component to display a list of questions and answers. Each row should have a "Change" link that takes users back to that question.
Example check answers page
Check your answers before submitting
Personal details
Contact details
Now submit your application
By submitting this application you confirm that the information you have provided is correct.
Grouping answers
If you have multiple sections in your form, group the answers under subheadings. This makes it easier for users to scan the page.
Change links
- Every answer should have a "Change" link
- The link should go directly to that question
- After changing, users should return to the check answers page
- Include visually hidden text for screen readers (e.g., "Change name")
Formatting answers
- Display dates in the format "15 March 1990"
- Display addresses with line breaks
- Display phone numbers as entered
- For boolean answers, use "Yes" or "No"
- For empty optional fields, show "Not provided" or similar
Submit button
Place the submit button at the bottom of the page. Use clear action text like:
- "Accept and submit"
- "Submit application"
- "Confirm and send"
Legal declarations
If users need to agree to a declaration, show it above the submit button:
Declaration
By submitting this application, I confirm that:
- the information I have provided is true and correct
- I understand that providing false information is an offence
Accessibility
- Use
<dl>,<dt>, and<dd>for semantic meaning - Include visually hidden text in Change links for context
- Ensure the page has a clear heading
- Group related information under subheadings