Content Request (R&S Article) from Auth Profile Team for Personal Information Revision

[MarciMcGuireGCIO]

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

• [ ] Launching one or more new unauthenticated (static) VA.gov pages
• [ ] Making revisions to one or more existing unauthenticated (static) VA.gov page
• [ ] Launching a new online form, app, or tool on VA.gov
• [ ] Making revisions to an existing online form, app, or tool on VA.gov
• [X] Something else (please add details in the next question)

What do you need help with?

• [X] Content support
• [ ] IA support

We are adding personal information fields to the VA.gov Profile, and in our research sessions users had concerns about how the information would be stored, accessed, and used. This request is to create a Resources & Support article that addresses these concerns.

Supporting Artifacts

Please provide supporting artifacts as available.

• Link to product outline: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/personal-information/personal-information-revision/README.md
• Link to or attach user flows: N/A
• Link to prototype or mockups: https://www.sketch.com/s/ba254d92-3c3d-4eba-825d-d7f5bda35565/a/ygWOEPy
• Link to any epics/issues that may be helpful: N/A
• Meeting notes that may be helpful:
  • Notes from 2/9/2022 meeting between Danielle, Samara, Marci & Christina
  • Notes from 2/8/2022 meeting with Lexi. Michael, Samara, Marci & Christina

Will this work be going through the Collaboration Cycle?

• [X] Yes
• [ ] No

When does this work need to be done?

• Estimated launch date: Mid-April
• Estimated staging review date: Mid-March
• Content and IA work needed by: Mid-March

Do you plan to bring this to an upcoming content office hours session?

• [ ] Yes, benefit content office hours (Thursdays, 3:00 p.m. to 3:45 p.m. ET)
• [ ] Yes, health content office hours (Thursdays, 11:00 a.m. to 11:30 a.m. ET)
• [ ] Yes, unauth office hours (Mondays, 11:00 a.m. to 11:30 a.m. ET)
• [ ] No, but I'd like to schedule time to talk about this request
• [X] No, let's work asynchronously and meet if needed

Note: If we think this work would benefit from a collaborative session with you, we may ask you to bring it to office hours or set up a separate time to meet.

About your team

• Team name:
• OCTO-DE product owner: Samara Strauss
• Product manager: Marci McGuire
• Designer: Christina Geldanske
• FE engineer: Adam Whitlock
• Product/team Slack channel: #vsa-authd-exp

Next steps

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

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

[DanielleThierryUSDSVA]

Hi @MarciMcGuireGCIO. For estimated turnaround time on this one:

• I think we can finalize the content within the profile within issue #36962 by the end of next week or early the following. FYSA I'm going to be traveling and working flex hours Wed 2/23 through Wed 3/2 so will be slower to respond during that time.
• I'd like to aim for the end of March/beginning of April for the full R&S article due to capacity. Note that R&S articles don't go through the collaboration cycle since they're templatized. Just let me know if you have any questions around this - thanks!

[MarciMcGuireGCIO]

@DanielleThierryUSDSVA hey! Just reviewing dependencies and wondering if your timeline above is still valid. Thank you!

[DanielleThierryUSDSVA]

Hi @MarciMcGuireGCIO! I think my part of issue #36962 is complete, correct? And then for the R&S article, I just sent Samara a message to get her thoughts on whether we might want to pause on that for now. Will post back the result of our discussion, thanks!

[MarciMcGuireGCIO]

Hi @DanielleThierryUSDSVA! I'm going to loop @cgednalske in because I know you two have had several conversations.

Christina - is there any additional content you need for Personal Info, other than the R&S article and URL? Thanks!

[MarciMcGuireGCIO]

And @DanielleThierryUSDSVA thank you for sending that info to Samara!

[cgednalske]

Hi @MarciMcGuireGCIO and @DanielleThierryUSDSVA! With the R&S article in the discussion phase, I don't think anything else is needed for this ticket -- just the few miscellaneous Personal info items left on issue #36862

[MarciMcGuireGCIO]

@DanielleThierryUSDSVA — did you actually mean to reference #36862?

36962 is a dashboard request.

If so, @cgednalske can you let Danielle know exactly what you still need in #36862 Thanks!

[cgednalske]

@MarciMcGuireGCIO @DanielleThierryUSDSVA Of course! Here are the other minor items we wanted to look at (some of which may no longer be needed):

• Language around "If not listed, please provide your ___"
  • Other language options for this sentence, such as not using "provide" and maybe exploring "self describe."
• Language around "Prefer not to answer" and selection logic.
  • "Prefer not to answer (unchecks other boxes)" - consider using "selections" or "options" rather than boxes? Particularly for those using screen readers
  • Danielle would like to talk through the instructions for the checkboxes. (NOTE: Danielle I believe you mentioned not doing this anymore, to avoid adding too much content)
• Preferred name - do we add "first"?
  • Danielle has been working on something similar with Dené on this so wants to look at what they've already worked through and see how that can apply. (NOTE: We now have hint text that includes "first," so unless we need it in the heading, this might not apply any more)

[DanielleThierryUSDSVA]

Oh, sigh! @MarciMcGuireGCIO @cgednalske Yes. No wonder I thought it had no more content stuff needed...I was looking at the wrong ticket! Will look at these items now. Sorry about that!

[DanielleThierryUSDSVA]

@MarciMcGuireGCIO @cgednalske

Language around "If not listed, please provide your ___" Other language options for this sentence, such as not using "provide" and maybe exploring "self describe."

What do you think of one of these options? I wanted to make it a little less declarative because they don't have to provide this information if their SO isn't listed. They could choose Prefer not to answer instead.

This version is a lot longer than the original.

If your sexual orientation isn't listed, you can write it in here (255 characters maximum)

Or a shorter option

Type in an option that's not listed above (255 characters maximum)

Language around "Prefer not to answer" and selection logic.

I was looking around for ideas for a good way to say this and found that Microsoft's style guide recommends using "clear" for this context. I think that could work nicely here. What do you think?

Prefer not to answer (clears other selections)

or

Prefer not the answer (choosing this will clear other selections)

Preferred name - do we add "first"?

I agree. Since we have it in the hint text, we probably don't need it in the label. Thanks!

[cgednalske]

Thank you @DanielleThierryUSDSVA! These are great! 👍 There are a couple I'm leaning toward, but also anxious to try out the different options tomorrow and see how they'd affect the spacing.

For the first part, "If your sexual orientation isn't listed, you can write it in here (255 characters maximum)" seems like a great option - super clear and sounds optional overall, which is a plus! You're right that it is kind of long though... looks like it would add approximately one more line for mobile and fill one line of text in desktop... but maybe not too long?

For "Prefer not to answer," I lean more towards "Prefer not to answer (clears other selections)," just because it's shorter, but both options are great!

[MarciMcGuireGCIO]

Oh, sigh! @MarciMcGuireGCIO @cgednalske Yes. No wonder I thought it had no more content stuff needed...I was looking at the wrong ticket! Will look at these items now. Sorry about that!

No worries @DanielleThierryUSDSVA! There's a lot going on in this request.

[MarciMcGuireGCIO]

@DanielleThierryUSDSVA - thank you for these recommendations -- very helpful!

@cgednalske I agree with you -- let's see how they look in context.

[DanielleThierryUSDSVA]

@MarciMcGuireGCIO @cgednalske Glad these options give you something to work with!

Also, I confirmed with Samara that we're going to hit pause on the Resources and Support article for now. Thanks!

[MarciMcGuireGCIO]

Thank you @DanielleThierryUSDSVA!

[MarciMcGuireGCIO]

Moving this to Icebox per above.

[cgednalske]

Reopening this ticket to start up the Resources & Support article work again - discussed with @DanielleThierryUSDSVA during content office hours. During Personal information UAT, Veterans conveyed that they’d like to be able to access more information about the Gender identity field and its healthcare-related use beyond what we’ve provided.

[SKasimow]

@cgednalske - I just added you as an assignee for tracking purposes.

[SKasimow]

@cgednalske - is this still active?

[cgednalske]

@SKasimow Yes, still active for when Danielle is able to carve out time to work on it. 🙂

@DanielleThierryUSDSVA, I know it's a bigger project, but do you have an idea of when you might be able to pick this back up again?

[andaleliz]

Hi @DanielleThierryUSDSVA I'm taking this over - following up with you to get a status update. Thanks!

[DanielleThierryUSDSVA]

Hi @andaleliz. I don't think we want to start work on this now due to some bigger open questions around this topic. I think we should put this back in the icebox for now. Thanks!

[andaleliz]

Hi @DanielleThierryUSDSVA just doing a quarterly check on this and making sure we should still have this in the icebox. Thanks!

[mtcA6]

Cross posting from slack: Liz Lantz Hi @Danielle Thierry , I hope you had a great weekend! I just came across this ticket in our icebox since Feb 2022 and wanted to confirm w/ you that it’s still relevant and should be kept open. Thanks!

Danielle Thierry Hi @Liz Lantz! Had a really lovely weekend, thank you. Hope you did too! This isn't something I think we should start work on at this time. But, there's no harm in keeping it in the icebox from my perspective unless your team would rather just close it out for now and content can open a ticket on it if/when needed.

[andaleliz]

Adding a note here that we have recently had a conversation about creating an R&S page specifically for updating gender identity and addressing how Veterans can get their birth sex on file changed at VA. The process is different for VHA and VBA; we have info about VHA in an FAQ and would like to migrate that information to an R&S page to minimize hidden content in the profile. Here's some background info in GH comment.