Skip to content

Commit cbabb0b

Browse files
Updates from Help Errors Triggers group (#347)
--------- Co-authored-by: Kenneth G. Franqueiro <[email protected]>
1 parent 2f83f2a commit cbabb0b

19 files changed

+101
-22
lines changed

guidelines/groups/error-handling.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
{
22
"children": [
3-
"correct-mistakes"
3+
"correct-errors",
4+
"prevent-errors"
45
]
56
}
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
children:
3+
- error-association
4+
- error-cause-association
5+
- error-cause-in-notification
6+
- error-identification
7+
- error-linked
8+
- error-location
9+
- error-notification-label
10+
- error-notification
11+
- error-persists
12+
- error-suggestion
13+
- make-errors-distinct
14+
---
15+
16+
Users know about and can correct errors.
Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
status: exploratory
2+
status: developing
3+
type: supplemental
34
---
45

56
Error notifications are :term[programmatically associated] with the error source so that users can access the error information while focused on the source of the error.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
status: developing
3+
---
4+
5+
When an error occurs that results from a user interaction with an :term[interactive element] or component (aka a cause), the element or component is visually and programmatically associated with the trigger.
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
status: developing
3+
type: supplemental
4+
---
5+
6+
When an error occurs that results from an :term[interactive element] or :term[component] (aka a cause), an indicator of the trigger is included in the error notification. If the interactive element or component is located in a different part of a process, then the page or step in the process is included in the error notification.
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
status: exploratory
2+
status: developing
33
---
44

55
Errors are visually identifiable without relying on only text, only color, or only symbols.
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
status: developing
3+
type: supplemental
4+
---
5+
6+
When an error notification is not adjacent to the item in error, a link to the error is provided.
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
status: developing
3+
type: supplemental
4+
---
5+
6+
Error notifications are visually collocated with the item in error within the viewport, or provide a link to the source of the error which, when activated, moves the focus to the error.
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
status: developing
3+
type: supplemental
4+
---
5+
6+
Error notifications include text with at least two of the following:
7+
* Error notifications are identified with an error icon in text.
8+
* Error notifications use a color that differentiates the error from other content.
9+
* Error notifications are labeled with text that indicates its an error.
Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
---
2-
status: exploratory
2+
status: developing
3+
type: foundational
34
---
45

56
Errors that can be automatically detected are identified and described to the user.

0 commit comments

Comments
 (0)