Please view the Milestone for all feedback and findings tickets associated with this Collaboration Cycle initiative.
VFS product information
VFS team name
Sitewide Content, Accessibility, and Information Architecture
Product name
Request help with VA debt from benefit overpayments page
Feature name
Request help with VA debt from benefit overpayments page
GitHub label for team
sitewide caia
GitHub label for product
sitewide content
GitHub label for feature
No response
Public DSVA Slack channel for VFS team
sitewide-content-accessibility-ia
Kickoff questions
Toggle kickoff questions
### When did/will you start working on this product/feature?
July 2024
### Will your work result in visible changes to the user experience?
Yes
### Are you doing research with VA.gov users?
No
### Will your work involve changes to...
Static pages
### Does your work require non-trivial code changes or involve PII/PHI?
None
### Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo?
Unsure
### Do you need to capture any additional analytics or metrics?
Unsure
### Will a VA editor (Drupal) notice this change?
Yes
### Product outline
N/A
### Verify all relevant materials provided to Governance Team
- [x] I have provided all relevant and up-to-date links, screenshots, images, designs, etc. of the as-is version of the product
### Add the GitHub labels for your team, product, and feature to this ticket.
- [x] I acknowledge that I must add the GitHub labels for my team, product, and feature to this ticket.
Kickoff Slack Thread with VFS team: [Kickoff thread](https://dsva.slack.com/archives/C01K37HRUAH/p1730906236582119)
Collaboration Cycle touchpoints
Design Intent
Toggle Design Intent instructions
#### Before the meeting
##### VFS team actions
- [ ] Review [Design Intent Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent) to understand what this touchpoint involves.
- [ ] Schedule your Design Intent (with at least 2 business days lead time from now):
- Open the [Calendly design intent calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review)
- Select a date and time and click "Confirm"
- Add your name and email
- Click "Add Guests" and enter the email addresses for VFS team attendees
- Click "Schedule Event"
- [ ] Link all artifacts in the `Design Intent artifacts for review` section below at least two business days before the scheduled Design Intent. Please don't add artifacts in the comments section.
**Design Intent artifacts for review**
[See guidance on Design Intent artifacts.](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent#Designintent-Artifacts) Governance Team feedback is based on the artifacts provided here as well as information provided during the meeting. Please provide links to artifacts **at least two business days** before the scheduled meeting.
Required:
- [ ] User flow
Not required, but nice to have:
- [ ] Wireframes (if provided, must include mobile wireframes)
Optional:
- [ ] Research plan
- [ ] Any other artifacts you have so far
##### Governance Team actions
- [ ] Design Intent Slack thread with VFS team
- [ ] Meeting date/time:
#### After the meeting
##### Governance Team actions
- [ ] Update this ticket with the Zoom recording
- Recording link
- Passcode:
- Accessibility
- [ ] Feedback ticket attached
- [ ] No feedback
- Design
- [ ] Feedback ticket attached
- [ ] No feedback
- IA
- [ ] Feedback ticket attached
- [ ] No feedback
##### VFS team actions
- [ ] Review feedback tickets. Comment on the ticket if there are any questions or concerns.
Toggle Staging Review
#### Before meeting
##### VFS actions
- Navigate to reference link: [Staging Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-review)
- [ ] Schedule your Staging Review when ready:
- Open the [Calendly staging review calendar](https://calendly.com/collaboration-cycle/staging-review)
- Select a date and time and click “Confirm”
- Add your name and email
- Click "Add Guests" and enter the VFS meeting attendees email addresses
- Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders
- Click "Schedule Event"
- [ ] If this product contains any [experimental design](https://design.va.gov/experimental-design/), add the `experimental-design` label and schedule a meeting with DSC to present the research findings.
- [ ] Link all artifacts **ONLY** in the Staging Review artifacts section below at least four days before the scheduled Staging Review. **Do NOT add artifacts to Comments section**
- [ ] I confirm the environment is available and test users have been provided.
- [ ] Please verify your product information in the [Product Directory](https://depo-platform-documentation.scrollhelp.site/getting-started/vfs-product-directory).
**Staging Review artifacts**
Links to [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-Artifacts) must be added to this ticket 4 business days ahead of the scheduled meeting. Please do not make changes to the product or artifacts during the 4-day review period.
**Required artifacts**
- [ ] **URL(s) to review the product**
- The product should be available on an [approved staging environment](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-environment-guidance-for-vfs-teams).
- List pages, sections of pages, and/or user flows impacted by this work.
- [ ] **Drupal or Staging URL for updated primary entry point:** the main way Veterans will access the tool through site navigation (not search)
- If the primary entry point is not a page on VA.gov, include information about how to view it. Reach out to `@platform-governance-team-members` on Slack with any questions.
- [ ] **Test users and scenarios** (when applicable)
- Store [test user information](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md), passwords, and tasks in a .md file in the va.gov-team-sensitive repository.
- Make sure all user scenarios can be tested, i.e.: in-progress form, submitted form, new form.
- [ ] **Link to Sitewide CAIA intake ticket**, if applicable.
- [ ] **Completed accessibility testing artifact:** see [instructions and link to accessibility testing template](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/prepare-for-an-accessibility-staging-review).
- [ ] **QA Artifacts:** artifacts that correspond to each of the [QA Standards](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards).
- [ ] Regression test plan
- [ ] Test plan
- [ ] Coverage for References
- [ ] Summary (Defects) reports
- [ ] E2E tests
- [ ] Code coverage
- [ ] Endpoint monitoring playbook
**Not required, but nice to have artifacts**
- [ ] **Content source of truth:** link to CAIA Content feedback, such as a content source of truth.
- [ ] **Information Architecture spec:** link to CAIA IA feedback, such as an IA spec.
##### Platform actions
- [ ] Slack thread with VFS team
- [ ] Meeting date/time:
#### After meeting
##### Platform actions
- [ ] Update this ticket with the Zoom recording
- Recording link
- Password:
##### VFS actions
- [ ] Review the findings tickets and comment on the ticket if there are any questions or concerns
- [ ] Close individual findings tickets when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment on the issue ticket.
- [ ] After launch, [request an accessibility audit from the VA 508 Office](https://depo-platform-documentation.scrollhelp.site/developer-docs/request-support-from-the-va-508-office#RequestsupportfromtheVA508office-AuditRequest). This is required even if no accessibility issues were found during the Staging Review.
- [ ] Share ServiceNow ticket number here: ______
- [ ] Close ticket once Privacy, Security, Infrastructure Readiness Review has been completed, VA 508 Office audit is requested, and all other post-Staging actions are complete
Hi! I opened this to request a staging review of a new static page in the main benefit hubs. The only artifact will be a single page in the Drupal preview environment. Let me know if I missed anything!
Please view the Milestone for all feedback and findings tickets associated with this Collaboration Cycle initiative.
VFS product information
VFS team name
Sitewide Content, Accessibility, and Information Architecture
Product name
Request help with VA debt from benefit overpayments page
Feature name
Request help with VA debt from benefit overpayments page
GitHub label for team
sitewide caia
GitHub label for product
sitewide content
GitHub label for feature
No response
Public DSVA Slack channel for VFS team
sitewide-content-accessibility-ia
Kickoff questions
Toggle kickoff questions
### When did/will you start working on this product/feature? July 2024 ### Will your work result in visible changes to the user experience? Yes ### Are you doing research with VA.gov users? No ### Will your work involve changes to... Static pages ### Does your work require non-trivial code changes or involve PII/PHI? None ### Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo? Unsure ### Do you need to capture any additional analytics or metrics? Unsure ### Will a VA editor (Drupal) notice this change? Yes ### Product outline N/A ### Verify all relevant materials provided to Governance Team - [x] I have provided all relevant and up-to-date links, screenshots, images, designs, etc. of the as-is version of the product ### Add the GitHub labels for your team, product, and feature to this ticket. - [x] I acknowledge that I must add the GitHub labels for my team, product, and feature to this ticket. Kickoff Slack Thread with VFS team: [Kickoff thread](https://dsva.slack.com/archives/C01K37HRUAH/p1730906236582119)Collaboration Cycle touchpoints
Design Intent
Toggle Design Intent instructions
#### Before the meeting ##### VFS team actions - [ ] Review [Design Intent Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent) to understand what this touchpoint involves. - [ ] Schedule your Design Intent (with at least 2 business days lead time from now): - Open the [Calendly design intent calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - Select a date and time and click "Confirm" - Add your name and email - Click "Add Guests" and enter the email addresses for VFS team attendees - Click "Schedule Event" - [ ] Link all artifacts in the `Design Intent artifacts for review` section below at least two business days before the scheduled Design Intent. Please don't add artifacts in the comments section. **Design Intent artifacts for review** [See guidance on Design Intent artifacts.](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent#Designintent-Artifacts) Governance Team feedback is based on the artifacts provided here as well as information provided during the meeting. Please provide links to artifacts **at least two business days** before the scheduled meeting. Required: - [ ] User flow Not required, but nice to have: - [ ] Wireframes (if provided, must include mobile wireframes) Optional: - [ ] Research plan - [ ] Any other artifacts you have so far ##### Governance Team actions - [ ] Design Intent Slack thread with VFS team - [ ] Meeting date/time: #### After the meeting ##### Governance Team actions - [ ] Update this ticket with the Zoom recording - Recording link - Passcode: - Accessibility - [ ] Feedback ticket attached - [ ] No feedback - Design - [ ] Feedback ticket attached - [ ] No feedback - IA - [ ] Feedback ticket attached - [ ] No feedback ##### VFS team actions - [ ] Review feedback tickets. Comment on the ticket if there are any questions or concerns.CMS Request
Toggle CMS Request
#### VFS actions - [ ] Complete the [CMS request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/cms-request)Staging Review
Toggle Staging Review
#### Before meeting ##### VFS actions - Navigate to reference link: [Staging Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-review) - [ ] Schedule your Staging Review when ready: - Open the [Calendly staging review calendar](https://calendly.com/collaboration-cycle/staging-review) - Select a date and time and click “Confirm” - Add your name and email - Click "Add Guests" and enter the VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click "Schedule Event" - [ ] If this product contains any [experimental design](https://design.va.gov/experimental-design/), add the `experimental-design` label and schedule a meeting with DSC to present the research findings. - [ ] Link all artifacts **ONLY** in the Staging Review artifacts section below at least four days before the scheduled Staging Review. **Do NOT add artifacts to Comments section** - [ ] I confirm the environment is available and test users have been provided. - [ ] Please verify your product information in the [Product Directory](https://depo-platform-documentation.scrollhelp.site/getting-started/vfs-product-directory). **Staging Review artifacts** Links to [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-Artifacts) must be added to this ticket 4 business days ahead of the scheduled meeting. Please do not make changes to the product or artifacts during the 4-day review period. **Required artifacts** - [ ] **URL(s) to review the product** - The product should be available on an [approved staging environment](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-environment-guidance-for-vfs-teams). - List pages, sections of pages, and/or user flows impacted by this work. - [ ] **Drupal or Staging URL for updated primary entry point:** the main way Veterans will access the tool through site navigation (not search) - If the primary entry point is not a page on VA.gov, include information about how to view it. Reach out to `@platform-governance-team-members` on Slack with any questions. - [ ] **Test users and scenarios** (when applicable) - Store [test user information](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md), passwords, and tasks in a .md file in the va.gov-team-sensitive repository. - Make sure all user scenarios can be tested, i.e.: in-progress form, submitted form, new form. - [ ] **Link to Sitewide CAIA intake ticket**, if applicable. - [ ] **Completed accessibility testing artifact:** see [instructions and link to accessibility testing template](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/prepare-for-an-accessibility-staging-review). - [ ] **QA Artifacts:** artifacts that correspond to each of the [QA Standards](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards). - [ ] Regression test plan - [ ] Test plan - [ ] Coverage for References - [ ] Summary (Defects) reports - [ ] E2E tests - [ ] Code coverage - [ ] Endpoint monitoring playbook **Not required, but nice to have artifacts** - [ ] **Content source of truth:** link to CAIA Content feedback, such as a content source of truth. - [ ] **Information Architecture spec:** link to CAIA IA feedback, such as an IA spec. ##### Platform actions - [ ] Slack thread with VFS team - [ ] Meeting date/time: #### After meeting ##### Platform actions - [ ] Update this ticket with the Zoom recording - Recording link - Password: ##### VFS actions - [ ] Review the findings tickets and comment on the ticket if there are any questions or concerns - [ ] Close individual findings tickets when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment on the issue ticket. - [ ] After launch, [request an accessibility audit from the VA 508 Office](https://depo-platform-documentation.scrollhelp.site/developer-docs/request-support-from-the-va-508-office#RequestsupportfromtheVA508office-AuditRequest). This is required even if no accessibility issues were found during the Staging Review. - [ ] Share ServiceNow ticket number here: ______ - [ ] Close ticket once Privacy, Security, Infrastructure Readiness Review has been completed, VA 508 Office audit is requested, and all other post-Staging actions are complete