《质量效应：仙女座》IGN 7.7分 好玩但问题太多
百度 在他的笔下，这些历史人物重新被赋予生命，走出书中来到读者面前，告诉我们汉朝的衰亡对于当今的警世意义。3.3.1 Error Identification: If an input error is 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 that an error has occurred and can determine what is wrong. The error message should be as specific as possible. In the case of an unsuccessful form submission, re-displaying 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. They may abandon the form altogether before encountering the error indicator, thinking that the page simply is not functional.
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 such as image, color etc, in addition to the text description.
Specific Benefits of Success Criterion 3.3.1:
Providing information about input errors in text allows users who are blind or colorblind to perceive the fact that an error occurred.
This Success Criterion may help people with cognitive, language, and learning disabilities who have difficulty understanding the meaning represented by icons and other visual cues.
Examples of Success Criterion 3.3.1
Identifying errors in a form submission
An airline Web site offers a special promotion on discounted flights. The user is asked to complete a simple form that asks for personal information such as name, address, phone number, seating preference and e-mail address. If any of the fields of the form are either not completed or completed incorrectly, an alert is displayed notifying the user which field or fields were missing or incorrect.
Note: This Success Criterion does not mean that color or text styles cannot be used to indicate errors. It simply requires that errors also be identified using text. In this example, two asterisks are used in addition to color.
Providing multiple cues
The user fails to fill in two fields on the form. In addition to describing the error and providing a unique character to make it easy to search for the fields, the fields are highlighted in yellow to make it easier to visually search for them as well.
Related Resources
Resources are for information purposes only, no endorsement implied.
d3151 Communicating with - receiving - general signs and symbols. International Classification of Functioning, Disability and Health. 2001. World Health Organization.
Techniques and Failures for Success Criterion 3.3.1 - Error Identification
Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. The techniques listed only satisfy the Success Criterion if all of the WCAG 2.0 conformance requirements have been met.
Sufficient Techniques
Instructions: Select the situation below that matches your content. Each situation includes techniques or combinations of techniques that are known and documented to be sufficient for that situation.
Situation B: If information provided by the user is required to be in a specific data format or of certain values.
G85: Providing a text description when user input falls outside the required format or values
SCR18: Providing client-side validation and alert (Scripting)
Providing client-side validation and adding error text via the DOM (future link)
Additional Techniques (Advisory) for 3.3.1
Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.
G139: Creating a mechanism that allows users to jump to errors
Validating form submissions on the server (future link)
Re-displaying a form with a summary of errors (future link)
Providing error notification as the user enters information (future link)
Assisting the user in making corrections by providing links to each error (future link)
Highlighting or visually emphasizing errors where they occur (future link)
Supplementing text with non-text content when reporting errors (future link)
Failures for SC 3.3.1
The following are common mistakes that are considered failures of Success Criterion 3.3.1 by the WCAG Working Group.
(No failures currently documented)
Key Terms
- input error
information provided by the user that is not accepted
Note: This includes:
Information that is required by the Web page but omitted by the user
Information that is provided by the user but that falls outside the required data format or values