Input Assistance 3.3

Understanding Guideline 3.3

Error Prevention (Legal, Financial, Data) 3.3.4

Understanding Success Criterion 3.3.4

Acceptance Criteria
  • 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.
If an Application Causes a Legal Transaction to Occur, Such as Making a Purchase
  • Provide a stated time within which an online request (or transaction) may be amended or canceled by the user after making the request.
  • Provide the ability for the user to review and correct answers before submitting.
If an Action Causes Information to be Deleted
  • Provide the ability to recover deleted information.
  • Request confirmation to continue with selected action.
Notes

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 below criteria is true.

Error Identification 3.3.1

Understanding Success Criterion 3.3.1

Acceptance Criteria
  1. Provide text descriptions to identify required fields that were not completed.
  2. Provide client-side validation and alert (if applicable).
  3. Provide a text description when the user provides information that is not in the list of allowed values.
  4. Provide a text description when user input falls outside the required format or values.
  5. Highlight errors where they occur.
  6. Need asterisk by required fields. Also, need note stating what asterisk means: Starred(*) fields are required.
Notes

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.

Labels or Instructions 3.3.2

Understanding Success Criterion 3.3.2

Example

        			
<label for="password">Password</label>
<input id="password" type="text" aria-describedby="passwordDesc">
<p id="passwordDesc">Must use 1 uppercase letter and 1 number.</p>
Acceptance Criteria
  1. Provide text instructions at the beginning of a form or set of fields that describes the necessary input.
  2. Position labels to maximize predictability of relationships.
  3. Indicate required form controls using label or legend.
  4. Use label elements to associate text labels with form controls.
  5. Provide a description for groups of form controls using fieldset and legend elements.
  6. Use the title attribute to identify form controls when the label element cannot be used.
Form Labeling

More Information on ARIA within Forms

Meeting Acceptance Criteria on Form Labeling
  1. Use <label> element when you can. It has excellent browser and screen reader support, and users can click on the label to select the associated form control.
  2. Use aria-labelledby to overcome the 1:1 limitations of <label>.
  3. Use aria-describedby in addition to a label when you need to associate descriptive text to the form control.
  4. Use a hidden <label> or title or aria-label when a visible text label is not available.
Notes

Labels or instructions are provided when content requires user input.

Error Suggestion 3.3.3

Understanding Success Criterion 3.3.3

Acceptance Criteria
  1. Create a mechanism that allows users to jump to errors.
  2. Make error messages easy to understand and distinguishable from other text in the Web page.
  3. When mandatory information has not been provided, including descriptions or examples of correct information in addition to identifying the field as mandatory.
  4. Repeat and emphasize suggestions for correcting each input error in the context of its form field.
  5. Provide a way for the user to skip from each item in a list of suggestions to its corresponding form field.
  6. Provide additional contextual help for the form field requiring change.
  7. Accept input data in a variety of formats.
  8. Provide success feedback when data is submitted successfully
If a Mandatory Field Contains No Information
  • Provide text descriptions to identify required fields that were not completed.
  • Identify a required field with the aria-required property.
If Information for a Field is Required to be in a Specific Data Format
  • Use aria-alertdialog to Identify Errors.
  • Provide a text description when user input falls outside the required format or values.
  • Provide suggested correction text.
  • Provide client-side validation and alert.
  • Provide client-side validation and adding error text via the DOM.
Notes

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

Accessible Authentication (Minimum) 3.3.8

Understanding Success Criterion 3.3.8

Acceptance Criteria
  1. A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:
    • Alternative: Another authentication method that does not rely on a cognitive function test.
    • Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
    • Object Recognition: The cognitive function test is to recognize objects.
    • Personal Content: The cognitive function test is to identify non-text content the user provided to the website.
Notes

Don’t make people solve, recall, or transcribe something to log in.

To Top