Staging Review finding: Update your multiple responses pattern to match more closely to the new pattern

[shiragoodman]

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: Disability Benefits Experience Team 1 Product: 21-526EZ Feature: Toxic Exposure Page

Findings details

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

Description

I listened to the Midpoint Review recording and know that you were deviating slightly from our old multiple responses pattern by using check boxes and a more flat IA. We have since updated the multiple responses pattern and have a new preferred UI and pattern.

Recommended action

If you can, try to align your UI or pattern closer to the new one. Look at things like the card style and edit link and delete buttons.

References

• Accessibility Defect Severity: N/A
• WCAG Success Criteria: N/A
• Modality: N/A
• Design System Component: N/A
• Design System Pattern or Template: Multiple responses
• 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.

[mayacarrolluxa6]

Taking a look at this now.

[mayacarrolluxa6]

@pacerwow I’ve created a Figma file called ‘Design Debt,’ which you can find here: [(https://www.figma.com/design/p5WMWutzPPhJvOkJmPtIsJ/Design-Debt?node-id=0-1&t=PQCok80qTL4RGqCl-1.)]

In the file, you’ll see the screenshots I collected from staging that highlight all instances where the outdated list loop component is being used.

Updating the designs with the new Multiple Responses component will require significant effort from both design and front-end engineering.

Since this isn’t a launch-blocking issue, I recommend adding it to the backlog under ‘design debt’ and scheduling it for a future sprint when it won’t interfere with higher priority tasks.