[CAIA Intake] Benefits - Dependent Experience Team: Review of 686c/674 Form Updates

[steele-lm]

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

• Team name: Benefits - Dependent Experience
• OCTO product owner: Emily Theis
• Product name: 21-868c and 21-674 online form flow
• Product manager: Laura Steele
• Slack channel: #benefits-dependents-management
• Dedicated content writer on your team (if you have one): none
• Dedicated a11y specialist on your team (if you have one): none

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
• 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?

Veterans are submitting online 686/674 claims that generate outdated pdf claim forms, are missing information, and/or contain information that is no longer required. Downstream systems (RBPS) need to offramp these claims for manual processing, which delays the Veteran's benefits. Our desired outcome: Veterans submitting online 21-686c and 21-674 claims can trust that their submissions include all the required information to ensure efficient processing.

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
• No
• I’m not sure

Where are you at in your timeline?

We have initial designs drafted, and we completed the Design Intent on 1/30/2024. We are currently working to incorporate feedback from Design Intent.

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

• Design intent (1/30/2024)
• Midpoint review 2/23/2024
• Staging
• None. This initiative isn’t going through the collaboration cycle.

Collaboration cycle ticket

If you’re going through the collaboration cycle, provide your ticket number and link:

• Ticket Number: Collaboration Cycle for [Benefits Dependent Experience, 21-686c/674, Critical Form Updates] #74059

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.

• User flow 686c Form Simple Flow (and future changes)
• Figma
• Initiative Brief
• Form Tool Page
• About 21-686c
• About 21-674

Next steps

• Post a link to this issue in the #sitewide-content-sitewide-content-accessibility-ia slack channel and tag @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.
• Review the remaining next steps in the VFS team tasks section here.

Tasks

VFS team tasks

Beta Give feedback

1. 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
2. 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
3. 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
4. If you're requesting a11y support for usability research, submit a research support request next.
   Open an a11y research support request
5. If you are requesting content support, please share your content source of truth (preferably as a SharePoint document).

CAIA operations

Beta Give feedback

1. Initial Review - @coforma-terry and @strelichl
2. Attend Kickoff 2/21/2024 (Terry and Lily)
3. Attend Midpoint Review 10:30 a.m. ET Friday, 2/23/2024

CAIA a11y tasks

Beta Give feedback

1. Attend Kickoff 2/21/2024 (Sara, Evan and Terry)
2. Design Review - Figma Designs V2 (option before Midpoint) @EvanAtCoforma
3. [a11y Design Review] Benefits - Dependent Experience Team: Review of 686c/674 Form Updates #76841
   6 of 6
   sitewide CAIA sitewide accessibility +2
   

   
4. Attend Midpoint Review 10:30 a.m. ET Friday, 2/23/2024 (Optional) @EvanAtCoforma
5. Share link to accessibility review (completed prior to Midpoint) @EvanAtCoforma
6. Weekly Design Sync: @EvanAtCoforma requested to be added weekly design sync with Dependent Management and Julie Strothman
7. Review Brian's feedback from Midpoint in CC ticket @EvanAtCoforma
8. Sync with Team post midpoint re: Staging Prep Option
9. Assist team with Staging Prep (as needed) CONNECT STAGING ARTIFACT TICKET TO THIS TASK LIST

CAIA content tasks

Beta Give feedback

1. Attend Kickoff 2/21/2024 (Katherine and Lily)
2. Requested content source of truth (Sharepoint) of text within the tool in KO 2/21/2024
3. Attend Midpoint Review 10:30 a.m. ET Friday, 2/23/2024 (Optional)
4. Remove timeframe from 686 confirmation screen #76831
   sitewide CAIA sitewide content +2
   

   
5. Review form updates #76923
   sitewide CAIA sitewide content +2
   

   
6. Update view / change dependents page #80538
   sitewide CAIA sitewide content +2
   
7. Review confirm and reminder emails #85759
   sitewide CAIA sitewide content +2
   

   

CAIA IA tasks

Beta Give feedback

1. Attend Kickoff 2/21/2024 (Jenny)
2. Attend Midpoint Review 10:30 a.m. ET Friday, 2/23/2024 (Optional)

[steele-lm]

cc @ajialeilani and @jstrothman

[ajialeilani]

Hi @strelichl @coforma-terry I'm curious about what kind of timeline we can expect from the review. We should have finalized designs in Figma a week from now

[strelichl]

@ajialeilani Thanks for that background, let me take a look on our end and I'll follow up tomorrow

[strelichl]

@ajialeilani As a first step, we'd like to set up a kickoff call to go over this work (and check in on the status of 686 work overall, I know we have a few other related tickets on our board). We have availability 2/21 at 12:00-12:30 and 12:30-1pm Eastern, would either of those work for you?

[ajialeilani]

@strelichl 12-12:30 on 2/21 would be great—thank you.

If I have more specific questions before then, can I ask them here or is it better to wait until office hours?

[strelichl]

@ajialeilani Here works! If it ends up being complicated I'll make sure the right person can be available during office hours to answer then.

[steele-lm]

@ajialeilani Takeaways from CAIA kickoff:

• Send invite to CAIA for Midpoint review scheduled for 2/23.
• Create Content Source of Truth and post to SharePoint, so CAIA can review all text in one place.
• Confirm how the interview-style online form handles the additional/supplemental forms outlined in paper form.
• CAIA may have some feedback on areas outside the purple areas in Figma.

[ajialeilani]

@strelichl forwarded the invite to midpoint. Let me know if you don't see it for some reason.

[strelichl]

Noting from kickoff 2/21:

• Team will forward invite to midpoint review
• Team will send content source of truth for CAIA to start review

[EvanAtCoforma]

Hey @steele-lm and @strelichl , the accessibility review for the Figma prototypes is complete. Please let me know if you have any issues with the feedback so I can provide clarification. Thanks!

[ajialeilani]

Hi @strelichl @coforma-terry @aprocik1 do you have an idea of when you'll be able to start review? I've marked off the portions of the mockup still awaiting answers from SMEs with red annotations, and I'll be integrating midpoint feedback today and tomorrow.

I also heard about the possibility of keeping the source of truth in Figma rather than creating a Sharepoint document if your team is provided edit access to the Figma file. Is that a possibility here?

cc @juliepedtke

[aprocik1]

Thanks for following up, @ajialeilani. Our goal is to start reviewing your form next week. We've talked about content sources of truth as a team with Beth and Danielle. For smaller projects, we're exploring Figma as a source of truth. Since this is a bigger project, we'd like to use a SharePoint document to record content recommendations for future reference. Let me know if that works for you.

[ajialeilani]

@aprocik1 Thanks for your update. That makes sense—it is a bit, meandering form. I'll have a Sharepoint doc ready for you by Monday.

[ajialeilani]

Hi @aprocik1 do ya'll have a template for a Sharepoint SoT? Something that covers error messages and other dependent states?

[ajialeilani]

Thanks for looking these over @katherine-fung—

1. SSN and where was the child born should have been separated. I've made the correction and resolved the comment.
2. That header in the PDF refers to question 11 " OFFICIAL BEGINNING DATE OF REGULAR TERM OR COURSE," which Kayce confirmed to be "Date of whatever term they started." So I understand the headings in financial info to be "First year you attended school" and "The following year."
3. I'm still working on the flow. I'll ping you when it's ready.

[ajialeilani]

@katherine-fung @aprocik1 are either of you opposed to me updating the H1/breadcrumb to

File a claim to add or remove dependents on your VA benefits

and putting in a request with Lighthouse to have the title in the Claim Status Tool (eventually) align with that?

[ajialeilani]

Hi @katherine-fung @aprocik1

I reviewed the confirmation and reminder emails that go out through VA Notify in connection with 686c/674. I've added changes to the bottom of the Source of Truth doc.
I'll post them here as well with screenshots of the original content.

Thanks!

Confirmation email

[H1] We’ve received your claim to add or remove dependents on your VA benefits

Dear ((first_name)),

Your claim to add or remove dependents on your VA benefits has been submitted for review. You don’t need to do anything unless we send you a letter asking for more information. Once we process your claim, we’ll mail you a letter with our decision.

You can also check the status of your claim online.

[Color link] Check the status of your claim online

Note: It may take 7 to 10 days after you apply for your claim to appear online.

[card]
Application details:
Claim to add or remove dependents on your VA benefits (VA Forms 21-686c and/or 21-674)
Date submitted:
((date))
[end card]

Thank you,
VA

You’re receiving this email because you started an application on VA.gov. Please don’t reply to this email. If you need to contact us, visit va.gov or call 800-827-1000. We’re here Monday through Friday 8:00 a.m. through 9:00 p.m. ET.

Reminder email

[H1] You have an unfinished claim on VA.gov

Dear ((first_name)),

We’re writing to let you know that you have an application still in progress. Make sure you complete your application so we can properly process your request.

[Card]
Claim to add or remove dependents on your VA benefits (VA Forms 21-686c and/or 21-674)
[color link] Continue your claim
Application expires on ((date))
[end card]

Thank you,
VA

You’re receiving this email because you started an application on VA.gov. Please don’t reply to this email. If you need to contact us, visit va.gov or call 800-827-1000. We’re here Monday through Friday 8:00 a.m. through 9:00 p.m. ET.

cc @strelichl

[ajialeilani]

Hi @katherine-fung @aprocik1 ,

Couple of questions about 21-674 that surfaced during PDF mapping:

1. Can I add an "Other" with a conditional text field option to the benefit/program question to cover for if this list is not exhaustive:

2. Can you confirm which question in the PDF this question is equivalent to if any?

When did the student  enroll in the federal education program or school?

Screenshots for reference:

cc @strelichl @steele-lm

[katherine-fung]

Hi @ajialeilani!

1. Yes, it's fine to add "Another program" as an option to that question. In the conditional field, we can just say, "Briefly list any other programs..." (I don't think VA.gov uses parentheses to indicate singular/plural - I could be wrong about this, but it's also just fine to use the plural).

2. Looking at this now, I'm actually not sure. It might be trying to ask the PDF question 9c "Date payments began." Is there another question in the online form that asks when payments began? If there is already a different question in the online form that asks when payments began, then I'm really not sure why we put "When did the student enroll in the federal education program or school?" question in the online form. (and we could probably remove it??)

[ajialeilani]

Thanks @katherine-fung. I'll add "Another program" with the conditional field copy without parentheses. And we do ask for date payments began on the page following the programs checkbox group, so I'll remove the "When did the student enroll..." question.

[ajialeilani]

Hi @katherine-fung,

Here are the latest updates to a flow for adding one or more children. Let me know if this is decipherable / aligns with your vision.

cc @strelichl @aprocik1

[katherine-fung]

Hi @ajialeilani! The flow looks great, and aligns with the content source of truth. Thanks so much for working with us to implement the changes!!

[ajialeilani]

Hi @katherine-fung I added hint text to the school/program question (equivalent to 9A) to further distinguish it from the program/benefit question (equivalent to 9B) based on Brandi's feedback (pictured below). We were confused looking at this section during PDF mapping and concerned Veterans would be confused also. Let me know if this addition makes sense or if you think the labels are enough or if there are other opportunities to further clarify program/benefit vs. school/program.

cc: @strelichl @aprocik1

[katherine-fung]

Thanks for the clarification @ajialeilani! EDITED: In that case, do you think tweaking the question this way helps provide enough distinction?

What's the name of the school or trade program the student attends? (trying to incorporate the hint text into the question, and eliminate "federally funded" which might imply benefit name)

[ajialeilani]

Hey @katherine-fung ! I think that's an improvement. I'll update the mockups. Thank you!

[ajialeilani]

Hi @katherine-fung @strelichl - just wanted to check in to see if you'd gotten a chance to look at our reminder and confirmation email updates. If not, do you have an estimate of when you'd be able to review them? Many thanks for all your work on this!

[katherine-fung]

Hi @ajialeilani! I'm working on these emails today.

[katherine-fung]

Hi @ajialeilani,

Our team has reviewed and edited the confirmation email copy in the Sharepoint source of truth.

Our team is in the process of editing the template for reminder emails for VA forms. This will be ready well ahead of the planned August/Sept launch for the form updates. I'll let you know when we've edited the reminder email for the 686c/674.

cc @steele-lm @aprocik1 @strelichl

[ajialeilani]

Hi @katherine-fung @aprocik1 @strelichl -

Our SMEs let us know that we need to include a "Remarks" section to 674 for form parity, which I've added here. Would love your review / any recommendations you can make as far as how to handle "Remarks" or how other forms do so.

According to the PDF, the remarks section is specifically for section III overflow (which is already being captured), and if the student has school-related expenditures that could be deducted from their net worth (for Pension recipients). But it may be that we need to keep it more general to capture other Veteran remarks.

Thanks!

[aprocik1]

@ajialeilani, I just left you a Figma comment with a recommendation and question. Thanks for your patience!

[katherine-fung]

Hi @ajialeilani,

I've reviewed the reminder email content in the SOT doc, and left recommendations there. I've also tweaked the confirmation email copy to use the word "request" instead of "claim" as I mentioned on Slack.

https://dvagov.sharepoint.com/:w:/r/sites/vaabdvro/_layouts/15/Doc.aspx?sourcedoc=%7B2C65A672-BC39-48B3-A36F-F8047F571C11%7D&file=686c_674%20Content%20source%20of%20truth.docx&action=default&mobileredirect=true

For context, our team hasn't finalized a template for reminder emails yet, and we're not sure of our timeline for doing so. But we wanted to get you the copy for this specific email. At some point in the future, once we have a template, we may revisit all the reminder emails for VA forms to make sure they align with the new template.

Thanks for your patience, and let me know if you have any questions!

cc @aprocik1

[strelichl]

@steele-lm I understand you're planning to launch incrementally in August or September? Let me know if you have dates for that yet--I'd like to set up a sync for us to coordinate the process for widget work. Thanks!

[steele-lm]

@strelichl Thanks for reaching out! The launch of our phase 1 (backend) changes was delayed, so we're now tracking to have our phase 2 (front end) changes out sometime in the Sept/Oct time frame. How far out would you like to meet? I can stick a reminder on my scheduled to touch base at that point!

[strelichl]

@steele-lm If we could get a month of lead time that would be ideal. Thanks!

[ajialeilani]

Hi @strelichl —

We recently had to update our List & Loop patterns in our designs from the single page to the preferred multi-page pattern. These updates included some minor content changes, so we wanted to make you aware. Here are the pages where changes were made (content changes are mainly to H3 headers and button copy):

• Spouse's former marriages and Veteran's former marriages
• Add one or more children
• Add one or more students
• Remove a dependent who has died
• Remove a stepchild who left your household
• Remove a child under 18 who got married
• Remove a child between ages 18 and 23 who stopped attending school

cc @steele-lm