Midpoint Review - IA Feedback - Veteran Facing Forms - Patterns - Form submitter pattern

[erinrwhite]

Next Steps for the VFS team

How did this touchpoint go? Give feedback on the Collaboration Cycle at any time.

• 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

• Hi folks - I am giving this feedback in advance of the touchpoint because I will be OOO for the holidays. I return 1/2 and will review the meeting recording and add any additional feedback then.

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: avoid dead ends On the flows where we ask if someone is a designated alternate signer/appointed rep, the current flow has a dead end with an alert and a removed continue button. We haven't used this pattern elsewhere on VA.gov and it could be perceived by users as a mistake or a malfunction in the form. This also nudges up against our guidance on conditional reveals and disabled form elements. I recommend making a path for folks who select "No" that allows them some options to continue if they can't complete the form. After they select "No I'm not a rep" and continue, can we show a screen that shows the alert - "You can't do this, but here are some options for you" - and includes a link to find a VSO, fill the requisite forms, or contact the VA for help.

• Consider: clarifying allowed/disallowed scenarios in the docs I love the clarity in the documentation about roles for this pattern. We talked about this a little at Design Intent: would it be useful to specify that we are not allowing a scenario where the form submitter is completing the form on behalf of the Veteran but is not an accredited rep? It's not specifically mentioned in the claimant definition section but is very clear from the user flow. Or do we want to go silent on it?

• Consider: including LOA1 user in flow The user flow includes LOA3 users and not-logged-in users. What about LOA1 users? It might be a simple one-step flow like "Send user to verify their account" but for the sake of completeness, it'd be helpful.

Governance team actions

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