Design Intent - Accessibility Feedback - Benefits Dependent Experience, 21-686c/674, Critical Form Updates

[briandeconinck]

Next Steps for the VFS team

• [ ] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform.
• [ ] Comment on this ticket:
  • If the Platform reviewer has any Thoughts/Questions that require responses.
  • When Must feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback.
  • When Should/Consider feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback.
• [ ] Questions? For the most timely response, comment on Slack in your team channel tagging @platform-governance-team-members.
• [ ] Close the ticket when all feedback has been addressed.

Thoughts/questions

• Sounds like you're thinking about all of the right things here. Looking forward to seeing this as it moves along!

Feedback

Practice areas will document their feedback on the VFS-provided artifacts following the Must, Should, and Consider Framework. Platform Governance reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes).

• [x] Must: Guidance was recently added to the design system on when conditionally-revealing new inputs is appropriate. Some instances in your form where it probably makes more sense to split things onto another page:
  • All of the conditionals in the Add spouse flow except "Type of marriage > Other" and "Reason marriage ended > Annulment or other."
  • All of the conditionals in the Add child <18 flow
  • All of the conditionals in the Add child 18-23 flow
• [x] Should: In Step 1, the block of text after the checkboxes is likely to be skipped by screen reader users, which means they may miss out on some important information. It's also a bit higher cognitive load to follow and parse out what I should or shouldn't be choosing. Two possible things to explore:
  • Try breaking this text out into simple yes/no questions that can then map to the right selections on the back end. This takes some of the cognitive load off of the user to parse through everything.
  • Include help text in context with the relevant checkboxes themselves using the tile variant of the checkbox component. That helper text will be announced by screen readers when announcing the checkbox label, which ensures it doesn't get skipped and gives the information to users in the moment when they're deciding what to check.

Governance team actions

• [x] Format feedback as individual tasks (check boxes)
• [x] Assign this ticket to the VFS team member that opened the Slack request
• [x] Add the VFS team product label
• [ ] Add the VFS team the feature label (if applicable)
• [x] Add the touchpoint labels
• [x] Add the practice area labels
• [x] Add the Collaboration Cycle initiative milestone
• [x] Add the Collaboration Cycle initiative epic

[ajialeilani]

All feedback has been addressed in the mockup