Design Intent - Accessibility Feedback - Appointments FE Team, Appointments on VA.gov, Appointment Details Redesign

[briandeconinck]

VFS actions

• [x] 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.
• [ ] Close the ticket when all feedback has been addressed.

Thoughts/questions

• Thank you for all the thought that went into button/link selections! It's tedious and frustrating and no one likes to talk about it but I promise it matters! 😄

Feedback

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

• Must/Consider: If the extraneous actions (print, cancel) are clustered at the bottom of the card, adding a heading to indicate what they are (eg. "Actions" or "More actions") will improve findability and help distinguish them from the other parts of the card. This would be a must for screen reader users using visually-hidden sr-only text, and I would say consider just making it visible to everyone instead of hiding it and see if that kind of structure helps more broadly.
• Consider: If adding an event to your calendar isn't likely to be relevant anymore, remove that button to streamline the card and reduce the visual clutter relative to other actions.

[outerpress]

@Cieramaddox could you review this one?

[Cieramaddox]

@briandeconinck I wanted to check in about the guidance for this.

We previously used tertiary buttons for the actions (now using secondary) and wanted to be clear that the recommendation for a heading for action buttons still applies to the buttons.

[outerpress]

@ldelacosta I added design ticket #88859 to handle this