Techniques for WCAG 2.0

On this page:

-

# G98: Providing the ability for the user to review and correct answers before submitting

## Applicability

Sites that collect data from users that is specific to the moment it is submitted, such as test data, and cannot be changed once it is submitted.

This technique relates to:

- Success Criterion 3.3.4 (Error Prevention (Legal, Financial, Data))
  - How to Meet 3.3.4 (Error Prevention (Legal, Financial, Data))
  - Understanding Success Criterion 3.3.4 (Error Prevention (Legal, Financial, Data))
- Success Criterion 3.3.6 (Error Prevention (All))
  - How to Meet 3.3.6 (Error Prevention (All))
  - Understanding Success Criterion 3.3.6 (Error Prevention (All))

## Description

The objective of this technique is to provide users with a way to ensure their input is correct before completing an irreversible transaction. Testing, financial, and legal applications permit transactions to occur which cannot be "undone". It is therefore important that there be no errors in the data submission, as the user will not have the opportunity to correct the error once the transaction has been committed.

On a simple, 1-page form this is easy because the user can review the form before submitting. On a form that spans multiple Web pages, however, data is collected from the user in multiple steps before the transaction is committed. The user may not recall all of the data that was entered in previous steps before the step which commits the transaction.

One approach is to cache the results of each individual step and allow the user to navigate back and forth at will to review all data entered. Another approach is to provide a summary of all data collected in all steps for the user to review prior to the final commitment of the transaction.

Before the final step that commits the transaction to occur, instructions are provided to prompt the user to review the data entered and confirm. Once the user confirms, the transaction is completed.

## Examples

- An online banking application provides multiple steps to complete a transfer of funds between accounts as follows:

  1. Select "transfer from" account

  2. Select "transfer to" account

  3. Enter transfer amount

- A summary of the transaction is provided showing the from and to accounts and the transfer amount. The user can select a button to either complete the transaction or cancel it.

- A testing application provides multiple pages of questions. At any time, the user can choose to return to previously completed sections to review and change answers. A final page is displayed providing buttons to either submit the test answers or review answers.

## Related Techniques

- G155: Providing a checkbox in addition to a submit button
- G168: Requesting confirmation to continue with selected action
- SCR18: Providing client-side validation and alert

## Tests

### Procedure

In a testing application or one that causes financial or legal transactions to occur and that also collects data from users in multiple steps:

1. Determine if the user is allowed to return to previous steps to review and change data.

2. Determine if a summary of all data input by the user is provided before the transaction is committed and a method is provided to correct errors if necessary.

### Expected Results

- Either #1 or #2 is true.

- Top
- Contents
- Intro
- Previous: Technique G97
- Next: Technique G99