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.
*Dedicated content writer on your team (if you have one):N/A*
*Dedicated a11y specialist on your team (if you have one):N/A*
Your CAIA team:
Filled out by CAIA
IA:
Content:
Accessibility:
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
[X] Something else: updating authenticated content in the bot in the context of escalating a veteran to a live chat service from a prescription refill user experience
What's the nature of your initiative and desired outcomes?
`we are aiming to improve on action of sending Veterans to the live chat service through chatbot with an updated button UI as a clearer call to action. We have multiple contextual scenarios to consider when the live chat service both is and is not available; We're looking for content guidance on what has been shared as "standard to include" from working with the MHV team, while considering the impact of this content on the specific product goal of directing a Veteran to the live chat service.
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.
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.
We're at the beginning of sprint 2 of 4 sprints. we are hoping to have content alignment by the end of the third sprint at the latest.; approx. 3-4 weeks from now
Will you release this new product incrementally (for example, release to 25% of users to start)?
[ ] Yes
[X] No
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.
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
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
Your CAIA team:
Filled out by CAIA
Your Initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
What's the nature of your initiative and desired outcomes?
`we are aiming to improve on action of sending Veterans to the live chat service through chatbot with an updated button UI as a clearer call to action. We have multiple contextual scenarios to consider when the live chat service both is and is not available; We're looking for content guidance on what has been shared as "standard to include" from working with the MHV team, while considering the impact of this content on the specific product goal of directing a Veteran to the live chat service.
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.
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?
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're at the beginning of sprint 2 of 4 sprints. we are hoping to have content alignment by the end of the third sprint at the latest.; approx. 3-4 weeks from now
Will you release this new product incrementally (for example, release to 25% of users to start)?
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply.
Next steps
Suggest an addition or update to the design system team