Midpoint Review [Caregivers, HCA-Self-Identifying Gender Identity]

[tchrisdyer]

Steps to complete Midpoint Review

• [x] VFS Product Manager: Create this issue and fill in your team and feature name in the title.
• [x] VFS: Using the Slack Workflow (User guide), notify Collaboration Cycle team of this Github ticket in #vfs-platform-support.
• [ ] Platform: Schedule meeting with Collaboration Cycle reviewers and VFS team attendees (listed below).
• [ ] VFS: At least 2 days before scheduled meeting/review, attach all artifacts listed below and ensure Collaboration Cycle reviewers have appropriate access to secured applications.
• [x] Platform: Create feedback tickets and link to the Midpoint Review ticket (if no feedback, please comment stating that).
• [ ] VFS: Respond to feedback tickets.
• [x] Platform: Update Platform Collaboration Point Tracker.
• [ ] VFS: Close this ticket when the review is complete.

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

• [x] Yes*
• [ ] No

*If yes, please be sure to include any relevant content artifacts.

Artifacts

• Link to product outline
• Link to or attach prototype or mockups:
  • Sketch files - Birth sex, Birth sex -open, gender, gender-open
  • PDF file
• Link to or attach your project's content source of truth (for example, mockup, prototype, Github, Word outline, or staging or preview link): Designs have the most up-to-date content

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

Midpoint Reviews can only be scheduled on Monday, Tuesday, or Friday.

Please select your preferred time slot per the Platform Collaboration Meetings Calendar

July 19 @ 3:30pm

Please note:

• Time slots are required for both synchronous meetings and asynchronous reviews.
• All times are shown in ET.
• Available time slots are indicated with [REVIEW BLOCK].
• When you reserve a time slot, the reserved meeting will show up alongside the [REVIEW BLOCK].
• Please select a time slot at least 2 business days from request date.

Meeting attendees from requesting team*

*Only required for synchronous meetings.

• Product Manager (required): Chris Dyer
• OCTO-DE Product lead (recommended): Ming Ligh
• OCTO-DE Design lead (required): Ryan Thurlwell
• Anyone else from your team who significantly contributed to the artifacts provided (required): Dene Gabaldon, Dat Tran, Daniel Nalbach
• VFS Content, IA, accessibility, and QA specialists (if applicable): Shawna Hein, Josh Kim, Angela Fowler

Additional information

Please refer to the Platform Collaboration Cycle README on Github for more information about the Collaboration Cycle.

[shiragoodman]

thanks, @tchrisdyer . Review is scheduled for 7/19. You'll receive feedback asynchronously via this ticket by EOD.

[joshkimux]

One thing per page works great here for accessibility! Great work!!

Some consider items:

• Could we provide more short one-liner help texts to explains why certain questions are being asked? Since the page is much less busy thanks to one thing per page, I feel there's an opportunity to make these questions more transparent without all the noise. For example, instead of just "Marital status, required," having a short one liner help text below it explaining briefly why it is required. I hope this can help build trust and transparency.
• If one thing per page persists throughout this entire form, I wonder if we could experiment with two things:
  • sending focus to the first question on the page instead of the stepper "Step 1 of 6..."
  • setting the question as the heading + legend that receives focus and demoting the stepper to a p tag similar to gov.uk

[peggygannon]

Hello, @tchrisdyer I have no content feedback for this update. thanks!

[Dene-human]

@joshkimux Thanks so much for your feedback. In regards to the one-liners. I have been working on this with Danielle. I updated the body of this ticket with out most recent designs/content. We will work on the Marital status and race pages next. Attaching PDF here

[joshkimux]

@Dene-human , that's awesome to hear! If the expandable help accordions are nested within the same fieldset as the radio options and legend, they should announce properly in context to screen reader users. We can test more when it's in staging 👍

[Dene-human]

@joshkimux Sounds good. Thank you!

@dat-gcio tagging you here for visibility on these recommendations for when you start the dev.

[mnorthuis]

No IA feedback for this work. Thanks!