Staging Review finding: Remove the summary box styling

[shiragoodman]

Value Proposition

As veteran whose claim hasn't been fully initially processed in VBMS, when I visit CST, I want it to be clear that my information is not complete pending the initial review process, so that I know to check later to see my full claim details.

Need help? Please review how to read a Staging Review ticket. Tag @platform-governance-team-members on Slack if you need further assistance.

Product Information

Team: Benefits team 1 Product: Claim status tool Feature: Claims process overview page

Findings details

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

Description

There is content that is styled similar to the summary box with a blue background. Per our guidance, the content should be “evergreen”, not time sensitive. If you have a message that will appear only for a defined period of time, use an Alert component instead.

Recommended action

Either change the summary box style to the alert component or drop the styling all together if you do not feel it needs it. If you decide to make this an alert, read over the guidance and consider using a slim alert on the page with multiple alerts to create hierarchy.

References

• Accessibility Defect Severity: N/A
• WCAG Success Criteria: N/A
• Modality: N/A
• Design System Component: Summary box
• Design System Pattern or Template: N/A
• Design System Foundation: N/A
• Content Style Guide: N/A
• Context: 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.

Open Questions

• What rules trigger this UI state? Contentions = 0, has to be "open", null value for claim date, null value for claim type.
• What's happening in VMBS to even allow this claim state?

Acceptance Criteria

• Component used is consistent with design system guidance.
• Language used accurately conveys the preliminary state of the claim status information and tells users to check back later for a full view of their claim details.
• The component used shows on the pages that would be most helpful for the user and not show in areas irrelevant to the user.

[skylerschain]

FIGMA (WIP as of 10.29)

[skylerschain]

Designs are ready for development.

[skylerschain]

Design QA: @harshil1793 and I shared screen to review the implementation locally on his machine. LGTM 👍

[skylerschain]

@jacobworrell @jerekshoe Design QA is complete (see above) and I believe this is merged, so can we close this ticket?