Midpoint Review - Design Feedback - Unified Appointment Experience, Appointments, Community Care Direct Scheduling

[allison0034]

Next Steps for the VFS team

• [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.
• [ ] 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

-

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: Work with accessibility on the filter results. Instead of "4 results", try "Showing 1-10 of 11 results for "health"
• [x] Must: I see the reset filters is the new button icon. Per our guidance, button icons are to be used in a Card or other container alongside a primary link. Unfortunately this will need to be a secondary button.
• [ ] Must: Several teams have been working on "filters" for content. We really do not have a great pattern. I would suggest you submit this to experimental design.

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
• [x] 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

[benbrasso-agile6]

@allison0034 no feedback or still populating?

[benbrasso-agile6]

Oh, sorry. I see it, doh.

[allison0034]

@benbrasso-agile6 sorry, I got it in late today, I needed to confirm something with Matt. Just let me know if you have any questions.

[benbrasso-agile6]

Work with A11y on results

Done

Can't use button icon

Changed it

[benbrasso-agile6]

Will leave this ticket open to work on the experimental ticket

[Cieramaddox]

@allison0034 I'd like to get an opinion on changes I've made to the filter page actions.

I received guidance from Sara Sterkenburg regarding the cancel action - making it a link rather than a button.

I would just make cancel a link in this case. Apply can be a button since it is saving data and navigating (same rules as "continue" buttons in forms).

With that in mind, I've come up with this as a solution (solving some of the visual issues with buttons on buttons on buttons). The left shows what we had previously. The right shows the updated design.

[allison0034]

Hi @Cieramaddox , does "Cancel" navigate? Pulling in @briandeconinck since he will know best.

[benbrasso-agile6]

Depends on the definition of navigate. It does navigate the user back to the last screen, while it also cancels/stops that sub-task from being completed.

[allison0034]

Ok, it may be something you want to actually walk @briandeconinck thru the flow.

[briandeconinck]

I think a link is appropriate here. Sara hit the distinction exactly right: does clicking the element change user data? Button. Does it just move you to a different screen? Link. I believe the Veteran Facing Forms team has something in the works that will eventually follow that pattern with the forms library, with the Back button becoming a link.

[Cieramaddox]

Wonderful, thank you!