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

[Discharge Upgrade Wizard] [ Staging Review] Various link and text changes from Staging Review Feedback #20124

Open
9 tasks
FranECross opened this issue Dec 18, 2024 · 4 comments
Labels
Discharge upgrade wizard Product owned by Public Websites team Public Websites Scrum team in the Sitewide crew sitewide VA.gov frontend CMS team practice area

Comments

@FranECross
Copy link

FranECross commented Dec 18, 2024

Status

[2024-12-18] [Fran] Note that this ticket should be worked on after the DADT DUW ticket is completed.

Description

The DUW Staging Review garnered various feedback, some of which will be shared with CAIA for determination on next actions, and some actionable without outside feedback.

This ticket has several minor changes we can make now.

Items to Change

Title Location Description
Link to find a VSO is outdated Results & Intro screens There is a link to Find a VSO near you that goes to https://www.benefits.va.gov/vso/varo.asp. This link is found in the introduction screen and results screen. We have recently launched a new Find a Rep tool which may be a better link destination. Change to implement: Update link location for Find a VSO to go to the new Find a Rep tool at https://www.va.gov/get-help-from-accredited-representative/find-rep (Fran has confirmed this is the correct link)
Unclear guidance in "tell us why you want to change your discharge paperwork Question 3: Tell us why you want to change your discharge paperwork Description: The note text (under the screen title for reason for requesting discharge upgrade) tells users to "choose number 2" but the radio buttons are not a numbered list, so it could be confusing or unclear to users what is meant by "number 2". Change to implement: Replace the phrasing "number 2" with something more precise: "choose the option associated with TBI"
Missing initialization in "tell us why you want to change your discharge paperwork Question 3: Tell us why you want to change your discharge paperwork Description: In the note text (under the screen title), the term "traumatic brain injury" is introduced without the initialization. Change to implement: Add the initialization so it reads "traumatic brain injury (TBI)"
All Steps on the Results page should be H2s Results page The following headers on the results page under the heading "Add supporting information" are H3s, like the main heading. The steps (main headings) should be H2s, and the sub headings are then correct remaining H3s

User story

AS A PO/PM managing DUW
I WANT to implement the Staging Review Feedback received
SO THAT DUW follows design guidance, as well as provides a polished, positive experience for Veterans.

Engineering notes / background

Roles / assignments

After functional testing, code review, accessibility review, and design review can happen in parallel.

Acceptance criteria

  • The breadcrumb 'How to apply for a discharge upgrade' returns the user to the introduction page of DUW /discharge-upgrade-instructions/introduction
  • All 'Find a VSO' links now opens the following: https://www.va.gov/get-help-from-accredited-representative/find-rep
    • the link on the introduction page in the accordion opens in the same tab
    • links on the results page open in a new tab
  • The guidance text on the last sentence of Question 3 (Tell us why you want to change your discharge paperwork) is now: For example, if you sustained a traumatic brain injury (TBI), which led to posttraumatic stress disorder (PTSD), choose the option associated with TBI.
  • On the results pages, all the steps should be updated to be h2s, regardless of it there is an alert or not (i.e. the steps will be siblings of the alert if it exists)
  • Ping Fran & Laura for testing
@FranECross FranECross added Needs refining Issue status sitewide VA.gov frontend CMS team practice area Public Websites Scrum team in the Sitewide crew Discharge upgrade wizard Product owned by Public Websites team labels Dec 18, 2024
@FranECross
Copy link
Author

@FranECross remove the breadcrumb item; DST ticket will fix it.

@FranECross
Copy link
Author

@laflannery answer heading question please.

@FranECross FranECross removed the Needs refining Issue status label Dec 18, 2024
@laflannery
Copy link
Contributor

@FranECross and @chriskim2311 I updated the headings AC to reflect that all steps should be H2s. Once that is updated, the H3s that were pointed out in staging review will be correct and no longer an issue

@FranECross
Copy link
Author

Thanks, @laflannery ! I updated the info in the table to reflect the updated AC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discharge upgrade wizard Product owned by Public Websites team Public Websites Scrum team in the Sitewide crew sitewide VA.gov frontend CMS team practice area
Projects
None yet
Development

No branches or pull requests

2 participants