WELCOME [ Log In · Register ]        SITE [ Search · Page Index · Recent Changes ]    RSS

Minimize Errors

Home > PDF/UA Home > Working Draft > Breadcrumb placeholder text

Reference WCAG 2.0 Guideline 2.5
Help users avoid mistakes and make it easy to correct them.

2.5.1
If an input error is detected, the error is identified and described to the user in text.

Accessibility Issue

The intent of this success criterion is to ensure that users are aware that an error has occurred and can determine what is wrong. In the case of an unsuccessful form submission, redisplaying the form and indicating the fields in error is insufficient for some users to perceive that an error has occurred. Screen reader users, for example, will not know there was an error until they encounter one of the indicators.
Providing information about input errors in text allows users who are blind, colorblind, or have learning disabilities to perceive the fact that an error occurred.

PDF/UA Implications

Required fields:

·    Provide a text message when any of the mandatory information has not been provided, and

·    The text message either:

1.      identifies the mandatory fields, or

2.      describes the method used to identify the mandatory fields.

Data formats and values:

·    Provide a text message when the user provides any information that falls outside the required data format or values, and

·    The text message does one of the following:

1.      identifies the field(s) in error and describes the acceptable data format or value range(s); or

2.      describes the method used to identify the field(s) in error and the method used to describe the acceptable data format or value range.

·    Validating data format for data provided in a form field.

·    Validating data provided in a form field.

·    Indicating mandatory fields on a form.

Proposed Revision

Comments

Possible exception: Usability studies which want to capture incorrect data input.

Requirement(s)

  1. If error detection/validation is used, error messages shall be provided in text which can be programmatically determined.
  2. If successful submission of a form is dependent upon correct field input, an error message shall identify the error.

2.5.2

If an input error is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the suggestions are provided to the user.

Comments on the Reference (Success Criteria)

Accessibility Issue

People need to understand how to correct their input. The intent of this success criterion is to ensure that users receive appropriate suggestions for correction of an input error if it is possible.

PDF/UA Implications

Proposed Revision

Comments

Exceptions: Passwords, Tests

A text message shall be provided which:

·    identifies mandatory fields, or

·    describes the method used to identify mandatory fields.

Error messages shall be provided in text which:

·    identify the error, and

·    describe how to correct the error.

·    Fields which require data input in a particular format or of a particular value range(s), shall describe the acceptable format or value range(s).

·    Mandatory fields shall be identified.

Requirement(s)

  1. An error message shall describe how to correct input errors, unless doing so would invalidate the security or purpose of the form.

2.5.3

For forms that cause legal or financial transactions to occur, that modify or delete data in remote data storage systems, or that submit test responses, at least one of the following is true:

·     Actions are reversible.

·     Actions are checked for input errors before going on to the next step in the process.

·     The user is able to review and confirm or correct information before submitting it.

Comments on the Reference (Success Criteria)

Accessibility Issue

The intent of this success criterion is to help users with disabilities avoid serious consequences as the result of a mistake. For example, purchasing non-refundable airline tickets or submitting an order to purchase stock in a brokerage account are financial transactions with serious consequences. If a user has made a mistake on the date of air travel, he or she could end up with a ticket for the wrong day which can't be exchanged. If the user made a mistake on the number of stock shares to be purchased, he or she could end up purchasing more stock than intended. Both of these types of mistakes can be very costly.

Users with disabilities may be more likely to make mistakes. People with learning disabilities may transpose numbers and letters, and those with motor disabilities may hit keys by mistake. Providing the ability to reverse actions allows users to correct a mistake that could result in serious consequences. Providing the ability to review and correct information gives the user an opportunity to detect a mistake before taking an action that has serious consequences.

PDF/UA Implications

Proposed Revision

Comments

We cannot predict the types of transactions that may be available in the future. The key words here are "serious consequences." "Serious consequences" is not something that can be verified.
Error detection/validation is not something that can be mandated. It is a business decision. The point is that IF validation is used, it shall do blah, blah, blah.

Requirement(s)

Forms which submit data shall allow users the opportunity to review and correct their input prior to submission.

2.5.4

Context-sensitive help is available for text input.

Comments on the Reference (Success Criteria)

Accessibility Issue

The intent of this success criterion to help users avoid making mistakes. Because of their disabilities, or aging, these users may be more inclined to make mistakes than users without disabilities.

PDF/UA Implications

Not needed here. Labels and tolltips could be considered context-sensitive help and are provided for in other requirements.