3.3.1 Error Identification
Contents |
3.3.1 3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) Intent of this Success Criterion The intent of this Success Criterion is to ensure that users are aware
3.3.3 Error Suggestion
that an error has occurred and can determine what is wrong. The error message should error identification worksheets be as specific as possible. In the case of an unsuccessful form submission, re-displaying the form and indicating the fields in error is what is error identification 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. They may abandon the form altogether before
3.3.4 Error Prevention (legal, Financial, Data)
encountering the error indicator, thinking that the page simply is not functional. Per the definition in WCAG 2.0, an "input error" is information provided by the user that is not accepted. This includes: information that is required by the web page but omitted by the user, orinformation that is provided by the user but that falls outside the required data format or allowed values.For example:the user fails to enter the proper abbreviation in to state,
Error Identification Tips
province, region, etc. field; the user enters a state abbreviation that is not a valid state; the user enters a non existent zip or postal code;the user enters a birth date 2 years in the future;the user enters alphabetic characters or parentheses into their phone number field that only accepts numbers;the user enters a bid that is below the previous bid or the minimum bid increment.Note: If a user enters a value that is too high or too low, and the coding on the page automatically changes that value to fall within the allowed range, the user's error would still need to be described to them as required by the success criterion. Such an error description telling the person of the changed value would meet both this success criterion (Error Identification) and Success Criterion 3.3.3 (Error Suggestion). The identification and description of an error can be combined with programmatic information that user agents or assistive technologies can use to identify an error and provide error information to the user. For example, certain technologies can specify that the user's input must not fall outside a specific range, or that a form field is required. Currently, few technologies support this kind of programmatic information, but the Success Criterion does not require, nor prevent it. It is perfectly acceptable to indicate the error in other ways suc
3.3: Help users avoid and correct mistakes. Intent of Guideline 3.3Everyone makes mistakes. However, people with some disabilities have more difficulty creating error-free input. In error identification exercises grammar addition, it may be harder for them to detect
Error Identification Definition
that they have made an error. Typical error indication methods may not be obvious to error identification practice them because of a limited field of view, limited color perception, or use of assistive technology. This guideline seeks to reduce the number of http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-identified.html serious or irreversible errors that are made, increase the likelihood that all errors will be noticed by the user, and help users understand what they should do to correct an error. Advisory Techniques for Guideline 3.3 (not success criteria specific)Specific techniques for meeting each Success Criterion for this guideline http://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error.html are listed in the understanding sections for each Success Criterion (listed below). If there are techniques, however, for addressing this guideline that do not fall under any of the success criteria, they are listed here. These techniques are not required or sufficient for meeting any success criteria, but can make certain types of Web content more accessible to more people.Hiding optional form fields (future link)Success Criteria for this Guideline: Understanding Success Criterion 3.3.1 [Error Identification] Understanding Success Criterion 3.3.2 [Labels or Instructions] Understanding Success Criterion 3.3.3 [Error Suggestion] Understanding Success Criterion 3.3.4 [Error Prevention (Legal, Financial, Data)] Understanding Success Criterion 3.3.5 [Help] Understanding Success Criterion 3.3.6 [Error Prevention (All)] TopContentsIntroPrevious: SC 3.2.5 [Change on Request]Next: SC 3.3.1 [Error Identification]This Web page is part of Understanding WCAG 2.0: A guide to understanding and implementing WCAG 2.0 (see the latest version of this document). The entire document
SoftwareMicrosoft ExcelMicrosoft PowerPointMicrosoft SilverlightMicrosoft WordMultimedia and Video ProgrammingSupport Information, Documentation, and Employee TrainingWebWindows Native SoftwareStandards508.22WCAG2 AWCAG2 AA Home>Best Practices>WCAG 2.0 Level A https://www.webaccessibility.com/best_practices.php?standard_id=646 >3.3.1 Error IdentificationShare this: 3.3.1 Error IdentificationDescriptionError Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. Locationhttp://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-identified.htmlMapped Best PracticesBest Practice - Sort DescendingParent Media Type - Ascending - Sort DescendingMedia error identification Type - Sort DescendingEnsure error messages are explicitly indicated at the beginning of a form after submitAdobe Acrobat PDFFormsEnsure audio information is not the only method used to indicate completion or errorAdobe Flash/FlexFormsEnsure error messages are explicitly indicated at the beginning of a form after submitAdobe Flash/FlexFormsEnsure 3.3.1 error identification audio information is not the only method used to indicate completion or errorAndroid OSAudio, Video and MultimediaEnsure error messages are in a platform specific alert or focus is moved to the error message after submitAndroid OSError HandlingProvide a clear indication of errorsAndroid OSError HandlingEnsure error messages are indicated in an accessible mannerDelphiFormsProvide both an audio and visual indication of any user cuesEmbedded SoftwareFormsEnsure error messages are explicitly indicated at the beginning of a form after submissionEmbedded SoftwareFormsProvide a clear indication of errorsEmbedded SoftwareFormsResults 1 - 10 of 26Show items per page Show items per page: All | Show items per page: 10 | Show items per page: 25 | Show items per page: 50 | Show items per page: 100< Previous Page 1 | Page 2 | Page 3 Page Next > Connect Connect on Facebook Follow on Twitter @WebAccess4Al