Open mmiddaugh opened 5 days ago
FYDA @mnorthuis
Note for CAIA: we want to look into the reasoning for linking to the page rather than tool (online vs PDF?). A will investigate.
@mmiddaugh, thanks for submitting this intake ticket.
Shannon recently asked us to update the About VA Form 21-0781 page in this related intake ticket. Shannon and SMEs reviewed the page before it was published, so it should be accurate.
That said, I agree with the Medallia feedback--this experience is very confusing.
It's my understanding that the online VA Form 21-526EZ includes the outdated VA Form 21-0781. The only way for a Veteran to submit an up-to-date VA Form 21-0781 is to complete a PDF. Correct me if I'm misunderstanding!
If that's true, I think this may be a product team decision. Should we update the online VA Form 21-526EZ to match the up-to-date VA Form 21-0781? Or, should we remove the link to the online VA Form 21-526EZ on the About VA Form 21-0781 page?
cc @jinaryu @katherine-fung @shannonkford
Having an H3 for the online tool and an action link to it under an H2 heading stating that the pdf is recommended is conflicting. If the online form does not fully support the 0781, we shouldn't be referencing it as an online tool for this form.
My recommendation would be to remove the online tool heading and action link and replace it with general content about the what they can/can't do within the online 526. A text link to the 526 could still be provided in this, but it wouldn't be the primary CTA on the page - the focus would be on the recommended downloadable pdf.
A couple other suggestions:
Thanks @mmiddaugh @mnorthuis @aprocik1!
I'm in the process of drafting updates to the page:
@shannonkford - given Veterans' negative feedback via Medallia, Mikki's guidance and Michelle's request, can we communicate to the SMEs that we need to make these updates?
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) team.
About your team
About 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?
Goals
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.
Enter your description here
Will you release this new product incrementally (for example, release to 25% of users to start)?
[ ] No
Note: For an incremental launch, we use React widgets to display dynamic content. We'll need at least 2 weeks of extra time to coordinate the content for this and work with your engineer. Learn more about our process for dynamic content. If your launch plans change, notify CAIA of the change as soon as possible so we can talk about how that will impact the timeline.
If you are releasing incrementally:
Enter dates
Name
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 a link to your Collaboration Cycle Request:
Next steps
Suggest an addition or update to the design system team