[CAIA intake] Content Request from 10-10 Health Apps - Registration Only

[hdjustice]

About your team

• Team name: 10-10 Health Apps
• OCTO-DE product owner: Patrick Bateman
• Product manager: Heather Justice, Alex Seelig
• Designer: Jessica Stump, Angela Agosto
• Accessibility specialist: n/a
• Content writer:
• Slack channel: 1010-health-apps

CAIA Support Request

Describe what you need in a few sentences:

We are incorporating a "Registration Only" pathway into the 10-10EZ for Veterans who do not qualify for health care enrollment. We need help to translate some of the directive legal verbiage into plain language.

Which are you doing?

• [ ] Launching a new page, tool, form, or app
• [X] Making changes to an existing page, tool, form, or app

Types of Support

What areas does your team need support in? Check all that apply.

Content

• [ ] Collaboration on content written by your team’s dedicated content writer
• [X] Collaboration on content if your team does not have a dedicated content writer

  Accessibility

• [ ] Accessibility review of wireframes and/or prototypes
• [ ] Accessibility issue (general request)
• [ ] Accessibility PDF review request
• [ ] Accessibility user research support (submit a separate, additional request)
• [ ] DST component or pattern
• [ ] Something else

  IA

• [ ] User Flows
• [ ] Page placement
• [ ] URLs
• [ ] Breadcrumbs and Left Nav placement
• [ ] Redirects

  Multilingual content

• [ ] Translating content

Timeframe

We guide and work alongside teams across nearly every OCTO digital product. We also work with partners across VA to lead content migration and manage all unauthenticated content on VA.gov. And we're always working to expand the VA.gov content style guide and our IA and accessibility documentation. We need to prioritize all intake requests based on our overall workload and VA and OCTO priorities.

Tell us about your product's timeline. And we'll work with you to meet timeline needs as best we can.

Have you worked with CAIA before?

• [X] Yes
• [ ] No

What's your team’s next step and its timing?

• Our next step is Decide on a workflow or two, start on designs
• Provide date if available: December 2023

Timing for your next step:

• [ ] Next week
• [ ] This month
• [ ] Next month
• [ ] This quarter
• [X] Next quarter
• [ ] 6 months
• [ ] 1 year

Is this timing related to a specific event or Congressionally mandated deadline?

• [ ] Yes
• [X] No

If you're conducting research, when is that starting?

Provide date if available: xx/xx/xxxx

• [ ] Next week
• [ ] This month
• [ ] Next month
• [ ] This quarter
• [X] Next quarter
• [ ] 6 months
• [ ] 1 year

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

• [X] Yes
• [ ] No

Note: If you checked yes, we’ll reach out to discuss details about the content in the react widget (we use these widgets to display entry points for new products to a certain percentage of users who visit our static pages).

When do you expect to launch your product to 100% of users?

Please provide an estimated date so our team can create other relevant tickets.

• We expect to launch our product to 100% of users on: Q2 2024

Collaboration Cycle

Will this work be going through the Collaboration Cycle?

• [ ] Yes
• [X] No

If no ...

• Skip to the supporting artifacts section, below.

If yes ...

Please provide the link to your Collaboration Cycle ticket:

Please check all of the phases in the Collaboration Cycle you have completed:

• [ ] Design Intent
• [ ] Midpoint Review
• [ ] Staging

For planning purposes, please check all of the phases in the Collaboration Cycle you feel you might need CAIA support and guidance:

Design Intent

• [ ] Accessibility
• [ ] Content
• [ ] IA
• [ ] Translation
• [ ] Already completed, no assistance needed
• [ ] Unknown at this time

  Midpoint

• [ ] Accessibility
• [ ] Content
• [ ] IA
• [ ] Translation
• [ ] Already completed, no assistance needed
• [ ] Unknown at this time

  Staging

• [ ] Accessibility
• [ ] Content
• [ ] IA
• [ ] Translation
• [ ] Already completed, no assistance needed
• [ ] Unknown at this time

Supporting artifacts

Please provide links to supporting artifacts as available.

• Initiative Brief: Registration Only Initiative Brief
• Wireframes: Registration Only wireframes
• Business Logic wireflow
• User flows: Same screen as Wireframes above
• Prototype or mockups:
• If this is in Sketch, which version or specific page should we focus on?
• Content source of truth:
• Research plan:
• Any epics/issues that may be helpful:
• Link to testing accounts (please do not paste them in this ticket):

Additional Support: Collaborative Sessions

Have you already worked with someone from OCTO leadership?

• [ ] Danielle
• [ ] Beth
• [ ] Mikki
• [ ] Martha

How do you plan to work with us on this request?

• [ ] I’ll take this to Beth or Danielle’s office hours.
• [ ] I’d like to schedule time to talk about this.
• [ ] Let’s work async and meet as needed.
• [X] Schedule a kick-off call with your team and CAIA for your project (Recommended)

Accessibility Help in Slack

The #accessibility-help channel in the DSVA Slack, is also available to you as a resource. Everyone is welcome to ask questions or get help from our a11y (accessibility) specialists. Tag @Terry Nichols to get a11y help asap.

Next steps

Once you’ve submitted this ticket, please post a link to this issue in the #sitewide-content-ia Slack channel and tag @Terry Nichols.

• If you also need engineering support from the Public Websites team, fill out their intake request form.

• If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a Redirect, URL change, or vanity URL request

  • If you are creating an experimental design, please also contact the DST.

• If you are requesting a11y support for user research, please complete this form, next.

[jessicastump]

Per the update in the collab cycle original request - this content request has changed slightly. The updated user flows and designs with alert content and adjustments are linked below:

• User flows
• Figma designs & drafted content

cc @aliyahblackmore

[strelichl]

@hdjustice following up with our order of operations for this: Since we have the ongoing OHI, 10-10D, and CHAMPVA work to move forward too, our plan is for Aliyah to focus on supporting docs first and then turn to this registration piece. We’ll be in touch as things progress!

[aliyahblackmore]

Hi @strelichl - just flagging that the OHI 1010D and CHAMPVA work is part of the IVC forms team, not the 1010 health apps team :)

[jessicastump]

@aliyahblackmore - for when it's time ;) --- I've updated the Figma page setup with what we learned working on the CG form: how the content components are structured and the source of truth setup, so it is all ready to go for you to edit directly in Figma. Also added a section for design decisions and you will find a black box with some background and links to tickets/Mural boards/etc. When ready, let me know if you have any questions or we can review in a future weekly content sync.

[aliyahblackmore]

Awesome! Thanks so much @jessicastump!!

[aliyahblackmore]

Updates here @jessicastump @strelichl

I wrapped up my review of the auth and unauth registration only designs (link to Figma).

Outline of content recommendations:

• As discussed, this is an MVP that the product team is using to collect data about the reg only path ahead of VES being ready. We are okay to revisit static page and form intro page updates in the future.
• Auth applicants - I recommended using a header ("Personal information") to clarify that there are two tasks on the screen. I flagged that the product team can confirm the "two things" approach with the design system given more recent accessibility feedback for "one thing" per page.
• We decided to leave "apply for" in the question to align with the PDF language and because even if someone only wants to register, they still need to fill out the entire EZ application. We can revisit this after any testing/applicant feedback.
• I flagged the designers use of "health care..." vs. "health services" (used in the PDF) -- they're going to leave in "health care" for now and have their SMEs confirm this when the do a review.
• In the additional info component with more details about the full medical benefits package - Jessica pulled that language directly from the VA.gov health benefits page and included the priority group info specific to folks with a 10-40% disability rating. I only added 1/ a sentence that explains what priority groups may help determine about their care ("..how much you'll pay...") and 2/ a sentence in the priority group 3 bullet point that clarifies that other factors aside of their disability rating may determine their placement in this priority group (...like details about your military service history...").

And as we chatted in our design/content meeting, content review was only needed only the new content screens specific to registration only. Your other design changes were only to move screens for unauth users to ensure the reg only path doesn't impact the form in any way.

[jessicastump]

Adding here from Slack convo too :) -- in case it needs to be part of this ticket or another request, during demo we received feedback to remove the "I'm not sure" option that was added during the final content/design review before development. - Link to Figma section

[aliyahblackmore]

Just an update here:

• Jessica shared more context about this in our weekly design and content sync.

• The team already talked about recommending that the applicant select "enroll" or give HEC a call if they're not sure. But they shared that recommending that they enroll would guide the Veteran towards an answer. So they'll include instead recommend that the Veteran give HEC a call.

• If someone calls and says they're not sure which option to select, product team shared that HEC should be able to answer any questions if the applicant isn't sure.

The content recommendations are in Figma. We moved the info out of hint text and place it under the first paragraph as a note. And I flagged that the team should confirm with their SMEs that the content is okay.

[aliyahblackmore]

Update here (tracking fro Slack - cc: @jessicastump):

• Product team shared today that they're launching MVP Monday.
• They got new feedback today and they'll need to make some updates before MVP - change to the additional info component and change to the information alert. They needed some quick turn around feedback.

The feedback and changes

• HEC shared today that Veterans can't register by phone. They can register by mail or in person and can call HEC to get help or ask any questions. The team removed the phone option from the information alert and moved the contact information to the bottom.
  • Content adjustments - I moved the contact information up on the information alert if someone only wants to register. Since the footer of the form includes contact / need help information, moving this up may help to distinguish that if they need help with reg only they should call HEC specifically. We can revisit post MVP based on feedback/data.
• HEC SMEs asked the designers to move the additional info component that's on the question screen above the "Note"
  • I recommend leaving it after the radio buttons (comment). The content before the question would get quite long if someone expands that component. But if you all, as the designers, think that it would actually be best between the body text and note, that is okay for this MVP. All in all, we should plan to revisit this once you all gather feedback and data about this reg-only path.

Feedback is tracked in this section of Figma and these updates are ready for the team to get their SME approval before their MVP launch.

fysa @strelichl

[aliyahblackmore]

Updates here (cross posting from Slack notes)

• On the screen with the question, we decided to leave the additional info component above the question. And we moved the "Note" after the radio button -if someone reviews the options and they’re not sure which option to select, the telephone number information is below. We can revisit this post MVP based on feedback.
• On the personal information screen (auth) - the designers changed the VA benefits hotline number to the Health Eligibility Center number. SMEs requested this change.
• MVP launch planned for next Monday.