aagosto90 commented 4 months ago

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

Team name: Health Enrollment
OCTO product owner: Patrick Bateman
Product name: 10-10EZ
Product manager: Heather Justice
Slack channel: [1010-health-apps](https://dsva.slack.com/archives/CMJ2V70UV)
Dedicated content writer on your team (if you have one): N/A
Dedicated a11y specialist on your team (if you have one): N/A

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
[x] 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
[ ] Something else: insert description

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

We're making some content and user flow updates to the toxic exposure questions on the 10-10EZ form as a result of usability testing we did with Veterans. These changes will provide better context for how to complete the questions and will only ask questions that may be relevant based on the user's service dates. We will make the same changes on the 10-10EZR in future sprints.

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?

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've completed research, research synthesis, follow-up discussions with stakeholders, and design/user flow updates. We're at the point where we need content feedback from CAIA and then our developers will implement the changes.

Will you release this new product incrementally (for example, release to 25% of users to start)?

[x] Yes
[ ] No

Note If you checked yes: Incremental launches require dynamic content. You'll need to ask your developer to build a React widget and provide CAIA with the ID code. CAIA will provide widget content and add the widget to your product’s static page. Please refer to this GitHub page for more information.
[x] I acknowledge that if I change the launch to be incremental, or change it from incremental to 100%, I must notify CAIA of this change as these additional steps will impact deadlines.

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.

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

[x] Post a link to this issue in the #sitewide-content-sitewide-content-accessibility-ia slack channel and tag @Naomi Eke, and we’ll then 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.
[ ] 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
[ ] If you're requesting a page/URL redirect, a URL change, or a vanity URL, submit an additional request for this work: Open a redirect, URL change, or vanity URL request
[ ] If you're creating an experimental design, also contact the design system team: Read more about experimental designs
Suggest an addition or update to the design system team
[ ] If you're requesting a11y support for usability research, submit a research support request next: Open an a11y research support request
[x] If you are requesting content support, please share your content source of truth (preferably as a SharePoint document).

aliyahblackmore commented 3 months ago

Tracking content status update here ahead of being OOO (cc: @strelichl @aagosto90 )

As mentioned, I started to review TERA update designs this week and flagged questions on the screens. I'll need to return to these areas of content when I'm back in office.

On the TERA what to know screen - content adjustments are there. Angela has a question for their SMEs about whether the branching logic impacts the training or serving on active duty service post. Are there screens that are only applicable to deployment vs. training/active duty service? Link to Figma comment
Showing dates on screens - research showed that some Veteran were curious about the dates for certain efforts/operations. The branching logic helps to clarify this, as questions will only show based on their service dates, but I'm curious about whether showing specific date ranges provides further clarity. I think that if there are dates on one screen, that should be consistent throughout. TBD based on conversations with Angela in content sync. Figma comment here
Gulf war screen split - the content here is ready and the headers align with the 526 headers. The outstanding questions here is if their PO and SMEs are fine with this split (this will happen for some applicants) given there is one Gulf War question on the PDF version of the form. Figma comment here
"Present" in header for Gulf War dates after August 1990 screen - All other content on this screen is ready. Outstanding question here about using "to present" in the header. Figma comment here
Operations screen - question here about the sentence "This does not have to include combat service" Curious about what SMEs want Veterans to consider when selecting yes/no. Figma comment here And question about listing only the years vs. listing the month/day/year range. Figma comment here
Agent Orange screen - is the "c-123 airplanes" point no longer necessary? It's not in the new design from the product team, but it's on the PDF and the live version of the form. Figma comment here
Other toxic exposures screen - the design updates included during "active duty service or training" only, but I'm wondering if this screen is asking about any other toxic exposures while deployed OR during training or active duty service? I adjusted the screen content and question in alignment with this, but we can adjust if SMEs share that they only want to know about exposures that may have happened during training or active duty service. Figma comment here

aliyahblackmore commented 3 months ago

Tracking updates here after our weekly design/content sync:

The product team shared (7/26) that they're going to start the dev work on the branching logic (so showing questions based on service dates) and if that's all done while I'm OOO, they're going to re-launch the toxic exposure section with only the branching logic (so showing screens based on service dates). And outside of the first toxic exposure screen and the Gulf War screen, the other questions that are already in production will remain the same. Their goal is to release this in phases and unblock their work as they wait for some SME answers to some questions on the new screens/designs. They're not sure if the dev work will be done before I'm back, but that's their goal and they'll launch if so.

I shared with the designers during our sync today that I think that this is fine from a content perspective as they're leaving the questions as is, but offering a solution to one of the larger pieces of Veteran feedback around dates.

When I'm back online, their hope is to have all of the SME feedback on the new designs/content review and then they'll move forward with updating the form with the new content (and the branching logic).

cc: @strelichl

UPDATE 4:45pm ET:

Product team needs to think more about the branching logic - because they'd need all service dates (start and end) for the branching logic to work.

strelichl commented 1 week ago

This work might be done, Heather will check with the team

aagosto90 commented 1 week ago

Hi @strelichl ! This ticket is complete. Is the expectation that the designer closes the ticket? Sorry if I missed that step!

aliyahblackmore commented 1 week ago

Also jumping in here to add that the content work wrapped up in August! Apologies for not tracking that update in this ticket.