Update Collab Cycle Request tickets for accessibility testing artifact

[shiragoodman]

User Story

As a VFS team member, I want to be able to rely on the Collaboration Cycle Request ticket for accurate information and not have to double check the Change History log for anything that has changed since my ticket was created.

Assignee: @briandeconinck
Peer Reviewer: @it-harrison

Description

The accessibility testing artifact was launched 12/1 and announced to VFS teams on 12/5. All Collaboration Cyce kickoffs 12/1 or later will reflect the new artifact request at Staging Review, however any kickoffs prior to this will still request the old accessibility artifacts under Staging Review. Any VFS team holding a Staging Review after 12/12/22 will be required to submit the new accessibility testing artifact.

The purpose of this ticket is to update all Collaboration Cycle Request tickets in the Collaboration Cycle Reviews board so that their accessibility artifacts section under Staging Review requests the new accessibility testing artifact.

Impacted Artifacts

Tasks

For every Collaboration Cycle Request ticket in the Collaboration Cycle Reviews board (excluding Post-Staging Pipeline), under Staging Review, Accessibility artifacts replace:

- [ ] [Completed TestRail Platform accessibility test plan](https://dsvavsp.testrail.io/index.php?/suites/view/14&group_by=cases:section_id&group_order=asc):  **(Preferred)** OR, 
- [ ] Document in your product folder that indicates all required checks from the [how to prepare for an accessibility staging review](https://depo-platform-documentation.scrollhelp.site/developer-docs/How-to-prepare-for-an-accessibility-staging-review.1909293137.html) doc are complete: 
- [ ] List of known issues with links to tickets (when applicable)

with:

- [ ] [Completed accessibility testing artifact](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=briandeconinck&labels=a11y-testing&template=a11y-testing.yaml&title=Accessibility+Testing+for+%5BTeam+Name%2C+Product+Name%2C+Feature+Name%5D). For details, see [Prepare for an accessibility staging review](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/prepare-for-an-accessibility-staging-review).

• Open Collab Cycle tickets updated
  • Collaboration Cycle for [VAOS, VA Online Scheduling, Appointment List Feature] #42025
  • Collaboration Cycle for [Authenticated Experience, My VA, Audit UX Improvements] #42601
  • Collaboration Cycle for [Benefits Team 1, Supplemental Claims Form 20-0995] #43919
  • Collaboration Cycle for [Digital GI Bill, GI Bill Comparison Tool: Comparison Tool Enhancements] #44187
  • Collaboration Cycle for [Public Websites, Income Limits, Income Limits Web App] #44321
  • Collaboration Cycle for Profile Team | Notification Preferences | 1095B Form  #45798
  • Collaboration Cycle for Sitewide Facilities VBA Regional Offices  #46029
  • [FSR - PI3/23] Collaboration Cycle for [Benefits Team 2 - FSR- Enhancements] #47462
  • Collaboration Cycle for [10-10 Health Apps, 10-10EZ, Household Information Optimization] #47766
  • Staging Review [MHV Secure Messaging in VA.gov] - Archived #48629
  • Collaboration Cycle for Virtual Agent Chatbot - Move the Chatbot #48652
  • Collaboration Cycle for [Modernized Check-in, eCheck-in & Pre-Check-in, Simplified VA Header/Footer] #48859
  • Collaboration Cycle for MHV to VA.gov Team - Medical Records (Health History - Vaccines, Allergies, Vitals, Health Conditions) #48972

Peer Review

To be completed by peer reviewer

• User story and acceptance criteria are met

Acceptance Criteria

• All CC Request tickets have been updated with current accessibility artifacts request for Staging Review

How to prepare this issue

Refinement

• Ticket has user story, description, tasks, and acceptance criteria
• Ticket has additional appropriate labels, if applicable
• Ticket has been sized
• Once all above items are checked, add the 'Ready' label.

Planning

If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly

• Ticket has been discussed as a team at Planning
• Ticket has been assigned to appropriate initiative or quarterly epic
• Ticket has been assigned to a Sprint
• Ticket has been moved to the Planned pipeline in the Governance team board
• Ticket as an assignee and peer reviewer

[briandeconinck]

@it-harrison this should be ready for review!

[it-harrison]

looks good @briandeconinck!