Midpoint Review eBenefits - "View your representative"

[jason-gcio]

Steps to complete Midpoint Review

Before meeting

VFS Product Manager

• [x] Create this issue and notify the Collaboration Cycle team of this ticket in the in #vfs-platform-support (see Slack Workflow (User guide).
• [x] Add artifacts listed below to the ticket at least 2 days before scheduled meeting.

Platform

• [x] Schedule meeting with Collaboration Cycle reviewers and VFS team attendees listed in the ticket.
• [x] Create feedback tickets and link to the Midpoint Review epic (if no feedback, please comment stating that).

After meeting

VFS Product Manager

• [ ] Respond to feedback tickets.
• [ ] Close this ticket when review is complete and feedback has been addressed.

Platform

• [x] Update Platform Collaboration Point Tracker.

Has your team met with the Sitewide Content team for content support?

• [x] Yes*
• [ ] No

*If yes, please include any relevant content artifacts. I believe Beth Potts has seen this copy.

Artifacts

Provide links or documents for the following:

• [x] Product outline

• [x] Finalized design prototype or mockup

• [ ] Research plan (?)

- [ ] Conversation guide (?)

Content artifacts

• [x] Content brief (if applicable) and your product’s content source of truth

• [ ] Github ticket for any relevant static content page and entry point updates for tool or feature (if applicable)

QA artifacts

Learn more about QA artifacts

• [ ] Regression test plans (if there isn't already a regression test plan for this feature in TestRail Product)
• [x] Link to test cases/test plan in TestRail (draft)

VFS Meeting Attendees

Required*

*Only required for synchronous meetings.

• Product Manager: [Insert name here]
• OCTO-DE Product lead: [Insert name here]
• OCTO-DE Design lead: Ryan Thurlwell

Team Members

• [Insert name here]
• [Insert name here]

VFS Attendees

• Content and IA:
• Accessibility:
• QA specialists:

Scheduling

Would you like this review to be asynchronous?

Please refer to the Midpoint Review guidance for the difference between a synchronous meeting and an asynchronous review.

• [x] Yes
• [ ] No

December 3, 2021 2 pm ET

Additional information

Please refer to Platform Collaboration Cycle or the Midpoint Review Touchpoint on Platform website for more information about the Collaboration Cycle.

[shiragoodman]

@jason-gcio The asynch review has been scheduled for 12/3, meaning you will receive feedback by EOD. No meeting will be held.

[joshkimux]

@jason-gcio Quick question, are the mockups linked in the ticket up to date? I see comments I've left on these from a year ago.

[allison0034]

@jason-gcio do you know if there are any user flows? Specifically, we are wondering where the ID.me button goes to (modal or a new page).

[joshkimux]

I've left a11y feedback into the mockups 🙇 New feedback includes:

• Adding purpose to the link (Go to eBenefits). You could potentially remove this link in favor of rewriting the previous content to be: Let us know if you'll be working with a representative or change your current representation on eBenefits
• When working with your developer, consider recommending to either (a) add a sr-only span of the form title (e.g. Appointment of Veterans Service Organization as Claimant's Representative) within the download links or (b) attach them to the download links using aria-describedby. This will help screen reader users navigating by links to receive the same local context a sighted user would have.

[sporeboy]

The amended mockups are ready for review. The link at the top of this tick is good. Thanks for the quick feedback @joshkimux; one of you suggestions has been implemented.

[joshkimux]

@sporeboy Awesome! Just checked them out. Might be a little nitpicky-- so only if you have the time-- I'd recommend considering removing the "Go to let VA know about changes" link in favor of linking up the "log in to eBenefits to make changes". It would save a little bit of space!

[jason-gcio]

@allison0034 - the only real user flow here is to have the Veteran login and be able to view their representative. The other screens in the mockup are for different status in case the representative isn't found or something.

ID.me verification button (on page 5) would go to that proofing function in profile if clicked, nothing new there. I don't think the verification functions can all fit into a modal.

[peggygannon]

Hello, @jason-gcio I have no content feedback at this stage. Thank you!

[jimuhh]

Apologies. I was out on Friday but have appended (very minor) IA feedback today.