[ ] 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
Sorry for the delayed written feedback! Overall this looks great, looking forward to seeing the outcome of your user research!
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).
[ ] Should: Between the two options presented, I have a strong preference for "Ape." The "one thing per page" approach has a bunch of accessibility benefits, not least of which is it minimizes the number of conditional-reveal questions. Those kinds of fields can get confusing for screen reader users who don't get the visual cue of something changing on the screen, and can be disorienting if a user decides to go back and change an answer but doesn't realize the that it will change the content of the page. (See also the guidance on conditional reveals in the design system, which is intentionally limiting.)
[ ] Consider: If "Elk" tests well for Veterans' mental model of how they enter their conditions, I would recommend exploring ways of breaking up those subsequent detail questions into multiple pages, rather than the conditional reveal approach.
Governance team actions
[x] Format feedback as individual tasks (check boxes)
[ ] 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
Next Steps for the VFS team
@platform-governance-team-members.Thoughts/questions
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).
Governance team actions