[CAIA Intake] OCTO Identity Team: Sign-in transition interstitial

[claytonzook]

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: OCTO Identity
• OCTO product owner: Samara Strauss
• Product name: Sign in Transition
• Product manager: Parker Baronowski or Joelle Wells
• Slack channel: #secure-sign-in-transition
• Dedicated content writer on your team (if you have one): kdmeg-bluetiger (note: OOO until Aug 20)
• Dedicated a11y specialist on your team (if you have one): none officially, so myself, and all of us unofficially

About 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
• [x] Adding new unauthenticated content to VA.gov
• [ ] Updating existing unauthenticated content on VA.gov
• [ ] Something else: insert description

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

have a prepared interstitial that we can use if we need to more aggressively communicate the need to transition credentials. This should show up as folks are signing in using one of the deprecated credentials

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?

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

As soon as possible, we want to have this interstitial ready to help help nudge folks to migrate to the modern credentials, to possibly go live by the end of October or early November

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

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.

• Product brief
• Figma design
  • Note: our content designer is currently working on content for this so this is just placeholder at this point, August 28, not content source of truth
  • Note: we also aren't sure at this time if this new page is going to be in unauthenticated or authenticated space which will definitely change the content needs. (the difference would be where folks see it in the sign in process)

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

### Tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/92586

[laurwill]

Hey @claytonzook , just confirming timing for this interstitial work—looks like you haven't yet gone to design intent, and the linked Figma is not ready for us to flow in and collaborate. Is that right? Happy to sync on this whenever you're ready.