Open nkontrabecki opened 3 months ago
+1 to @artsymartha68 comments. I suspect the search results page will be the most revealing on smaller screens because there is so much stuff pushing the search results (the thing that is most important) down the page.
Also +1 to what i believe @erinrwhite suggested regarding H2s and dropping the accordions altogether — generally speaking, it'd be nice if all search results on VA.gov delivered a very similar experience. There are many search tools, and i would think no matter which of them a user decides to use, they would expect them behave similarly — maybe not exactly the same depending on the needs, but similar. Dropping the accordions def gets us nearer to that unified experience.
@artsymartha68 The team is working on the mobile mock ups. What is the recommended review process once we are ready for your team to review and provide feedback? @cora-goldston-bah
If @briandeconinck doesn't have the time to take another look, I may be able to help a bit (but I'm nowhere near as good as Brian!). Just reach out on slack. Hopefully struggling with the small mobile screen will help you streamline the workflow and content you're presenting.
@briandeconinck and @artsymartha68 Our team started the mobile web Figma Mock ups. We are still working on the Results page portion. Please review the mobile version and provide feedback on what we have accomplished to date. As soon as we have the Results page completed, I will let you know. VTS Mobile Web Figma
This is really shaping up! You broke out the questions to “one thing at at time” and reduced the content to its core. This is so difficult design-wise but really makes a big difference, especially for the folks who will be using this questionnaire.
Please view the Milestone for all feedback and findings tickets associated with this Collaboration Cycle initiative.
VFS product information
VFS team name
Transition Experience
Product name
Transition Experience MVP v1
Feature name
V1 Transition Experience
GitHub label for team
transition-experience
GitHub label for product
transition-experience-MVP
GitHub label for feature
No response
Public DSVA Slack channel for VFS team
ves-transition
Kickoff questions
Toggle kickoff questions
### When did/will you start working on this product/feature? May 2024 ### Will your work result in visible changes to the user experience? Yes ### Are you doing research with VA.gov users? Yes ### Will your work involve changes to... Both ### 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? Yes ### Product outline https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/vet-transition-support ### 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. ### Notify the Collaboration Cycle team of this ticket in your team's public Slack channel. - [X] I acknowledge that I must notify the Governance team by completing the Collab Cycle Kickoff workflow in my team's Slack channel after submitting this issue. This can be completed by typing "/collab cycle" and selecting the kickoff workflow. Kickoff Slack Thread with VFS team: [Kickoff thread](https://dsva.slack.com/archives/C06C7RS27GD/p1715355788426939)Recommended 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: - [X] [User flow](https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1716219020147/013c6f25f45e35963469c7bb7a94b66e1402f663?sender=uba527cafb8ded20512886129) Not required, but nice to have: - [X] [Wireframes](https://www.figma.com/design/Y72reZ0Qt9xteezdnLbBDW/Wireframes-for-v1?node-id=0%3A1&t=l90aXJCrJfAktf1O-1) Optional: - [ ] Research plan - [ ] Any other artifacts you have so far ##### Governance Team actions - [x] [Design Intent Slack thread with VFS team](https://dsva.slack.com/archives/C06C7RS27GD/p1715625704260119) - [x] Meeting date/time: **Friday, May 24, 2024 at 2:00PM ET** #### After the meeting ##### Governance Team actions - [x] Update this ticket with the Zoom recording - [Recording link](https://oddball-io.zoom.us/rec/share/HNkdixvhDWWXV70fBQEVlWlmaKKM-ZIRkwztoaCcWR4bD7bNQi6uOkz3m64SR3SK.llJFqX4Yo-73350T) - Passcode: `$PG.2BhD` - Accessibility - [x] Feedback added to milestone - [ ] No feedback - Design - [x] Feedback added to milestone - [ ] No feedback - IA - [x] Feedback added to milestone - [ ] No feedback ##### VFS team actions - [ ] Review feedback tickets. Comment on the ticket if there are any questions or concerns.Research Review
Toggle Research Review
#### VFS actions - [ ] Complete the [research review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Research-plan-review.1781891143.html)Midpoint Review
Toggle Midpoint Review
#### Before meeting ##### VFS actions Navigate to reference link: [Midpoint Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review) - [ ] Schedule your Midpoint Review when ready: - Open the [Calendly midpoint review 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 VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click "Schedule Event" - [ ] Check this box if you'd like this review to be asynchronous (Please refer to the [Midpoint Review guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Midpoint-review.1781039167.html) for the difference between a synchronous meeting and an asynchronous review) - [ ] Link all artifacts **ONLY** in the Midpoint Review artifacts section below at least two days before the scheduled Midpoint Review. **Do NOT add artifacts to Comments section** **Midpoint Review artifacts** See Platform guidance on [Midpoint Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review#Midpointreview-Artifacts). Platform feedback is based solely on the artifacts provided, as reviewed during the two days before the Midpoint Review meeting. Any work not included in the artifacts below or any ongoing work taking place during the review period may not be reflected in that feedback. Provide links or documents for the following: - [x] [Finalized design prototype or mockup](https://www.figma.com/design/DNy6D8ELfTQW1g3EK7yJu5/Mid-Fidelity-Prototype-for-v1?node-id=2643-7998&t=Q4dUcfCm5ja3SRpf-0) - [x] Specify which pages are included in the review: **All pages of our v1 product** - [x] [Research plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/vet-transition-support/research/2024-02-discovery/research-plan.md) - [x] [Conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/vet-transition-support/research/2024-02-discovery/conversation-guide.md) **Content artifacts** [CAIA intake](https://github.com/department-of-veterans-affairs/va.gov-team/issues/83802) - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form. - [x] None received **IA artifacts** - [x] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-caia-intake-request) feedback you received, including an IA review document or intake form. - [x] [Link to the CAIA intake form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/83802) and [Link to the IA feedback from our Design Intent meeting](https://github.com/department-of-veterans-affairs/va.gov-team/issues/83999) Note: As documented in the comments on the IA feedback ticket, we are not including a "Skip" button per the team's original recommendation, due to development challenges. With the IA team's agreement, we are leaving all questions except one as "optional," so the user can skip questions by not answering them. ##### Platform actions - [x] [Slack thread with VFS team](https://dsva.slack.com/archives/C06C7RS27GD/p1716411335425739) - [x] Meeting date/time: July 11, 2024 at 3:30 p.m. ET #### After meeting ##### Platform actions * Accessibility * [x] Feedback added to milestone * [ ] No feedback * Content * [x] Feedback added to milestone * [ ] No feedback * Design * [x] Feedback added to milestone * [ ] No feedback * IA * [x] Feedback added to milestone * [ ] No feedback * [x] Update this ticket with the Zoom recording - [Recording link](https://oddball-io.zoom.us/rec/share/d-ZhTjwjXmxf9jntGuC91jlZdojR3O4FJjfgT0jWYNPGXW9olmb0Q84fycuJr-Tc.Hatm3CO7Zc0jxPds) - Passcode: `3%p2vxn2` ##### VFS actions - [ ] Review feedback tickets and comment on the ticket if there are any questions or concernsAnalytics Request
Toggle Analytics Request
#### VFS actions - [ ] Complete the [analytics request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Analytics-request.1782120453.html) - [ ] Link to the Analytics Implementation and QA Request ticket belowContact Center Review
Toggle Contact Center Review
#### VFS actions - [ ] Complete the [Contact Center review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Contact-center-review.1782317061.html) - [ ] Link to the Contact Center review request ticket belowStaging 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** See Platform guidance on [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-Artifacts). Platform findings are based solely on the staging URL and test users provided, as reviewed during the four days before the Staging Review meeting. Any test cases not covered or any ongoing work taking place during the review period may not be reflected in those findings. **Product artifacts** - [ ] Staging URL - [ ] Specify which pages are included in the review - [ ] Staging test user information **Note:** Please double-check that you've provided staging access information appropriate for testing the tool or feature. Don't put staging credentials in your va.gov-team ticket; store [test user information, passwords, and tasks](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md) in a .md file in the va.gov-team-sensitive repository. **Content artifacts** - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including a content source of truth, any relevant static content page and entry point updates, and the intake form. **IA artifacts** - [ ] Please include a link to any [Sitewide CAIA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-caia-intake-request) feedback you received, including an IA review document or intake form. **QA artifacts** An artifact that corresponds to each standard in 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 **Accessibility artifacts** - [ ] [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). ##### 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 completePrivacy, Security, Infrastructure Readiness Review
Toggle Privacy, Security, Infrastructure Readiness Review
#### VFS actions - [ ] Complete the [Privacy, security, infrastructure readiness review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Privacy-and-security-review.1782317101.html) - [ ] Link to the Readiness Review ticket below #### Platform actions - [ ] Privacy, security, infrastructure readiness review is complete