Content, accessibility, information architecture (CAIA) new initiative collaboration request
Use this ticket to start collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.
Note: If you’re already partnering with us on an initiative, you don't need to fill out this request form. If you don’t have access to your initiative’s CAIA epic, post a message in the #sitewide-content-accessibility-ia slack channel and tag @Terry Nichols and @Lily Strelich.
About your team
Team name: Benefits - Non-Disability Experience
OCTO product owner: Emily Theis
Product name:
Personalized Career Planning and Guidance Program (PCPG) aka Chapter 36 (25-8832)
Vocational Rehabilitation and Education (VR&E) aka Chapter 31 (28-1900)
Burial Benefits (21P-530EZ)
Certificate of (Loan) Eligibility (COE)(26-1800)
Product manager: Laura Steele
Slack channel: #benefits-non-disability
Dedicated content writer on your team (if you have one): none
Dedicated a11y specialist on your team (if you have one): none
About your initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
[ ] Digitizing a new form
[ ] Creating a new digital tool
[ ] Updating an existing form or tool
[ ] Translating a form or tool into Spanish
[ ] Adding new unauthenticated content to VA.gov
[x] Updating existing unauthenticated content on VA.gov
[ ] Something else: insert description
What's the nature of your initiative and desired outcomes?
As part of updating all the forms listed above, we've also identified updates that need to be made to the static pages associated with each form.
Collaboration timeframe
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?
[ ] Yes
[x] No
[ ] I’m not sure
Where are you at in your timeline?
All of these forms require updates to align with the most recent version of each form's pdf. We are actively moving through the Collaboration Cycle for all of these forms:
Burial: Preparing for Staging Review (ETA is the week of March 11). Our goal is to go live by the end of March.
PCPG: Design Intent completed, CAIA review request submitted on 3/6
VR&E: Preparing for Midpoint Review
COE: Draft designs expected end-of-March
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply. (SEE ABOVE)
[ ] Design intent
[ ] Midpoint review
[ ] Staging
[ ] None. This initiative isn’t going through the collaboration cycle.
Collaboration cycle ticket
If you’re going through the collaboration cycle, provide your ticket number and link:
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.
The suggested changes to the static pages are outlined in this document.
Next steps
[x] Post a link to this issue in the #sitewide-content-sitewide-content-accessibility-ia slack channel and tag @Terry Nichols. We’ll reply within 24 hours to 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.
Tasks
### VFS team tasks
- [ ] **If you also need engineering support from the public websites team**, fill out their intake request form as well.<br> [Open a public websites intake request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E)
- [ ] **If you're requesting a page/URL redirect, a URL change, or a vanity URL**, submit an additional request for this work. <br> [Open a redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=jennymayoco%2C+kristinoletmuskat%2C+strelichl%2C+FranECross&labels=sitewide+CAIA%2C+Sitewide+IA%2C+Public+Websites%2C+VA.gov+frontend%2C+Redirect+request&projects=&template=redirect-request.md&title=Redirect+Request)
- [ ] **If you're creating an experimental design**, also contact the design system team. <br> [Read more about experimental designs](https://design.va.gov/about/contributing-to-the-design-system/experimental-components-and-patterns#what-is-an-experimental-component-or-pattern?) <br> [Suggest an addition or update to the design system team](https://design.va.gov/about/contributing-to-the-design-system/suggest-an-addition-or-update)
- [ ] **If you're requesting a11y support for usability research**, submit a research support request next. <br> [Open an a11y research support request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=coforma-terry%2Cangelafowler82&labels=508%2FAccessibility%2C+sitewide+CAIA%2C+sitewide+accessibility%2C+CAIA-a11y-research&template=caia-a11y-research.yaml&title=%5BCAIA+A11y+Research%5D%3A+Team+name%2C+product+name)
- [ ] **If you are requesting content support**, please share your content source of truth (preferably as a SharePoint document).
Content, accessibility, information architecture (CAIA) new initiative collaboration request
Use this ticket to start collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.
Note: If you’re already partnering with us on an initiative, you don't need to fill out this request form. If you don’t have access to your initiative’s CAIA epic, post a message in the #sitewide-content-accessibility-ia slack channel and tag
@Terry Nichols
and@Lily Strelich
.About your team
About your initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
insert description
What's the nature of your initiative and desired outcomes?
As part of updating all the forms listed above, we've also identified updates that need to be made to the static pages associated with each form.
Collaboration timeframe
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?
Where are you at in your timeline?
All of these forms require updates to align with the most recent version of each form's pdf. We are actively moving through the Collaboration Cycle for all of these forms:
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply. (SEE ABOVE)
Collaboration cycle ticket
If you’re going through the collaboration cycle, provide your ticket number and link:
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.
Next steps
@Terry Nichols
. We’ll reply within 24 hours to 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.Tasks