Content, accessibility, information architecture (CAIA) new initiative collaboration request

Use this ticket to request collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.

About your team

Team name: My education benefits
OCTO product owner: Eddie Ricks
Product name: Edu Application Recommender Tool
Product manager: Alexander Ferzola
Slack channel: https://join.slack.com/share/enQtNzI4MTYxNDIwOTQ2MC00ZWUyMzE1YzBlNzNiNWU3NDMwM2Q5ZDg3N2U0MzM2Yjc5NTRjMDllOGNiNjBlZjBjNTlkMmYyYTY1MzU1MDZl
Dedicated content writer on your team (if you have one): Insert name and/or GH handle
Dedicated a11y specialist on your team (if you have one): Insert name and/or GH handle

About your initiative

Which of these descriptions best fits the work we’ll partner on?

Select all that apply.

[ ] Digitizing a new form
[x] Creating a new digital tool
[ ] Updating an existing form or tool
[ ] Translating a form or tool into Spanish
[x] Adding new unauthenticated content to VA.gov
[ ] Updating existing unauthenticated content on VA.gov
[ ] Something else: insert description

What's the nature of your initiative and desired outcomes?

We are replacing the outdated, deprecated how to apply wizard that is located on the EDU How to Apply and Eligibility sections of Va.Gov. Our "Edu Application Recommender Tool" is a 1:1 replacement of the wizard and will seamlessly review prospective applicant information on the backend to recommend a likely education application form. Because we want to be transparent about their application options, we need some static copy around the new tool (and within the tool itself) for a good user experience.

Collaboration timeframe

Within the next two weeks would be helpful!

Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.

Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?

[x] Yes
[ ] No
[ ] I’m not sure

Where are you at in your timeline?

Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.

We have high fidelity wireframes that are ready for review. We have brought this to through the collaboration cycle. https://share.goabstract.com/b42bd417-c1cf-48c1-84c3-0656c8918e46

Will you release this new product incrementally (for example, release to 25% of users to start)?

[ ] Yes
[x] No

Note If you checked yes: Incremental launches require dynamic content. You'll need to ask your developer to build a React widget and provide CAIA with the ID code. CAIA will provide widget content and add the widget to your product’s static page. Please refer to this GitHub page for more information.
[ ] I acknowledge that if I change the launch to be incremental, or change it from incremental to 100%, I must notify CAIA of this change as these additional steps will impact deadlines.

Collaboration cycle

Which phases of the collaboration cycle have you completed?

Select all that apply.

[x] Design intent
[ ] Midpoint review (in the past)
[ ] Staging
[ ] None. This initiative isn’t going through the collaboration cycle.

Collaboration cycle ticket

https://github.com/department-of-veterans-affairs/va.gov-team/issues/83194

Supporting artifacts

Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content.

Supporting artifact placeholder link

Next steps

[x] Post a link to this issue in the #sitewide-content-sitewide-content-accessibility-ia slack channel and tag @Naomi Eke, and we’ll then acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.
[x] Review the remaining next steps in the VFS team tasks section here.
[ ] If you also need engineering support from the public websites team, fill out their intake request form as well: Open a public websites intake request
[ ] If you're requesting a page/URL redirect, a URL change, or a vanity URL, submit an additional request for this work: Open a redirect, URL change, or vanity URL request
[ ] If you're creating an experimental design, also contact the design system team: Read more about experimental designs
Suggest an addition or update to the design system team
[ ] If you're requesting a11y support for usability research, submit a research support request next: Open an a11y research support request
[ ] If you are requesting content support, please share your content source of truth (preferably as a SharePoint document).

department-of-veterans-affairs / va.gov-team

[CAIA Intake] <My Education Benefits>: <Edu Application Recommender Tool> #85984