IA Feedback - Midpoint Review [DGIB, My Education Benefits]

[mnorthuis]

VFS acceptance criteria

• [ ] Let Platform know when the Must feedback has been incorporated
• [ ] Leave any comments for feedback you decide not to take
• [ ] VFS team closes the ticket

Thoughts/questions

The "wizard" on the How to apply page - a couple of FYIs about this existing functionality...

• The wizard does not currently pass data into the form flow, it only knows to link users to specific URLs (form URLs) based on how they answer their questions.
• The wizard currently lives on the How to apply page, but per standards needs to be moved into the React application (the form flow). If you look at the disability claim form, you will see how the wizard is supposed to be implemented. In addition, this wizard (specific to education) will live on 5-6 different forms, so this needs to be considered if you plan to make changes to the wizard. This work will also impact all of our entry point links.

Application status and return users

• How/where do users check the status of their application after they submit it? My VA? If so, what do the different statuses look like on this page?
• This information will need to be added to appropriate content pages such as the confirmation page, and After you apply page. Please work with sitewide content on this.

My VA page

• What are the various statuses that would be shown?
• Where do each of the links on the right side go? Are these new pages, or are they deep links into existing tools?

General

• Where does the "explanation of benefits" links used across the experience go? And is this link relevant if they are denied benefits?

Feedback

• Must = the feedback must be applied
• Should = the feedback is best practice
• Consider = suggestions/enhancements

Must: Education form flow

• The breadcrumb for the form shown in your mocks is incorrect. The correct breadcrumb is: Home > Education and training > Apply for education benefits. This is different than the live site, which is currently incorrect. When this form flow is implemented, this should be corrected. It must be accurately reflected in the prototype for user research to ensure users have an accurate view of where they are.
• There is an unauth and auth version of the /introduction page of the form. Current screen shots only show an auth version of the page. Most users are unauthenticated when they arrive on a form, that version must be included in user testing to ensure an accurate flow is represented.

Must: Download VA benefit letters

• The breadcrumb shown in your mocks is incorrect. The correct breadcrumb is Home > Records > VA letters and documents. This is different than the live site, which is currently incorrect. When this page is modified, this should be corrected. It must be accurately reflected in the prototype for user research to ensure users have an accurate view of where they are.
• There is a typo in the H1 the word "documents" is missing the "d".

Must: Email

• link labels need to be fully descriptive to where they are taking the user, and must match the landing page. Avoid using links labels such as "here". Please work with sitewide content to refine content.

Should:

Consider:

[mnorthuis]

@rlyons89 I have a number of questions and would love to connect and work with you and your team to ensure we have entry points, flows, URLs and link labels all worked out. I can also help provide background on the existing wizard implementation and existing education forms. Please reach out and let me know how I can help.

[rlyons89]

@mnorthuis thanks for the quick feedback and questions! I will reach out to find a time to discuss the questions and thoughts

[mnorthuis]

@rlyons89 Can you submit an IA request for this work, and we can work together on finalizing the placement, URLs and links/entry points for this work?

https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=mnorthuis%2C+shiragoodman&labels=vsp-product-support%2C+collaboration-cycle%2C+collab-cycle-review%2C+ia&template=ia-request.md&title=IA+Request+%5BTeam-Name%2C+Feature-Name%5D