Closed cassidy-beach closed 2 weeks ago
@sara-amanda Hello! VYE Team completed moderated user research testing and are finishing up unmoderated user research testing within the next week. I'm hoping for some clarification on what more is needed, if anything, from the VYE team moving forward as we gear up for Staging Review in the next month or two. Please let me know if I need to provide additional information. Thank you!
Hi @cassidy-beach! I'm one of the IA specialists with CAIA and had some follow-up questions after reviewing the ticket:
www.va.gov/education/verify-school-enrollment/enrollment-verifications/
? Is there a way to host both on the same URL? Or to show only 1 benefit depending on which one a Veteran is enrolled in? If not, Sitewide IA can work you all to update the URL in staging so it's correct and specific to this GI bill benefit. We'll also want to ensure there's content on the static page so Veterans can distinguish between which tool applies to them.Hi @jennymayoco!
Hi again @jennymayoco,
Quick correction: users have to submit Form 22-8979 if there are errors in their enrollment.
Hi @cassidy-beach thank you for your insights! I dropped some comments in the Figma file. I'm OOO 4/1-4/2 but will be back on Wednesday and can check in in case of any follow up questions.
A couple of follow-ups:
www.va.gov/education/verify-school-enrollment/enrollment-verifications/
, the H1 is Post-9/11 GI Bill enrollment verifications
. We're wondering if there is an opportunity to update that H1 and have that page show 2 cards/links, one for Post-9/11 and the other for Montgomery benefits, or if possible to only show the current benefit so Veterans don't have to choose. The link would direct them to the page where they can verify enrollment, this page in the designs. I created a quick flow of what this could look like in Mural. What do you think about the flow and technical lift at this stage? I understand that staging review is coming up so this might be out of scope at this time and our deepest apologies for jumping in later in the process! I'd also love to learn more about the research the team has done if you could point me to that. Thank you!
Hi @jennymayoco,
Thank you for your input! Since we are actively preparing for release it is too close to make such a significant change. Additionally, the Post-9/11 link and page falls under another team and another stakeholder. However, our team is happy to put this work in the backlog and commit to it after our initial release.
To my knowledge there are plans to move away from TIMS and BDN to a modernized system that works across VA.gov benefits management so Veterans do not have to input/update their information at several points. I am unsure of when this will go into effect or who is taking over the initiative.
Absolutely! Our team is compiling the moderated and unmoderated research results into a report during our next sprint. For now, feel free to look over all the data in Optimal Sort. You need special access to look at the data, but trying to open it is worth a shot. I'd be happy to send over the report once it's finished.
Figma link for all mockups -> https://www.figma.com/file/B3Ds72oQhBZG1EtfffbAYk/VYE-Wireframes?node-id=42%3A4775&mode=dev
@cassidy-beach one clarifying question for you all: if the team is aiming for a mid-month launch instead of May 28, would that be mid-May or mid-June?
@strelichl Mid-June
Noting next steps from today's sync:
Hi @RyanGrayVA @jsimonVA @cassidy-beach,
I checked with a content OCTO lead and a copy editor about the registered trademark symbol. They confirmed that we shouldn't include it in the H1 of the VYE tool. (OCTO's response: "Way back when we first launched the education hub (this is one of the places you mentioned you saw the trademarked symbol), the lawyers approved the approach of including the symbol on a high-level page once, and that was enough."
There's some guidance here as well: https://design.va.gov/content-style-guide/trademarks
Please let me know if you have any questions. Thanks! cc @aprocik1 @strelichl
Hey @jsimonVA @RyanGrayVA @cassidy-beach,
I've got a question about this copy in the VYE prototype separate from what we discussed yesterday. The Figma says:
If the above enrollment information isn’t correct, please do not submit the form. Instead, work with your School Certifying Official (SCO) to ensure your enrollment information is updated with the VA before submitting this form.
Note: Please note that providing false reports concerning your benefits may result in a fine, imprisonment or both.
To the best of your knowledge, is this enrollment information correct? (*Required)
Have lawyers at VA approved the language in bold+italics? For context, we usually need lawyers to approve legal language in forms. The PDF version of form 22-8979/Student verification of enrollment says:
PENALTY - Willful false reports concerning benefits payable by VA may result in a fine, imprisonment, or both.
whereas the va.gov style guide has default language for penalty notices in online forms, which is this:
Note: According to federal law, there are criminal penalties, including a fine and/or imprisonment for up to 5 years, for withholding information or for providing incorrect information (See 18 U.S.C. 1001).
The style guide also notes we can't change legal content without legal review.
If VA lawyers haven't yet approved the language about penalties in the VYE tool, can you please connect with them and confirm the exact legal language we can use to inform users about the penalties for providing false information to VA? Let me know in a Github comment. Thanks!
Thanks Katherine, we'll get it removed.
From: katherine-fung @.> Sent: Friday, May 10, 2024 9:42 AM To: department-of-veterans-affairs/va.gov-team @.> Cc: Gray, Ryan T. (governmentcio Llc) @.>; Mention @.> Subject: [EXTERNAL] Re: [department-of-veterans-affairs/va.gov-team] [CAIA Intake] Verify Your Enrollment (VYE) (Issue #68205)
Hi @RyanGrayVAhttps://github.com/RyanGrayVA @jsimonVAhttps://github.com/jsimonVA @cassidy-beachhttps://github.com/cassidy-beach,
I checked with a content OCTO lead and a copy editor about the registered trademark symbol. They confirmed that we shouldn't include it in the H1 of the VYE tool. (OCTO's response: "Way back when we first launched the education hubhttps://www.va.gov/education/ (this is one of the places you mentioned you saw the trademarked symbol), the lawyers approved the approach of including the symbol on a high-level page once, and that was enough."
There's some guidance here as well: https://design.va.gov/content-style-guide/trademarks
Please let me know if you have any questions. Thanks! cc @aprocik1https://github.com/aprocik1 @strelichlhttps://github.com/strelichl
- Reply to this email directly, view it on GitHubhttps://github.com/department-of-veterans-affairs/va.gov-team/issues/68205#issuecomment-2104633332, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCH5UIA5ROJZKM4C73XOKHDZBTFCNAVCNFSM6AAAAAA6MWLSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBUGYZTGMZTGI. You are receiving this because you were mentioned.Message ID: @.**@.>>
Hi @RyanGrayVA @cassidy-beach @jsimonVA @jason-gcio here is the finalized IA spec.
Some things of note in the doc:
www.va.gov/education/verify-school-enrollment/mgib-enrollments/
and used /verify-information/
for the step in the flow to represent that the first page is a list of enrollment verifications and the second page is where folks can take action/verify this info.Let me know if you have any questions!
cc @katherine-fung @aprocik1
Providing 2 updates here:
We're happy to return to this and complete our review when the product team is ready.
Hi A.,
I've tagged you in the relevant spots in the Figma file, but so we have a record here:
Please let me know if you have additional questions.
Thanks!
Ryan
From: A Procik @.> Sent: Thursday, May 23, 2024 11:41 AM To: department-of-veterans-affairs/va.gov-team @.> Cc: Gray, Ryan T. (governmentcio Llc) @.>; Mention @.> Subject: [EXTERNAL] Re: [department-of-veterans-affairs/va.gov-team] [CAIA Intake] Verify Your Enrollment (VYE) (Issue #68205)
Providing 2 updates here:
We're happy to return to this and complete our review when the product team is ready.
- Reply to this email directly, view it on GitHubhttps://github.com/department-of-veterans-affairs/va.gov-team/issues/68205#issuecomment-2127451321, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCH5UIA4A34Q47T25IOSPCDZDYEZDAVCNFSM6AAAAAA6MWLSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRXGQ2TCMZSGE. You are receiving this because you were mentioned.Message ID: @.**@.>>
@RyanGrayVA @jsimonVA Here is the widget copy to use on the static page. I'm noting that I'm not sure which phone number to use. Currently I have the main education line but if it should be the WAVE number, please let me know and we can change it. I'll also need to figure out the hours for that one.
Verify enrollment widget copy.docx
When we add this widget to the page, we'll also need to update the widget that's currently there for Post-9/11 GI Bill so that it's clear it's for different benefits. Is this also your team or someone else?
@RyanGrayVA, thanks for following up on my comment above. I left you these three comments in the Figma file: Comment 1, comment 2, and comment 3.
Governance determines what's launch blocking in staging review, so they may have a perspective on the "no" option. CAIA just provides recommendations--both for immediate and future consideration. If a user selects "no," I think we'd want to present them with clarifying content that describes their next steps. But I don't think we'd want them to still submit their form.
10-4. Thanks A.
From: A Procik @.> Sent: Wednesday, May 29, 2024 9:57 AM To: department-of-veterans-affairs/va.gov-team @.> Cc: Gray, Ryan T. (governmentcio Llc) @.>; Mention @.> Subject: [EXTERNAL] Re: [department-of-veterans-affairs/va.gov-team] [CAIA Intake] Verify Your Enrollment (VYE) (Issue #68205)
@RyanGrayVAhttps://github.com/RyanGrayVA, thanks for following up on my comment above. I left you these three comments in the Figma file: Comment 1https://www.figma.com/design/B3Ds72oQhBZG1EtfffbAYk?node-id=42-5180#819878741, comment 2https://www.figma.com/design/B3Ds72oQhBZG1EtfffbAYk?node-id=48-9273#792188488, and comment 3https://www.figma.com/design/B3Ds72oQhBZG1EtfffbAYk?node-id=48-9273#820812563.
Governance determines what's launch blocking in staging review, so they may have a perspective on the "no" option. CAIA just provides recommendations--both for immediate and future consideration. If a user selects "no," I think we'd want to present them with clarifying content that describes their next steps. But I don't think we'd want them to still submit their form.
- Reply to this email directly, view it on GitHubhttps://github.com/department-of-veterans-affairs/va.gov-team/issues/68205#issuecomment-2137482931, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCH5UIG4QA4EYILC47MRGHDZEXNDTAVCNFSM6AAAAAA6MWLSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZXGQ4DEOJTGE. You are receiving this because you were mentioned.Message ID: @.**@.>>
@RyanGrayVA, our content review of the MGIB VYE tool is complete. If you'd like, we're happy to help implement staging review feedback. Thanks for collaborating on this with Katherine and I.
A,
That's great news. I'm sure the team would be delighted to have your help in implementing the staging review feedback.
What would that entail?
Ryan
From: A Procik @.> Sent: Wednesday, May 29, 2024 2:03 PM To: department-of-veterans-affairs/va.gov-team @.> Cc: Gray, Ryan T. (governmentcio Llc) @.>; Mention @.> Subject: [EXTERNAL] Re: [department-of-veterans-affairs/va.gov-team] [CAIA Intake] Verify Your Enrollment (VYE) (Issue #68205)
@RyanGrayVAhttps://github.com/RyanGrayVA, our content review of the MGIB VYE tool is complete. If you'd like, we're happy to help implement staging review feedback. Thanks for collaborating on this with Katherine and I.
- Reply to this email directly, view it on GitHubhttps://github.com/department-of-veterans-affairs/va.gov-team/issues/68205#issuecomment-2137978477, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCH5UIBWHTY5AFRMNGMAU43ZEYJ4VAVCNFSM6AAAAAA6MWLSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZXHE3TQNBXG4. You are receiving this because you were mentioned.Message ID: @.**@.>>
@RyanGrayVA, we sometimes help teams implement or interpret Governance's content feedback. If you're uncertain about how to act on any of their content feedback after your staging review, feel free to tag me in this ticket. We can review it together and align on next steps.
Got it. Thanks A.
From: A Procik @.> Sent: Monday, June 3, 2024 8:21 AM To: department-of-veterans-affairs/va.gov-team @.> Cc: Gray, Ryan T. (governmentcio Llc) @.>; Mention @.> Subject: [EXTERNAL] Re: [department-of-veterans-affairs/va.gov-team] [CAIA Intake] Verify Your Enrollment (VYE) (Issue #68205)
@RyanGrayVAhttps://github.com/RyanGrayVA, we sometimes help teams implement or interpret Governance's content feedback. If you're uncertain about how to act on any of their content feedback after your staging review, feel free to tag me in this ticket. We can review it together and align on next steps.
- Reply to this email directly, view it on GitHubhttps://github.com/department-of-veterans-affairs/va.gov-team/issues/68205#issuecomment-2145059425, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BCH5UIFKOIVRKTNPQLFDVZDZFRNTHAVCNFSM6AAAAAA6MWLSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGA2TSNBSGU. You are receiving this because you were mentioned.Message ID: @.**@.>>
@RyanGrayVA @jsimonVA Here is the widget copy to use on the static page. I'm noting that I'm not sure which phone number to use. Currently I have the main education line but if it should be the WAVE number, please let me know and we can change it. I'll also need to figure out the hours for that one.
Verify enrollment widget copy.docx
When we add this widget to the page, we'll also need to update the widget that's currently there for Post-9/11 GI Bill so that it's clear it's for different benefits. Is this also your team or someone else?
@RLHecht the post 9/11 is a different team. Looks like this team is the "My Education Benefits Team"
Hi A., we just received staging review feedback and got a blocker related to content: Staging Review finding: Entry points/static page(s) not updated to point to new tool #86820
Of the four entry points CAIA identified in the IA Design for Montgomery GI Bill Benefits - Verify Your Enrollment doc, we've already dealt with item number 1 ("Verify Your School Enrollment" page), we are working to get a new react widget live now.
But for numbers 2-4, those are responsibilities of the Content team, correct? Do we need to do anything to help these changes along?
@cassidy-beach FYI @katherine-fung @jennymayoco
@RyanGrayVA, we sometimes help teams implement or interpret Governance's content feedback. If you're uncertain about how to act on any of their content feedback after your staging review, feel free to tag me in this ticket. We can review it together and align on next steps.
@RyanGrayVA We've already talked in slack but just commenting here as well. We are waiting for the PR to merge for the widget to display correctly on the static landing page. And I will have the preview links for the 3 other pages for you shortly.
But just to clarify, because this is a staged rollout, the links on these three other pages will point to our static page for now and not the VYE tool since that won't be visible to everyone at this time. So these are not technically entry points right now and shouldn't be a blocker.
@RyanGrayVA The widget on the static "Verify your school enrollment" page is now showing correctly, so this should no longer be a launch blocker.
Here's the preview link (you need to be on the VA network for this to work): http://preview-prod.vfs.va.gov/preview?nodeId=51828
Since the IA spec has been updated to reflect this is the main entry point and the 2 MGIB pages are cross links, I don't know that you need to show those to the collab cycle, but here they are:
MGIB-AD: http://preview-prod.vfs.va.gov/preview?nodeId=932 MGIB-SR: http://preview-prod.vfs.va.gov/preview?nodeId=934
When the tool is ready to launch, let us know so we can publish these 3 static pages. Thanks!
Thanks @RLHecht! Hopefully, this removes the staging blocker. @cassidy-beach FYI
@RLHecht Is this one ok to close now?
Hi @strelichl yep, this looks like we can close this.
About your team
CAIA Support Request
Describe what you need in a few sentences:
Examples
Which are you doing?
Types of Support
What areas does your team need support in? Check all that apply.
Content
Accessibility
IA
Multilingual content
Timeframe
We guide and work alongside teams across nearly every OCTO digital product. We also work with partners across VA to lead content migration and manage all unauthenticated content on VA.gov. And we're always working to expand the VA.gov content style guide and our IA and accessibility documentation. We need to prioritize all intake requests based on our overall workload and VA and OCTO priorities.
Tell us about your product's timeline. And we'll work with you to meet timeline needs as best we can.
Approximately 3 months
Have you worked with CAIA before?
What's your team’s next step and its timing?
Timing for your next step:
Is this timing related to a specific event or Congressionally mandated deadline?
If you're conducting research, when is that starting?
Provide date if available: xx/xx/xxxx
Will you release this new product incrementally (for example, release to 25% of users to start)?
Note: If you checked yes, we’ll reach out to discuss details about the content in the react widget (we use these widgets to display entry points for new products to a certain percentage of users who visit our static pages).
When do you expect to launch your product to 100% of users? May 2024
Please provide an estimated date so our team can create other relevant tickets.
Collaboration Cycle
Will this work be going through the Collaboration Cycle?
If no ...
If yes ...
Please provide the link to your Collaboration Cycle ticket:
Please check all of the phases in the Collaboration Cycle you have completed:
Completed 10/19/2023
Design intent recording Passcode: &V^AXU19Completed 12/4/2023
Recording linkFor planning purposes, please check all of the phases in the Collaboration Cycle you feel you might need CAIA support and guidance:
Design Intent
Midpoint
Staging
Supporting artifacts
Please provide links to supporting artifacts as available.
Product outline: Verify Your Enrollment Product Outline
User flows:
Prototype or mockups: VYE Wireframe v1
If this is in Sketch, which version or specific page should we focus on? There is only one page.
Content source of truth: VYE Team and EDU Business Line (VRE)
Research plan: TBD
Any epics/issues that may be helpful:
Link to testing accounts (please do not paste them in this ticket): We do not have testing accounts yet.
Additional Support: Collaborative Sessions
Have you already worked with someone from OCTO leadership?
How do you plan to work with us on this request?
Accessibility Help in Slack
The #accessibility-help channel in the DSVA Slack, is also available to you as a resource. Everyone is welcome to ask questions or get help from our a11y (accessibility) specialists. Tag
@Terry Nichols
to get a11y help asap.Next steps
Once you’ve submitted this ticket, please post a link to this issue in the #sitewide-content-ia Slack channel and tag
@Terry Nichols
.If you also need engineering support from the Public Websites team, fill out their intake request form.
If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a Redirect, URL change, or vanity URL request
If you are requesting a11y support for user research, please complete this form, next.