Web checklist

Checkpoint AA3.3.4: *WCAG 2.0 AA* Error Prevention (Legal, Financial, Data)

Web pages used for legal commitments, or financial transactions, that modify or delete user-controlled data in a storage system, or submit user test responses must 1) allow the user to reverse the submission, OR 2) be checked for input errors and provide the user with the ability to correct input before submission OR 3) allow the user to review, confirm and correct information before finalizing the submission.


Rationale

This checkpoint helps users avoid irreversible consequences that may occur when performing an action in a Web application, including submitting financial transactions that cannot be reversed, deleting data that the application cannot recover, and purchasing items from an online merchant. Because people with disabilities may be more likely to make mistakes when using applications like these, your application must enable the user to recover from unintended actions by implementing these techniques and examples.

Required development and unit test techniques


To comply with this checkpoint, you must meet at least one of the following techniques. These techniques are defined in WCAG 2.0 Level AA Success Criterion 3.3.4 (link resides outside of ibm.com).

  1. Forms involving legal transactions: Forms involving legal transactions, such as making a purchase or submitting an income tax return, your application must provide the following:

    1.1 A stated period of time after submission of a form when an order can be updated or canceled by the user.

    1.2 The ability for the user to review and correct answers before submitting a form.

    1.3 A checkbox in addition to a Submit button.

  2. Deleted information: If an action causes information to be deleted, your application must provide the following:

    2.1 The ability to recover deleted information.

    2.2 Request confirmation to continue with a selected action.

    2.3 A checkbox in addition to a Submit button.

  3. Web page includes a testing application: If a Web page includes a testing application, your application must provide the following:

    3.1 The ability for the user to review and correct answers before submitting.

    3.2 Request confirmation to continue with a selected action.

    Note: The examples presented in the techniques are not exhaustive. They are meant to illustrate the spirit of this checkpoint.

General examples

  1. Forms involving legal transactions: For forms involving legal transactions, such as making a purchase or submitting an income tax return, your application must provide the following:

    1.1 A stated period of time after submission of a form when an order can be updated or canceled by the user.

    General example 1

    When a customer places an order for a book on a merchant’s Web site, they are given 24 hours to cancel or change the order. The 24-hour policy is explained as part of the checkout procedure when purchasing a book.

    Required unit tests for general development technique 1.1

    Manually confirm that forms involving legal transactions, such as a making a purchase or submitting an income tax return, provides the user with a time period to cancel or change an order and describes the change.

    1.2 The ability for the user to review and correct answers before submitting a form.

    General example 2

    A Web application contains tests for university students. A student completes answers on each page of a test and navigates to the next page by selecting a Next link. At any time while completing a test, a student may select a Previous link to return to the previous page to change their answers. Additionally, when all questions have been answered, students are given the opportunity to review and change answers before finally submitting a test.

    Required unit tests for general development technique 1.2

    Locate form elements. For any forms involving legal transactions, such as making a purchase or submitting an income tax return, manually review the form to confirm that the Web page provides the ability for the user to review previous entries and correct answers before submitting.

    1.3 Provide a checkbox and a Submit button.

    General example 3

    A Web site that allows users to renew their driver license prompts the user to enter their name, date of birth, license plate number and credit card payment information. Because the transaction is not reversible after submission, the last page of the renewal process presents the data the user has entered and a checkbox asking the user to select the box if the information entered is correct.

    Required unit tests for general development technique 1.3

    Manually confirm that forms involving legal transactions, such as making a purchase or submitting an income tax return, contain the following:

  2. Deleted information: If an action causes information to be deleted, your application must provide the following:

    2.1 The ability to recover deleted information.

    General example 4

    A Web-based email application moves deleted emails to a trash folder for a 10-day period before permanently removing the emails. Before the 10-day period has expired, a user may restore deleted items by moving the emails from the trash folder back to the inbox.

    2.2 Request confirmation to continue with a selected action.

    General example 5

    A stock brokerage Web site permits users to buy stocks. The last page in the stock purchase process presents the user with a message that says "this is a firm order that cannot be reversed". After the message, the page displays a Confirm button to place the order and a Cancel button to cancel the order.

    Required unit tests for general development techniques 2.1 and 2.2

    Manually confirm that forms involving legal transactions, such as making a purchase or submitting an income tax return, enable the following actions:

    2.3 A checkbox and a Submit button.

    See general example 3 above.

  3. Web page includes a testing application: If a Web page includes a testing application, your application must provide the following:

    3.1 The ability for the user to review and correct answers before submitting.

    See general example 2 above.

    3.2 Request confirmation to continue with a selected action.

    See general example 5 above.

 

Recommended development techniques

Although you are note required to implement the recommended techniques in order to comply with this checkpoint, you should review these techniques because they can improve the accessibility and usability of the application. Refer to the WCAG 2.0 Additional Techniques (Advisory) for Success Criterion 3.3.4 (link resides outside of ibm.com) for a list of techniques and examples.


©2011 IBM Corporation

Last updated July 1, 2011.

W3C Recommendation 11 December 2008: http://www.w3.org/TR/WCAG20/ (link resides outside of ibm.com)
Copyright 1994-2009 W3C (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University), All Rights Reserved.