Accessibility Feedback - Midpoint Review - Debt Resolution Team, Combined Debt Portal

[briandeconinck]

VFS acceptance criteria

• [x] Let Platform know when the Must feedback has been incorporated
• [ ] Leave any comments for feedback you decide not to take
• [ ] VFS team closes the ticket

Thoughts/questions

• Thank you! Overall this is great, and my feedback is pretty minor. I'm looking forward to seeing it at staging!

Feedback

• Must = the feedback must be applied
• Should = the feedback is best practice
• Consider = suggestions/enhancements

Must:

• Place the "TTY" inside the link when linking to the TTY number. When coded, this should look like: <a href="tel:711" aria-label="TTY: 7 1 1.">TTY: 711</a>. This ensures that the purpose of the link is clear without relying on any surrounding context (and helps screen reader users avoid accidentally calling this number).'
• During the meeting today there was some discussion of the alerts used when listing current debts. I'll defer to Sean and Allison for specific guidance on how those alerts should be used. If you're able to use the Design System component for this purpose, then that's great -- most accessibility features should be baked into the component. But if these end up coded as custom alerts and if multiple icons are used for different debt situations, make sure each icon has appropriate alternative text or screen reader only text to indicate what's being communicated. I'm happy to provide more guidance on that as needed!

Should:

Consider:

• On the Current VA Debt page when there are current debts (eg. the No copays on record view), the "Check details" link text for current debts may be a little ambiguous. Two big potential impacts here are screen reader users (harder to differentiate which link goes where) and voice command users (speaking the command Click check details link will match with both links). Consider adding some extra text to make the link purpose a little clearer across every possible use case, eg. "Check details" becomes "Check compensation and pension debt details." If that's not a practical option, then when this goes to code we may still need some helping aria-label text for screen reader users.

Platform directions

• Update "Issue Title"
• Link to collab cycle touchpoint meeting epic
• Add to the Feedback pipeline on the Platform Governance team board
• Add your feedback
• Add assignees based on collab cycle touchpoint
  • Design Intent: VFS designer, VFS PM (optional), yourself (optional)
  • Midpoint Review: VFS PM, yourself (optional)
  • Staging Review QA Only: VFS PM, yourself (optional)

[rileyorr]

Thank you for the feedback @briandeconinck! I believe @Dr-Pongo is already tackling the feedback about placing "TTY" inside the link when linking to the TTY number. I've opened a couple tickets regarding your additional feedback:

• Reviewing the icons in the cards' status sections
  • This also encompasses feedback from the design feedback ticket
• Reviewing the 'Check details' link text