[CAIA Intake] My HealtheVet: Sign-in / access audit

[sterkenburgsara]

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) team.

About your team

• Team name: Cartography (though this is portal-wide)
• OCTO product owner: Patrick Bateman / Samara Strauss / others?
• Product name: My HealtheVet on VA.gov
• Product manager: Wes Rowe
• Designer(s): Sara Sterkenburg, Florence McCafferty, Jonathan Nelson
• Slack channel: #mhv-on-vagov-cartography-team
• Dedicated content writer on your team (if you have one):
• Dedicated a11y specialist on your team (if you have one):

About your initiative

Some updates to sign-in process related to the sunsetting of the MHV credential recently happened on MHV National Portal. We are now unsure if some URLs / links / buttons in our sign-in and access-related alerts on VA.gov are still working and make sense since we were not a part of that QA process.

We want to make sure that 1.) all sign-in routes that are offered from the national portal work fine and that 2.) all sign-in processes on VA.gov related to My HealtheVet also work find & any "go back" links to the national portal make sense and work as expected.

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
• [x] Updating an existing form or tool
• [ ] Translating a form or tool into Spanish
• [ ] Adding new unauthenticated content to VA.gov
• [x] Updating existing unauthenticated content on VA.gov (maybe?? Not sure yet)
• [ ] Something else: auditing & fixing auth sign-in alerts if/when problems are surfaced

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

Tell us briefly about your work and the outcomes you’re aiming to achieve.

• document user flows for all sign-in flows related to My HealtheVet access (either VA.gov or national portal)
• Identify problems
• ticket follow-on work to fix the problems, including re-writing content where needed

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.

• Mural with previously documented flows for auth sign-in

Collaboration timeframe

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
• [x] 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.

Enter your description here

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

• [ ] Yes

• [x] 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
• [x] 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:

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).

[sterkenburgsara]

cc @laurwill @sterkenburgsara

[sterkenburgsara]

Spinning up IA child ticket here to document user flows for various sign-in patterns (post 9/19/24 launch of updates).

[sterkenburgsara]

See related slack thread with identity team here