Content Feedback - Midpoint review - DGIB, My Education Benefits

[peggygannon]

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

-

Feedback

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

[peggygannon]

Hi, @rlyons89 here is my feedback from today's Midpoint Review. Please let me know if you have any questions or want to discuss anything in more detail.

Questions/thoughts As discussed, please submit ticket to sitewide content team to request more in-depth content review and writing support. https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/.github/ISSUE_TEMPLATE/sitewide-content-intake-form.md

I'm also sharing a link to the VA.gov content style guide https://design.va.gov/content-style-guide/

A few things to note from the style guide

• We use contractions on VA.gov to support a conversational voice and tone.
• When referring to VA, use the first-person pronoun (we, us, our). Use the second person (you, your) to refer to Veterans, service members, and others.

---

Should feedback

1. Please write Post-9/11 GI Bill consistently throughout application (some instances are without hyphen)

2. Yellow alert on the application screens I think the alert content should be more detailed and specific, letting users know that they need to go through the wizard questions again to apply for other education benefits. Please work with sitewide content on the messaging in this alert.

3. For validation errors, please follow the [error message guidance here] (https://design.va.gov/patterns/messaging-dictionary) The validation error should read: Please enter your last name (not “a” last name)

4. Applicant info modal. Please work with sitewide content on the messaging and buttons content

5. Why does the H1 and form number change for the Service History screens? H1 and form numbers should be consistent throughout application, so users know they are in correct form/flow

6. H1 on the application approval/review/denial screens Our guidance is to not use punctuation or special characters (exclamation points) at end of H1s. Please remove the punctuation from H1s.

Also, H1 should be written in active voice. Here are some recommended updates:

• You have been approved! > We’ve approved your application
• Your application is under review. > We’re reviewing your application
• Sorry, you are not eligible. > Your application isn’t approved (I suggest moving the "we're sorry" to the first line of the the body content)

7. VA letters and documents screen Please fix misspelling of documents in the H1 (missing the d)

[rlyons89]

@peggygannon thanks for the feedback! We will review and incorporate and let you know if we need any clarification