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

[erinrwhite]

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 bringing this to us - this new design holds a lot of complexity and is still simplified and streamlined from the previous iteration. Not much in the way of notes from me.
• I very much support the team's plan to research primary actions users might take on appointment detail pages and look forward to seeing how this'll move our thinking on the ol' buttons vs links debate.

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: If keeping the Print and Cancel CTAs on the same view, they should be visually separated rather than on the same line, as they're different types of tasks (verifying/documenting information vs. destroying it).

• [x] Consider: Small things on the user flow - there is some inconsistency on where "directions" links are set to go (Google Maps vs. Default map program) and calendar link says CSS instead of ICS.

[outerpress]

@Cieramaddox could you review this one?

[Cieramaddox]

@erinrwhite Is this a launch blocker, or could I get a ticket out to fix this post launch?

[erinrwhite]

@Cieramaddox none of these would be launch-blocking - and because this is feedback from a Design Intent in September it might no longer be valid.

[outerpress]

@erinrwhite just wanted to check up on this one since it didn't come up during staging review. Is it still a must to visually separate the action buttons? It looks like they're still on the same line.

And if so (I'm assuming yes) does visually separate means they should be on separate lines - or are there other treatments that you were thinking of?

[outerpress]

@erinrwhite I think we resolved all the content inconsistencies, and no more came up on staging review so I'm checking off that item.

[erinrwhite]

Thanks @outerpress for following up on this one! It isn't an experience standards violation so much as a suggestion to have these actions farther apart from each other. A separate line would be great! But again, because this isn't a standards violation, you can take or leave this feedback (this note should have originally been a "should", not a "must").

[outerpress]

Thank you @erinrwhite ! @Cieramaddox any thoughts on/objections to moving these to separate lines? If you prefer we can also leave it as is since there's been some talk about repositioning these buttons entirely in the future.

[outerpress]

@outerpress NTS this may be done, look for a dev ticket for this

[outerpress]

Going to handle this in #88859