Feedback

The success or failure of every user initiated action is clearly indicated to the user by visual, programmatically-determinable, rapid feedback in the primary modalities of the content. Audio feedback is supported.

Suggestion for Priority Level: AA

Related Glossary additions

Clearly indicated (success or failure)

confirmation informing the user, after a user-action, that the action was successful or failed and, if the action is part of a process, where the user is in the process.
(was: confirm that, after a user action, the user knows that the action was successful or not. Applications should also let the user know what just happened and where they are in a process.)

Rapid feedback

The next activity or event affecting the application.

Audio feedback (was: Spoken feedback)

Audible feedback is often more effective then written feedback. However, having both audible feedback and longer-lasting written and visual feedback helps the user know where they are, and restores the context if attention is lost. Audible feedback can annoy and distract some people, so audible feedback should be available as an option, and in response to a user-preference setting when available.
(was: Spoken feedback is often more effective then written feedback. However, having both spoken feedback and longer-lasting written and visual feedback helps users know where they are, and restores the context if attention is lost. Spoken feedback can annoy and distract some people, so spoken feedback should be available as an option, and in response to a user-preference setting when available.)

Primary modalities of the content

Modes and technologies considered during design phase of development.

Principle and Guideline

Principle 3, Guideline 3.3

Description

Applications should consistently provide easily-recognizable success or failure feedback with every user action.

For example:

• After a step in a multi-step task is completed, breadcrumbs display a tick or a checkmark next to that step's name; and, if applicable, the title or the name of the next step is readily apparent.
• After a button is clicked, it should look depressed. (Note that if it is a toggle button, the state should also be programmatically determinable).
• After a form is submitted or an email message is sent, feedback communicating what just happened, such as "Your application was submitted, thank you" or "Your email message was sent" is provided.

Benefits

Overt indication of the result stemming from a user action helps people with a variety of cognitive disabilities:

• understand that their action occurred (e.g., the click did something);
• prevent uncertainty or doubt regarding the outcome; and
• remember what they just did.

User-action feedback during a multi-step task can also assist people, with attention or short-term cognitive disabilities, avoid inadvertently leaving a task by reminding them that they are in a process, and where in the process they currently are.

This information supports those who have Aphasia, Dementia, Dyslexia, or those who acquire cognitive disabilities as they age. It also helps anyone with impaired short-term memory remember what they just did.

Related Resources

Resources are for information purposes only. No endorsement is intended or implied.

• Cognitive Accessibility User Research sections: 3.1, 3.2, 3.4, 3.5, 3.6, 3.7, and 4.2
• Is a big button interface enough for elderly users? (PDF), page 24. Tanid Phiriyapkanon, Mälardalen University Press, Sweden, 2011

Testability

Procedure

1. Trigger every user-initiated action, and visually inspect the screen, to determine if the resulting content provides a rapid and clear indication of success or failure.
2. If the user-initiated action is part of a multi-step process, visually inspect the screen to confirm the resulting content informs users which steps have been completed, and which step they are on in the process.
3. Trigger every user-initiated action with a screen reader to determine if the resulting content announces a rapid and clear indication of success or failure.
4. If the user-initiated action is part of a multi-step process, confirm, with a screen reader, that the resulting content announces to users which steps have been completed, and which step they are on in the process.

Expected Results

• All checks above are true

Techniques

• All existing techniques for 3.3.1.
• Use WAI-ARIA states to provide state feedback for a toggle button with an animation showing the state (such as a button was pushed )
• Use ARIA-pressed with a visual or a checkbox is checked/unchecked,
• Provide a confirmation message when an email message is successfully sent, or a form is successfully submitted.
• Use a progress-indicator element (e.g., breadcrumbs) to communicate completed and current steps in a multi-step process.
• Provide visible and programmatically-determinable information to indicate a new password satisfies security requirements.