3.3 Understandable > Input Assistance Flashcards
What makes up 3.3 Input Assistance?
- 3.1 Error Identification - A
- 3.2 Label or Instructions - A
- 3.3 Error Suggestion - AA
- 3.4 Error Prevention - AA
- 3.5 Help - AAA
- 3.6 Error Prevention (All) – AAA
3.3.1 Understandable > Input Assistance > Error Identification
What? 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.
There are TWO situations: when the input is required or when the input requires a specific format
How? Identify with text, required fields that were not completed. Or Aria-Alert for format error.
Both situations should use Aria-Invalid but don’t make it true for requireds until submitted. Client side validation and alert.
For format, provide text description when entry is not on list, is not in format, use Aria role=alert, aria-alertdialog (modal) with aria-label or aria-labelledby.
3.3.2 Labels and Instructions
What? present instructions or labels that identify the controls in a form so that users know what input data is expected.
provide important cues and instructions that will benefit people with disabilities.
HOW?
What it is NOT-
does not require that labels or instructions be correctly marked up, identified, or associated with their respective controls - this aspect is covered separately by 1.3.1: Info and Relationships.
does not take into consideration whether or not alternative methods of providing an accessible name or description for form controls and inputs has been used - this aspect is covered separately by 4.1.2: Name, Role and Value.
whether or not these labels are sufficiently clear or descriptive is covered separately by 2.4.6: Headings and Labels.
How? aria-describedby, aria-labeledby, aria grouping roles, provide format examples, text instructions, position labels, identify required fields not completed, indicate required using label or legend and on PDF, use label elements
Failure! F82: Failure of Success Criterion 3.3.2 by visually formatting a set of phone number fields but not including a text label
3.3.3 Error Suggestion
What? ensure that users receive appropriate suggestions for correction of an input error if it is possible. Success Criterion 3.3.1 provides for notification of errors, this one tells them how to fix errors.
How?
Mandatory field not completed- text description to identify it as required, aria-required, PDF indicate required.
Data input must be in specific format OR Input must be one of limited set of values: aria-alertdialog, text description, provide suggested correction text, client-side validation and alert, client-side addition of error text via the DOM, indicating error for PDF
3.3.4 Error Prevention (Legal, Financial, Data)
What? For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:
Reversible-Submissions are reversible.
Checked-Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
Confirmed-A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
How?
Legal transaction- a stated time within which they can back out, ability to review and correct before submittal, a checkbox in addition to a submit button
Information Deletion- ability to recover deleted data, confirm to continue, a checkbox in addition to a submit button
Testing App - ability to review and correct before submittal, request confirmation before continuing.
3.3.5 Help
AAA
What? help users avoid making mistakes. Using context-sensitive help, users find out how to perform an operation without losing track of what they are doing.
Context-sensitive help only needs to be provided when the label is not sufficient to describe all functionality.
How? Provide help link on every page, provide help by an assistant, provide spell checking and suggestions for input, text instructions, expected format example,
3.3.6 Error Prevention (ALL)
AAA
What? For Web pages that require the user to submit information, at least one of the following is true:
Reversible-Submissions are reversible.
Checked-Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
Confirmed-A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
How? Following the sufficient techniques for Success Criterion 3.3.4 for all forms that require the user to submit information.
Here they are: a stated time within which they can back out, ability to review and correct before submittal, a checkbox in addition to a submit button, ability to recover deleted data, confirm to continue, a checkbox in addition to a submit button, ability to review and correct before submittal, request confirmation before continuing.
