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: Storybook buttons say "button goes here" #3673

Closed
shiragoodman opened this issue Jan 9, 2025 · 1 comment
Closed

DST Staging Review: Storybook buttons say "button goes here" #3673

shiragoodman opened this issue Jan 9, 2025 · 1 comment

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 encounters consistent, clear design components and patterns.
VA.gov Experience Standard - category: Consistency
This is an issue with the: code
High-priority: No
Collab Cycle Reviewer: @erinrwhite (IA), @allison0034 (Design)

Description

In storybook, all the buttons for each iteration of the sign-in alert have some variation of the language "Button goes here" - including examples like verifying the account with ID.me or Login.gov that should use the same button design and text regardless of the application. It makes the Storybook documentation look unfinished.

Link, screenshot or steps to recreate Image

Recommended action

Update storybook buttons to use some kind of default button design/text, even if that text can be changed as a component variable.

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
@caw310
Copy link
Contributor

caw310 commented Jan 15, 2025

Closing as @danbrady figured out a way to fix this which has been implemented. Thanks Dan!
https://design.va.gov/storybook/?path=/docs/components-va-alert-sign-in--docs

@caw310 caw310 closed this as completed Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants