Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DST Staging Review: Broken link to guidance from Storybook #3667

Closed
shiragoodman opened this issue Jan 9, 2025 · 0 comments · Fixed by department-of-veterans-affairs/component-library#1449

Comments

@shiragoodman
Copy link
Collaborator

shiragoodman commented Jan 9, 2025

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

Design System Staging Information

Component: Alert Sign-in
Staging Review ticket: Design System Staging Review: Alert Sign-in

Findings details

VA.gov Experience Standard - issue: User knows where a button or link leads.
VA.gov Experience Standard - category: Comprehension
This is an issue with the: guidance
High-priority: yes
Collab Cycle Reviewer: @erinrwhite (IA)

Description

The link in Storybook to View guidance for the Alert sign in component in the Design System points to https://design.va.gov/components/alert-sign-in resulting in a 404.

Link, screenshot or steps to recreate Image

Recommended action

Update the link to point to the URL for the guidance - https://design.va.gov/components/alert/alert-sign-in/

References

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

Next Steps for DST

  • Close the ticket when the issue has been resolved or validated by your Product Owner
  • If your team has additional questions or needs Governance help validating the issue, please comment on the ticket
  • If this ticket has a high-priority label, please address as soon as possible so VFS teams are not impacted
  • If this ticket has a consider label, please consider for future implementation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment