Staging Review finding: Content recommendations in opening paragraph

[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 encounters content that does not meet best practices. VA.gov Experience Standard - category: Comprehension Launch-blocking: No Design System review: No Collab Cycle Reviewer: @kkitagawa-bosch (content)

Description

There are a few content issues in the introductory paragraph. Nothing is particularly "wrong" per the style guide, but significant improvements can be made.

Recommended action

(1) Change "this is a recommendation tool . . ." to be more active. "This tool does not determine eligibility" is clearer, then you can explain how users may determine eligibility elsewhere

(2) Move "welcome to VA" to the top, if anywhere. I don't think it's necessary, but it feels strange at the end of the second paragraph.

(3) Third paragraph does not need to be a separate paragraph and should be included in paragraph two.

References

• Accessibility Defect Severity: N/A
• WCAG Success Criteria: N/A
• Modality: N/A
• Design System Component: N/A
• Design System Pattern or Template: N/A
• Design System Foundation: N/A
• Content Style Guide: Content principles
• 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]

This ticket is closed 10/7/2024 because there is new text in the opening paragraph consistent with CAIA recommendations. Sprin3 Jira tickets 157, 158 and 175.