Staging Review BAM2 Debt Letters Iteration 2

[leahkeeler]

Steps to complete Staging Review:

Requested time 12/1 11am

• [x] Product Manager: create this issue and fill in feature name in the title and other bolded information appropriately
• [x] Attach all artifacts before requesting the meeting
• [x] Link to this issue once created in #vfs-platform-support in Slack; tag @ Shira Goodman and @ Andrea Hewitt
• [x] Shira to schedule meeting with VSP reviewers and requesting team attendees (as listed below)
• [ ] At least 4 days before scheduled meeting, you must complete list of artifacts below
• [ ] Staging Review meeting completed
• [ ] Practice area reviewers create sub-issues attached to this one with feedback for your team on feature name
• [ ] Requesting team completes attached feedback tickets based on definition of done included in each practice area feedback ticket (may differ for each practice area, please refer to attached tickets for further instruction)

Artifacts - please provide the following artifacts at least 4 days before scheduled review meeting

-URL You have to sign in first, then enter the following: https://staging.va.gov/manage-va-debt/your-debt/

-Designs

• Link to product outline

• Link to [release plan]

• Access information for the tool or feature in staging do not put staging credentials in your va.gov-team ticket; store or reference them in a .md file in the va.gov-team-sensitive repository User 1 and User 38

• Link to your product test cases/test plan in TestRail with test execution logs (learn more) for QA practice area review

• Link to your Coverage for References and Summary(Defects) reports in TestRail for QA practice area review

• Certify that the following required accessibility tests are complete by checking each of these boxes (your accessibility specialist is available to help). Recommended items are optional, but highly encouraged.

  Required:

  • [x] Read the accessibility staging review documentation 
  • [x] Conduct axe browser scan, and document or address issues found
  • [x] Ensure end-to-end tests - including the axe check, pass
  • [x] Check color pairing for proper contrast
  • [x] Check for colorblindness issues
  • [x] Zoom to 200% at 1280px wide and confirm readability, no info cut off, etc
  • [x] Repeat for 300%
  • [x] Repeat for 400%
  • [x] Navigate all pages and core functionality with keyboard only
  • [x] Test all pages and core functionality happy path with MacOs + VoiceOver and/or NVDA+Firefox

  Recommended:

  • [ ] Read the accessibility post-launch processes 
  • [ ] Add keyboard end-to-end tests in CI/CD test runs
  • [ ] Conduct axe-coconut browser scan, document or address issues found
  • [ ] Test with WAVE tool

List of known issues (with links to tickets when applicable): (Please note, these should be links to individual issue tickets where the team documents issues found in their tests.)

1. The corona alert will change, currently under review with Peggy since collections will restart 2."why might I have this debt" under review with Peggy

Meeting attendees from requesting team

• Product Manager (required): Leah Keeler
• DEPO product lead (required): Matt Self
• Anyone else from your team who significantly contributed to the artifacts provided (required): Brad Conley, Craig Wheeler
• Other specialists: Becca Walsh Riley Orr

VSP will only invite those specified, so be sure to list your content, IA, accessibility and QA specialists, if applicable.

Scheduling

• Please reference the VSP Collaboration Meetings Calendar (times shown are ET)
• Note an available time slot within a recurring "[CALENDAR BLOCK] Review Group Office Hours" slot that works for your team and is at least 4 business days from now
• Write that preferred time slot here (on this ticket), and VSP will send you a meeting invite
• If no available time slots work for your team, write your availability and requirements here and shira will reach out as needed

Additional Notes

During this collaboration point, you will receive feedback from the following practice areas: design, accessibility, content, QA, and optional: product, analytics, engineering, information architecture

[shiragoodman]

@leahkeeler can you add last names please? I don't know who Craig is. Also, please be sure to include any shared resources for a11y, QA, content, IA or design. Thanks!

[leahkeeler]

@shiragoodman last names added. For reference, Iteration 2 adds additional information to Iteration 1 - mainly debt status and history - everything else is the same - Iteration 1 was going to be released and went through staging review already.

[mnorthuis]

@leahkeeler Is there something that details out what exactly was added in this iteration? Is it just data within the existing pages, and if so, which data?

[leahkeeler]

@mnorthuis Iteration 1 which was not released as planned only had the debt card and ability to download debt letters. Iteration 2 adds debt status and debt history in addition to Iteration 1 functionality.

[1Copenut]

@leahkeeler Is there a preferred test user for this staging review?

[leahkeeler]

user 1 and user 37