[CAIA Intake] Benefits Dependent Experience: CST Static Page Content Update Request

[steele-lm]

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: Benefits - Dependent Experience
• OCTO product owner: Emily Theis
• Product name: 21-868c and 21-674 online form flow
• Product manager: Laura Steele
• Slack channel: #benefits-dependents-management
• Dedicated content writer on your team (if you have one): none
• Dedicated a11y specialist on your team (if you have one): none

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

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

We would like to request that CAIA assist in adding the "Request to Add and/or Remove Dependents" form to the list of claim types on the CST page.

The Dependent Experience Team received a request from the VBA to remove the reference to a "1 week timeframe" for claim review on the confirmation screen for the 686/674 form flow. The proposed new copy will direct users to check the status of their claim via the Claim Status Tool, however, the landing page for the CST tool does not mention the "Request to Add and/or Remove Dependents" as one of the claim types that can be viewed within the tool.

To expedite this VBA request, we will be making the timeframe-related copy update to the confirmation screen independently of the broader updates we're making to the 686/674 for flow.

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?

We are working to finalize copy for the 686 confirmation screen with Kathrine Fung, and we anticipate releasing the update page with the new language by 3/19/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.

• Figma file of 686/674 design

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
- [ ] **If you also need engineering support from the public websites team**, fill out their intake request form as well.<br> [Open a public websites intake request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E)
- [ ] **If you're requesting a page/URL redirect, a URL change, or a vanity URL**, submit an additional request for this work. <br> [Open a redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=jennymayoco%2C+kristinoletmuskat%2C+strelichl%2C+FranECross&labels=sitewide+CAIA%2C+Sitewide+IA%2C+Public+Websites%2C+VA.gov+frontend%2C+Redirect+request&projects=&template=redirect-request.md&title=Redirect+Request)
- [ ] **If you're creating an experimental design**, also contact the design system team. <br> [Read more about experimental designs](https://design.va.gov/about/contributing-to-the-design-system/experimental-components-and-patterns#what-is-an-experimental-component-or-pattern?) <br> [Suggest an addition or update to the design system team](https://design.va.gov/about/contributing-to-the-design-system/suggest-an-addition-or-update)
- [ ] **If you're requesting a11y support for usability research**, submit a research support request next. <br> [Open an a11y research support request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=coforma-terry%2Cangelafowler82&labels=508%2FAccessibility%2C+sitewide+CAIA%2C+sitewide+accessibility%2C+CAIA-a11y-research&template=caia-a11y-research.yaml&title=%5BCAIA+A11y+Research%5D%3A+Team+name%2C+product+name)
- [ ] **If you are requesting content support**, please share your content source of truth (preferably as a SharePoint document).

### CAIA operations
- [ ] Initial Review - @coforma-terry and @strelichl 

### CAIA a11y tasks

### CAIA content tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-team/issues/77468

[steele-lm]

@ajialeilani and @jstrothman Just tagging you for awareness. 👍

[steele-lm]

@jacobworrell For awareness.

[strelichl]

Noting that Katherine and A will complete #76923 on form use cases before picking this up.

[strelichl]

Since this is in priority order behind #76923 I'm placing it in the Backlog for now