Info and relationships
Benefits: Blind, low-vision disabilities.
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
- Do form labels and fields have same/similar and appropriate identification that relates the fields with the label?
- Are labels positioned nearby their associated fields?
- Are labels still viewable when zoomed?
- Can users with different disabilities use Assistive Technologies to adapt content according to the user's needs?
- Is information and relationships that are implied by visual or auditory formatting preserved when the presentation format changes?
Benefits: Blind, low vision, cognitive/intellectual, motor disabilities.
When any component receives focus, it does not initiate a change of context.
- Is functionality predictable as the user navigates their way through a document?
- Is an unexpected change of context avoided when a component receives focus?
Benefits: Blind, low vision, cognitive/intellectual disabilities.
Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.
Changes of context are appropriate only when it is clear that such a change will happen in response to the user's action.
- Is the user pre-informed/cued when a change to a form control has a change of context?
- Is an explanation of what will happen when the control is changed available prior to the controls activation?
Benefits: Blind, colorblind, cognitive/intellectual disabilities.
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.
- Is the user aware and notified/alerted that an input error has occurred?
- Can the user determine and understand what is the error?
- Is the message specific to the error?
Labels or instructions
Benefits: Blind, low-vision, motion impairment, cognitive / intellectual disabilities.
Labels or instructions are provided when content requires user input.
- Are instructions or labels that identify the controls in a form placed so that users know what input data is expected?
- Are data format instructions specified in the instructions or labels, or are examples provided, especially when there are out of customary formats or specific rules for correct input?
- Can the user accomplish the task without undue confusion or navigation?
- Can the user determine required versus optional fields, so that an incomplete form cannot be submitted?
- Are field labels located in close proximity to the associated field?
Benefits: Blind, colorblind, motion impairment, cognitive/intellectual disabilities.
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.
- Does the user receive appropriate suggestions for correction of an input error?
- Can the user determine how to correct the error?
Error prevention (Legal, Financial, Data)
Benefits: All disabilities.
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.
- Can the user correct a mistake to avoid the serious consequences as the result of an action that cannot be reversed?
- Are safeguards provided to avoid mistakes that can have serious consequences?
- Can the user review, correct, confirm before submitting or deleting?
- Is success feedback provided when data is submitted successfully?
Name, role, value
Benefits: All disabilities using Assistive Technologies.
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.
- If custom controls are created, or interface elements are programmed (in code or script) that have a different role and/or function than usual, are additional measures used to ensure that the controls provide important information to Assistive Technologies and can be controlled by assistive technologies.