[Consistency] User encounters design components that are inconsistent or confusing.

[shiragoodman]

This ticket was generated during the pilot process for the new VA.gov experience standards. Please tag @platform-governance-team-members on Slack if you need assistance interpreting this ticket.

Product Information

Team: Benefit Tools Product: Claim Status Tool Feature: Improved Evidence Request Initiative

Findings details

VA.gov Experience Standard - issue: User encounters design components that are inconsistent or confusing. VA.gov Experience Standard - category: Consistency Launch-blocking: No Design System review: No Collab Cycle Reviewer: @allison0034 (Design), @briandeconinck (Accessibility)

Description

On the claims page, there are multiple warning alerts stacked on top of each other. Per our guidance, you should not stack alerts.

Recommended action

These are notifications, not Alerts, because: They are triggered not by the user, but by an external process They should stick around until the user has dealt with them (they are not dismissible but no idea how long they'll stay in this interface) and thus they should have state (read, unread) and the ability to see them later (archive). We would love to see something new proposed for this situtaion however since it is late in the game, choose a hierarchy and show one at a time until it is dealt with. Matt Dingee has filed a design gap ticket, if you would like to propose something new please reach out.

References

• WCAG Success Criteria: N/A
• Modality: N/A
• Design System Component: Alert
• Design System Pattern or Template: N/A
• Design System Foundation: N/A
• Content Style Guide: N/A
• Context: N/A
• Accessibility Defect Severity: N/A

---

Next Steps for the VFS Team

• [ ] Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members with any questions or to get help validating the issue.
• [ ] Ticket ownership: If you believe that this issue is out of scope, not your team's responsibility, or a Design System issue, comment and tag @platform-governance-team-members on your team channel in Slack to provide an explanation and who you believe is responsible. The Governance team will follow up.
• [ ] Close this ticket when the issue has been resolved or validated by your Product Owner.

[jacobworrell]

We do not have evidence that the direction given in this feedback helps solves our user's pain points and we have some indication that we'd create brand new ones if we created functionality allowing users to dismiss these to-do items. It's important that the items get dismissed only when the action being requested is taken. We understand the desire to not make pages too "noisy", but the value of having these high priority items super salient to veterans seems to outweigh this concern. We think the current design approach works for our use cases and would like to close this ticket @shiragoodman. Happy to discuss in future office hours if necessary.

[shiragoodman]

@allison0034 and @briandeconinck tagging you both since you flagged this an an issue. See Jacob's comments above and let me know if there's anything we need to escalate. I can pull in Matt if you think it's necessary.