Update prefill pattern VADS content

[msbtterswrth]

Staging review feedback on our new pattern:

• Staging Review finding: Descriptive alt text for images va.gov-team#98539 - BLOCKER
• Staging Review finding: Ensure that content style guide is also updated with engagement/feedback/alert messages va.gov-team#98543 (make changes to https://dev-design.va.gov/3480/content-style-guide/error-messages/engagement) See comment below with the updates needed for this bullet point.
• Staging Review finding: Typo: "Design principals" va.gov-team#98540
• Staging Review finding: Broken links for user research va.gov-team#98541
• Staging Review finding: Make new tab behavior consistent in examples for "directions for updating uneditable information" section va.gov-team#98542
• Staging Review finding: Add guidance around alert placement va.gov-team#98532
• Staging Review finding: Missing comma in "design principles"  va.gov-team#98534

Staging review feedback on our the Prefill pattern documentation:

• Staging Review finding: Confusing language in "when to use this pattern"  va.gov-team#98533
  • Change the sentence "When using this pattern, clearly inform the user of where their data is being pulled from to prefill for them." to "When using this pattern, clearly inform the user where their data is being pulled from to complete the prefill."
• Staging Review finding: Missing comma in "design principles"  va.gov-team#98534
  • The "Design Principles" section should use the exact text that we have in the Update Prefill page.
• Staging Review finding: Errant capitalization in image caption under "prefill check page"  va.gov-team#98535
  • In the caption "Image caption: Editable prefilled information displayed on the Prefill check page. This is the proposed style to display data that is editable" make "prefill" lower case.
• Staging Review finding: Placeholder text in "communicate information that can not be edited" section va.gov-team#98536
  • In the bullet point "Directions for editing uneditable information" remove the last phrase "which will be updated soon".

Additional changes to make to the Prefill pattern based on the changes we made after the second round of research:

USAGE section

• In "When not to use this pattern > For unauthenticated users" the period after "unauthenticated users" should be bolded to match other bolded periods on the page.

HOW TO DESIGN AND BUILD section

• Change "Prefill check page: Any page of a form that displays prefilled information users can edit within the form." to say "Prefill edit pages: Any pages on which users edit prefilled data."
• Update screenshots under the "How to design and build" - see Slack message
• "How this pattern works" section - use what we have in Github for this section (I had updated it earlier but we didn't make a PR with it)
• Under "How this pattern works," after the sentence "The alert also encourages users to sign in to benefit from this time-saving feature." add "This alert should be placed at the top of the page, directly under the form name."

EXAMPLES section
I think most of this requires updates to the code.

• Update cards to match designs
• Remove the Prefilled Info Alert
• Update Signed In Prefill Alert to match designs

CONTENT CONSIDERATIONS section

• Under "Directions for updating uneditable information" change the text to: "Directions for updating information that can’t be updated online vary. See the "Help users to... Update Prefilled information" pattern for guidance.
• Replace "Authenticated intro page alert" screenshot - see Slack message
• Remove the "Authenticated contextual alert" header, text, and screenshot below it.

RESEARCH section

• Update the user research section to say: "The Authenticated Experience Design Patterns team conducted user research in mid 2024 to gather validation about this pattern. The pattern was further tested as part of a late 2024 study by the same team.

Staging review feedback on the "Help users to…Know how their information is updated" pattern, which will be coming down (no action needed; we'll close the tickets):

• Staging Review finding: Errant capitalization in "when to use this pattern"  va.gov-team#98537
• Staging Review finding: Inappropriate use of bold text for emphasis va.gov-team#98538

[msbtterswrth]

@kristen101606 @ChristineRoseSteiffer can we drop in the updates that need to be made for the first pattern including screenshots and content that needs to be updated.

[msbtterswrth]

Will circle back to update screenshots relating to alerts once we get all these updates completed.

[adamwhitlock1]

The main content PR for this page is marked as ready to review here:

department-of-veterans-affairs/vets-design-system-documentation#3562

Everything but the code examples for the 'Know when their information is prefilled' have been updated to what is the newest content and addresses these staging tickets.

@msbtterswrth there has been a lot of back and forth for the content, and I am 95% sure that I have all the current changes integrated into this PR, but if you could double check my work, the preview URL is: https://dev-design.va.gov/3562/patterns/help-users-to/update-prefilled-information

[kristen101606]

For the second bullet point in the body of the comment above, here are the changes we need to make:

• On the Engagement messages page, there are 3 rows that deal with Prefill. Those 3 rows should change to these 2 rows:

Scenario	Message title	Message content	Actions	Component	State	Location
Prefill - Intro variation (for authenticated users)	We’ve prefilled some of your information	Since you’re signed in, we’ve prefilled part of your application based on your profile details. You can also save your application in progress and come back later to finish filling it out.	None	Alert box	Informational	After h1 on Form Introduction page
Prefill - Step variation (for authenticated users) - If saving to form and Profile	None	Any changes you make will also be reflected on your VA.gov profile.	None	Alert box	Informational	After Progress bar - Segmented on a Form Step page

• On the System Messages page, we should replace the row starting with "Form prefill notice" to the below 2 rows:

Scenario	Message title	Message content	Actions	Component	State	Location
Save your work in progress (for unauthenticated users)	Sign in now to save time and save your work in progress	Here’s how signing in now helps you: * We can fill in some of your information for you to save you time. * You can save your work in progress. You’ll have 60 days from when you start or make updates to your application to come back and finish it. Note: You can sign in after you start your application. But you’ll lose any information you already filled in.	Sign in to start your application (primary button); Start your application without signing in (link)	Alert box	Informational	After h1 on Form Introduction page
Prefill - Intro variation (for authenticated users)	We’ve prefilled some of your information	Since you’re signed in, we’ve prefilled part of your application based on your profile details. You can also save your application in progress and come back later to finish filling it out.	None	Alert box	Informational	After h1 on Form Introduction page

[msbtterswrth]

@adamwhitlock1 this looks great to me! Let's get this in front of Matt and co and we'll address any changes we need to make next sprint in a separate PR.