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: Clashing content guidance in content style guide #3378

Open
shiragoodman opened this issue Oct 15, 2024 · 0 comments
Open

Comments

@shiragoodman
Copy link
Collaborator

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: Help users to... Know when their information is prefilled
Staging Review ticket: AEDP, Design Patterns, Help users to... Know when their information is prefilled

Findings details

VA.gov Experience Standard - issue: User encounters design components or patterns that are inconsistent or confusing.
VA.gov Experience Standard - category: Consistency
This is an issue with the:
High-priority: No
Collab Cycle Reviewer: @erinrwhite (IA), @KKitagawa-Bosch (content)

Description

In the content style guide's engagement messages guidance the sample messages should match the new pattern guidance.

Recommended action

Update the engagement messages guidance to incorporate the appropriate content from the Contextual Alert Content section and link to the engagement messages page from the pattern page, rather than duplicating contnt.

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: Error messages - Engagement
  • 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