Matched up “correct errors” group with latest feedback

- Updated content in correct errors group to latest.
- Removed error linked, cause identified, descriptive errors.
- Changed name for error cause association to input errors.

Signed-off-by: Hidde de Vries <hidde@hiddedevries.nl>

Author: hidde

guidelines/groups/error-handling/correct-errors.md

@@ -1,15 +1,14 @@
 ---
 children:
   - error-notification
-  - error-cause-identified
-  - descriptive-errors
-  - error-cause-in-notification
-  - error-suggestion
   - error-visibility
-  - error-persists
-  - error-cause-association
-  - error-linked
+  - input-errors
+  - error-suggestion
   - error-location
+  - error-persists
+  - error-prevention
 ---
 
 Users know about and can correct errors.
+
+

guidelines/groups/error-handling/correct-errors/descriptive-errors.md

@@ -3,4 +3,14 @@ status: developing
 type: supplemental
 ---
 
-Error messages are visually collocated with the error source.
+Error messages are visually collocated with the error source or the focus is moved to the error message and a mechanism is available to move to the input that is in error. 
+
+:::tests
+<b>Procedure</b>
+1. Zoom in 400%
+2. Trigger errors
+3. Make sure the error is visible next to the trigger or that the focus moves to the error. 
+
+<b>Expected Results</b>
+* #3 is true
+:::

guidelines/groups/error-handling/correct-errors/error-cause-association.md

@@ -3,4 +3,18 @@ status: developing
 type: foundational
 ---
 
-When an error is detected, users are notified visually and programmatically that an error has occurred.
+Errors that can be automatically detected are identified and the problem is clearly described to the user.
+
+:::note
+Examples of errors include invalid form input, server errors or application errors.
+:::
+
+:::tests
+<b>Procedure</b>
+1.Identify parts of the conformance scope where errors can occur.
+2. Trigger errors.
+3. For each error, verify that the nature of the problem is identified and described
+
+<b>Expted results</b>
+* #3 is true for each error.
+:::

guidelines/groups/error-handling/correct-errors/error-cause-identified.md

@@ -3,4 +3,13 @@ status: developing
 type: foundational
 ---
 
-Error messages persist until the user dismisses them or the error is resolved.
+Error messages persist at least until the error is resolved or the user dismisses them.
+
+:::tests
+<b>Procedure</b>
+1. Identify the error messages. 
+2. Verify that the error messages persist until the user fixes the error or dismisses the message. 
+
+<b>Expected Results</b>
+* #2 is true
+:::

guidelines/groups/error-handling/correct-errors/error-cause-in-notification.md

@@ -0,0 +1,13 @@
+---
+status: developing
+type: foundational
+---
+
+Data entry allows users to do at least one of the following before submission:
+
+* Review, confirm, and correct all information; or
+* Review and correct input errors found during validation.
+
+:::except-when
+data submission is auto-saved and/or reversible.
+:::