[CAIA intake] Content review for two existing eCheck-in pages

[benbrasso-agile6]

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

Use this ticket to start collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.

Note: If you’re already partnering with us on an initiative, you don't need to fill out this request form. If you don’t have access to your initiative’s CAIA epic, post a message in the #sitewide-content-accessibility-ia slack channel and tag @Terry Nichols and @Lily Strelich.

About your team

• Team name: Check in
• OCTO product owner: Kay Lawyer
• Product name: Check in
• Product manager: Lori Pusey
• Slack channel: check-in-experience
• Dedicated content writer on your team (if you have one): shared
• Dedicated a11y specialist on your team (if you have one): shared

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

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

How might eCheck-in change when a BT eligibility API exists?

Userflow

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.

Content updates to two existing pages in our web app. 1) Would you like to file for BT page, and 2) Check in complete page.

This is future work; release date end of 2024.

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 your ticket number and link:

• Ticket Number: xxxxxx

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.

Note: Attending design office hours to understand if using the check eligibility pattern is being used correctly.

Content source of truth:

• Variations of "Would you like to file for BT" page
• Variations of "Check in complete" page

Next steps

• [x] Post a link to this issue in the #sitewide-content-sitewide-content-accessibility-ia slack channel and tag @Terry Nichols. We’ll reply within 24 hours to acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.
• [x] Review the remaining next steps in the VFS team tasks section here.

Tasks

### VFS team tasks
- [x] **If you are requesting content support**, please share your content source of truth (preferably as a SharePoint document).

[strelichl]

@benbrasso-agile6 for our planning purposes: there will be three total pages for review including this "check in with your smartphone" page (#80574), is that correct? And for timing, looks like the smartphone page will need review before the other two?

[benbrasso-agile6]

I would prioritize #80754, which should ideally go out with our product release. That one is more "writing/editing" vs. "reviewing" since that page is owned by CAIA (I think), but we're happy to collab and do a first draft if that's better. Kickoff is probably best for this one.

Then, #80519 is very much not a priority, but that is reviewing 2 pages; 1 page with 3 alert-content variations, the other page with 2 body-content variations.

[benbrasso-agile6]

@loripusey I just dropped the HCE label so it doesn't appear in our EOS reports

[loripusey]

ok, I guess, those reports are causing us to change how we do things not in a good way