Staging Review finding: Breadcrumbs incorrect

[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: Transition Experience Product: Transition Experience MVP v1 Feature: V1 Transition Experience

Findings details

VA.gov Experience Standard - issue: User can't determine where a page is within the VA.gov website. VA.gov Experience Standard - category: Findability Launch-blocking: No Design System review: No Collab Cycle Reviewer: @erinrwhite (IA)

Description

Breadcrumbs for the tool are currently VA.gov home > Benefit and resource recommendation tool > [Current Page] but should remain consistent throughout the form flow. Breadcrumbs should also reflect hte location of the tool within the VA.gov information architecture once that is determined.

Link, screenshot or steps to recreate


Recommended action

Update breadcrumbs to accurately indicate where the tool will fall within the VA.gov information architecture. Because this is a form flow, the current breadcrumb should be the title of the form. See breadcrumb guidance for additional information.

References

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

[nkontrabecki]

Good Morning @erinrwhite. Our team has some questions about this ticket. Please advise when you are available to discuss. https://staging.va.gov/benefit-eligibility-questionnaire

We understand that since this is a form flow, the current breadcrumb should be the title of the form. We updated the breadcrumb to "Discover your benefits" on each page, however, when the breadcrumb link is clicked, on each page, it does NOT take the user to the Welcome/Get Started page of the tool. This is the desired outcome. The developers did some research and identified that the va-breadcrumbs component is setting the href automatically. We would like to discuss.

The team reviewed the breadcrumb guidance for additional information.

[erinrwhite]

@nkontrabecki Agh! This sounds like an issue with the component - I encourage your team to reach out to the #platform-design-system channel in Slack to ask about this behavior in the breadcrumbs component.

Relatedly, if possible please use the same/similar text for all the title elements on the page: the first part of the title tag, the current breadcrumb, the H1, and if possible the URL slug. Currently the first part of the title tag and the URL slug are different (Benefit Eligiblity Questionnaire) from the page h1 and the current breadcrumb (Discover your benefits). Apologies if this is already on the list, just wanted to note it while here.

[nkontrabecki]

@erinrwhite Thank you for getting back to us quickly. We reached out to the #platform-design-system team and inquired about the behavior. Laura Flannery indicated the following "this had previously come up when the guidance for the breadcrumbs was being finalized, this was the previous thread. The ticket that was mentioned, that was written up is here. I'm not sure of the timeline for an update though."

Based on that information, we will monitor this. Also, we are aware that the first part of the title tag and the URL slug are different from the h1 and the current breadcrumb. We have a separate ticket to address this. @cora-goldston-bah @RonnieYoung-UX