Midpoint Review - IA Feedback - Secure Messaging, Landing Page/Navigation Updates

[erinrwhite]

Next Steps for the VFS team

• [ ] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• [ ] Comment on this ticket:
  • If the Platform reviewer has any Thoughts/Questions that require responses.
  • When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• [ ] Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members.
• [ ] Close the ticket when all feedback has been addressed.

Thoughts/questions

• This is looking good to me - y'all have streamlined this significantly from design intent which is great.

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform Governance reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

• [ ] Must: H1, current breadcrumb and page title should match Y'all asked about the H1's and breadcrumbs during the review; those are looking good as outlined. For Staging Review, make sure your h1, current breadcrumb on desktop, and first part of the title tag before | Veterans Affairs are all using the same text.

Governance team actions

• [x] Format feedback as individual tasks (check boxes)
• [x] Assign this ticket to the VFS team member that opened the Slack request
• [x] Add the VFS team product label
• [x] Add the VFS team the feature label (if applicable)
• [x] Add the touchpoint labels
• [x] Add the practice area labels
• [x] Add the Collaboration Cycle initiative milestone

[underpaid1ntern]

Hi @erinrwhite ! Thank you for your feedback!

I just wanted to note a needed deviation for staging based on a PII / PHI concern.

Here's the formula we use for title tags per Sara Sterkenburg:

The TLDR background:

• When Veterans start new messages on Messages, there is a required subject line which is an open field
• This subject line becomes the h1 of the conversation details page (which houses all msgs related to that convo)
• Previously, SM was forming title tags as [h1] + " MHV Secure Messaging | Veteran Affairs"
• Google Analytics captures title tags and doesn't scrub PII / PHI
• Therefore, it was possible for GA to obtain and store bits of PII /PHI if Veterans were to put in a provider name, condition/medication in the subject line as an example
• CAIA collaborated and came up with a generalized format that doesn't exactly mirror the h1 but is still 508 compliant

CC: @emilytaylorux @sterkenburgsara

[erinrwhite]

@underpaid1ntern yes, absolutely! Looks good. Thanks for the documentation.