[CAIA Intake] Guardian access / Secure sign-in transition updates for 2/1/25

[kdmeg-bluetiger]

Content, accessibility, information architecture (CAIA) new initiative collaboration request

Use this ticket to request collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) shared services team. Feel free to delete instructions and unselected options from the ticket to make it easier to scan.

Your team

• Product name: Sign-in experience
• Team name: OCTO Identity Experience
• OCTO product owner: Samara Strauss
• Product manager: Joelle Wells
• Slack channel: #secure-sign-in-transition
• Dedicated content writer on your team (if you have one): Megan Driscoll
• Dedicated a11y specialist on your team (if you have one): N/A

CAIA specialists involved

Filled out by CAIA

• IA: @kristinoletmuskat
• Content: @laurwill
• Accessibility: @coforma-jamie

Your Initiative

Which of these descriptions best fits the work we’ll partner on?

Select all that apply.

• Digitizing a new form
• Creating a new digital tool
• Updating an existing form or tool
• Translating a form or tool into Spanish
• Adding new unauthenticated content to VA.gov
• Updating existing unauthenticated content on VA.gov
• Something else:

What's the nature of your initiative and desired outcomes?

1. Update the sign-in modal and unified sign-in page content for secure sign-in changes taking place on February 1, 2025.

• Remove My HealtheVet from the list of sign-in options.
• Add link to new pages for court-appointed guardians to access My HealtheVet.
• Add link to new pages for anyone else who needs support creating a modern account to access My HealtheVet.
• Add link to details about how to delete your account to meet app store requirements per request of the Mobile team.

2. Add new pages to support edge cases that require access to My HealtheVet after January 31, 2025

• Court-appointed guardians
• Anyone else who can’t create a modern account by the deadline

Supporting artifacts

Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content. FOR FIGMA/MURAL: please tell us which screens/board/section to look at so we don't leave comments on old stuff.

• Figma file
• User flow
• Content iterations
• Research plan

Collaboration timeframe

These updates will be released on February 1, 2025 after the My HealtheVet depreaction.

Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.

Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?

• Yes
• No
• I’m not sure

Where are you at in your timeline?

Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.

• We had our design intent meeting on November 22, 2024.
• User research is being planned right now.
• Midpoint review is scheduled for December 5, 2024.
• These updates will be released on February 1, 2025.

Will you release this new product incrementally (for example, release to 25% of users to start)?

• Yes
• No

Note: For an incremental launch, we use React widgets to display dynamic content. We'll need at least 2 weeks of extra time to coordinate the content for this and work with your engineer. Learn more about our process for dynamic content. If your launch plans change, notify CAIA of the change as soon as possible so we can talk about how that will impact the timeline.

If you are releasing incrementally:

• What dates do you anticipate starting and ending your incremental launch? Enter dates
• What is the name of your engineer who will build the React widget? Name

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

• Design intent
• Midpoint review
• Staging
• None. This initiative isn’t going through the collaboration cycle.

Collaboration cycle ticket

If you’re going through the collaboration cycle, provide a link to your Collaboration Cycle Request:

• Hyperlinked Ticket Number: Collaboration Cycle for Identity, Login, Guardian Access #96978

Next steps

• Review the remaining next steps in the VFS team tasks section here.
• If you also need engineering support from the public websites team, fill out their intake request form as well: Open a public websites intake request
• If you're requesting a page/URL redirect, a URL change, or a vanity URL, submit an additional request for this work: Open a redirect, URL change, or vanity URL request
• If you're creating an experimental design, also contact the design system team: Read more about experimental designs
  Suggest an addition or update to the design system team
• If you're requesting a11y support for usability research, submit a research support request next: Open an a11y research support request
• If you are requesting content support, please share your content source of truth (preferably as a SharePoint document).
• Please don't close this intake when work is complete - CAIA will close and track

[aprocik1]

@laurwill will be the content lead on this work, likely collaborating with Danielle and Jamie.

[kristinoletmuskat]

Hey @claytonzook, thanks for submitting this! I'll be supporting as the IA on this work, and I am new to understanding the guardian experience. I saw that you all have plans to conduct baseline research on this -- would you be able to add Laura and I to some of those sessions as observers?

I also see a few diff dates for your next steps -- when is your midpoint scheduled for?