54 lines
2.4 KiB
Markdown
54 lines
2.4 KiB
Markdown
[Back to 4 Robust index](index.md)
|
|
|
|
# 4.1.3 Status Messages
|
|
|
|
- Level: AA
|
|
- Guideline: 4.1 Compatible
|
|
- Principle: 4 Robust
|
|
|
|
## What it is
|
|
|
|
In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
|
|
|
|
## How to test
|
|
|
|
- Check: In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
|
|
- Use the sufficient techniques below as acceptable methods when applicable.
|
|
- Confirm none of the common failures apply.
|
|
|
|
## Sufficient techniques (W3C)
|
|
|
|
- ARIA22: Using role=status to present status messages
|
|
- G199: Providing success feedback when data is submitted successfully
|
|
- ARIA19: Using ARIA role=alert or Live Regions to Identify Errors
|
|
- G83: Providing text descriptions to identify required fields that were not completed
|
|
- G84: Providing a text description when the user provides information that is not in the list of allowed values
|
|
- G85: Providing a text description when user input falls outside the required format or values
|
|
- G177: Providing suggested correction text
|
|
- G194: Providing spell checking and suggestions for text input
|
|
- ARIA23: Using role=log to identify sequential information updates
|
|
- Using role="progressbar" (future link)
|
|
- G193: Providing help by an assistant in the web page
|
|
|
|
## Advisory techniques (W3C)
|
|
|
|
- Using aria-live regions with chat clients (future link)
|
|
- Using aria-live regions to support 1.4.13 Content on Hover or Focus (future link)
|
|
- Using role="marquee" (future link)
|
|
- Using role="timer" (future link)
|
|
- ARIA18: Using aria-alertdialog to Identify Errors
|
|
- SCR14: Using scripts to make nonessential alerts optional
|
|
|
|
## Common failures (W3C)
|
|
|
|
- F103: Failure of Success Criterion 4.1.3 due to providing status messages that cannot be programmatically determined through role or properties
|
|
- Using role="alert" or aria-live="assertive" on content which is not important and time-sensitive (future link)
|
|
|
|
## Resources
|
|
|
|
- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#status-messages
|
|
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html
|
|
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#status-messages
|
|
|
|
[Back to 4 Robust index](index.md)
|