Open jeana-adhoc opened 7 months ago
Update: Team is aiming to go live with this form the week of February 5-9. I will sync with Jeana on 1/29 and aim to have copy by 1/30.
I reviewed the updated language that @jeana-adhoc is working on. Jeana and I talked through a few more tricky content challenges related to third-party representatives who can sign. Jeana is asking the stakeholder a few more follow-up questions.
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
Insert name and/or GH handle
About your initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
insert description
What's the nature of your initiative and desired outcomes?
We have already worked with @megzehn on content writing/review for our stand alone form 21-0966. Since then, we needed to add a new flow that allows an even easier/faster submission of a form. Also, during that time, I provided CAIA with a document that outlines inconsistencies we noticed in ITF language across VA.gov. That work is being done here.
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 are close to shipping. We've already gone through staging review, and even with these changes, we won't need to go through staging again. But I need a second set of eyes on this content, and to help guide us on how to make the language more consistent with other Intent to File language across VA.gov
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply.
Collaboration cycle ticket
If you’re going through the collaboration cycle, provide your ticket number and link:
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.
Next steps
@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.Tasks