Open marywang2 opened 8 months ago
Noting that this work is in the queue behind other IVC forms work so we'll pull in a11y when we're ready to pick it up!
From our sync 3/21:
And context from Mary:
@strelichl tracking updates here on the 10-7959c (OHI) form.
Jamie confirmed yesterday that this is the Figma file that I should work form. In section "Working file for CAIA comments_4/22/24"
Noting I updated the name of this ticket to make clear that this is for the OHI cert form
Hi @laurwill @strelichl @aliyahblackmore! We would like to schedule staging review for OHI. Would you be able to take another content review pass before we schedule it? (Also please let me know if I should open a separate ticket). Thank you! cc @jamiefiore
Also wanted to note that the react widget ID is: form107959c. Please let me know if I should open a new ticket for the content creation or if it is fine to track here. @laurwill @strelichl
Update here:
As requested, I reviewed the confirmation screen and email content. Comments/adjustments are in Figma. :link:OHI link
And as we chatted earlier today, I'll hold on a second content review of the full OHI flow because you all mentioned that you got new information from your VA partners yesterday and may make further design adjustments.
Update here
Mary and Jamie joined office hours to talk about FMP reg and other emails.
We confirmed that we'll move forward with making the CAIA content adjustments to the confirmation emails now. The adjustments across 1010D/OHi/CHAMPVA claim, where applicable, will align. And when CAIA has standard VA notify content, we'll circle back if there are any future adjustments that need to happen.
We confirmed on the call that we'll move the contact information up under "What to expect next" and remove the header "How to contact us about your application."
And we confirmed that we'll use the header "What to do if you need to submit supporting documents" for the supporting documents" information, where applicable.
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
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?
Our team will be digitizing existing forms for the CHAMPVA program and Foreign Medical Program, among other Veteran and Family Member programs. We would like CAIA's support in reviewing content changes or changes wtih accessibility impacts.
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?
Early user flows
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