Design Intent - Design Feedback - Name of Project

[allison0034]

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

• Look at Experimental Design Colored tags and see if this is of interest to you. It may help with stacked alerts.

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: Per our guidance, you cannot stack alerts. Work with accessibility on alert placement so they are not stacked. For the alert "We requested more information from you: Check the claim details to learn more.", you could consider removing the alert style, there is really no action the user can take.
• [ ] Must: Slim alerts are reserved for immediate feedback or alert hierarchy. I don't believe either of your fits that. Review the guidance and use the standard alert style if needed.
• [ ] Must: Revaluate the summary box. Be sure to look at the guidance and make sure your content fits that style. Also, consider giving the user the option to try to upload the file again.

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

[uxgary]

Hello @allison0034 , Thank you for your detailed feedback and for taking the time to explain each point thoroughly. I truly appreciate your insights.

I wanted to clarify that some of the points you raised regarding the use of the alert inside the card have already undergone experimental design and are part of the design system, "Card - Claim Status." This is why we opted to continue using the slim alert within the card.

We are continuing design work to address the other concerns you’ve raised, however.

I hope this provides some additional context, and I’m happy to discuss further if needed!

[allison0034]

@uxgary ok, thank you for the explanation, you can disregard that feedback.