-- **User action.** Offer the user clear guidance on how to resolve the error (ie, "Please make sure your file is a .pdf format").
-- **Authorization issue.** If the issue is due to VA.gov inability to find user's records in our system, direct the user to try again or call the VA.gov help desk if they think their records should be available.
-- **User's records showing the user can't use benefit/service.** Offer a path forward:
- - **User not eligible for benefit:** Direct to relevant eligibility information
- - **User not enrolled in benefit:** Direct to relevant eligibility information and application page.
- - **User not a VA patient:** Direct to facility locator to find contact information to call their VA facility.
-- **System or network access issue.** The error message should include timing for when the user should try again. This can be specific timing (eg, in an hour, tomorrow, etc.) if an estimate is available or more general timing (eg, soon, later) if an estimate isn't available.
+### How this pattern works
-### 4. If the resolution fails, what’s the next step?
+- Use the default Error alert when there is a problem (such as a sign in failure).
+- Use the default Warning alert to communicate system-wide issues.
+- Use the Background alert variation for immediate feedback, such as in single-page applications or dynamic Javascript driven forms.
+- Use inline error messaging when an issue has occurred within a form field. In all cases, only show error validation messages or stylings after a user has interacted with a particular field.
-The answer will inform whether or not to include a “next-step call to action” to help guide the user further should the first call to action fail to resolve the issue. This may be language directing the user to call the VA.gov help desk or other VA resources, and will be determined on an issue-by-issue basis. See [Next-step calls to action](#next-step) below for more information and guidance.
+### Components used in this pattern
-## Content within the message - Task completion
+#### Alert
-Below are examples of each type of [Alert]({{ site.baseurl }}/components/alert) style for task completion.
+#### Background alert
-### Success alerts
+#### Form field error states
-Create a brief title documenting the task that was successfully completed, followed by a brief description of the success.
+## Content considerations
-#### Saved
+## Accessibility considerations
-{% include component-example.html alt="Success alert for saving." file="/images/patterns/help-users-to/recover-from-errors/saved-001.png" caption="We saved the information you've entered so far." reverse=true width="50%" %}
-
-### Error alerts
-
-Include exactly what failed in the title, followed by a brief apology, reiteration of the failure reframed in the VA.gov perspective, and prompt to try again.
-
-#### Your form didn't save
-
-{% include component-example.html alt="Error alert for form didn't save." file="/images/patterns/help-users-to/recover-from-errors/saved-error-002.png" caption="We're sorry. We couldn't save your form. Please try again." width="50%" %}
-
-Consider whether there is additional information, including a time estimate for resolution and/or a call to action button, that should be included.
-
-#### Please save this application and try again
-
-{% include component-example.html alt="Error alert for please save and try again." file="/images/patterns/help-users-to/recover-from-errors/saved-error-003.png" caption="We're sorry. Your application didn't go through. We're working to fix the problem, but it may take us a while. Please save your application, and try again tomorrow." width="50%" %}
-
-### Informational messages and warnings
-
-To create an effective informational message or warning, ask yourself these 2 questions:
-
-### 1. What's the key information the user needs to know?
-
-This information should be presented as succinctly as possible in the title and then reiterated in the description with any additional relevant details.
-
-#### Informational example
-
-{% include component-example.html alt="Info alert for site maintenance." file="/images/patterns/help-users-to/recover-from-errors/down-004.png" caption="We’ll be doing some work on VA.gov on [DATE] between [TIME] and [TIME]. If you have trouble using the site during that time, please check back soon." reverse=true width="75%" %}
-
-#### Warning example
-
-{% include component-example.html alt="Info alert for site maintenance." file="/images/patterns/help-users-to/recover-from-errors/warning-005.png" caption="We’re doing some work on VA.gov right now. You should still be able to use the site applications and tools. If you have any trouble, please check back soon." reverse=true width="75%" %}
-
-### 2. Does the user need to take action, or do we want the user to take action?
-
-When action is required, frame required information as a need.
-
-#### We need your help to finish reviewing your claim
-
-{% include component-example.html alt="Info alert for site maintenance." file="/images/patterns/help-users-to/recover-from-errors/continue-006.png" caption="We need you to provide more evidence (supporting documents) so we can finish reviewing your claim." reverse=true width="50%" %}
-
-When we want to prompt the user to take action, frame the prompt as a question to engage the user.
-
-#### Want to make your VA.gov account more secure?
-
-{% include component-example.html alt="Info alert for site maintenance." file="/images/patterns/help-users-to/recover-from-errors/secure-007.png" caption="You can add an optional extra layer of security (called 2-factor authentication) to your account. This helps to make sure that no one but you can access your account—even if they get your password." reverse=true width="50%" %}
-
-## Messages dictionary
-
-The messages dictionary holds the title, content, component, and state for each scenario of message on the site.
-
-View the messages dictionary
-
-## Style and tone
-
-### Clear and direct
-
-Tell the user what’s happened/happening, how it will impact them, and how they can resolve it.
-
-### Humble, helpful, and non-alarming
-
-