Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finalize design recommendations for Service Location Address paragraph type #17489

Closed
4 tasks done
davidmpickett opened this issue Mar 11, 2024 · 6 comments
Closed
4 tasks done
Assignees
Labels
CY24-Q2 Calendar year Q2 2024 priority Design CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide UX VAMC CMS managed product owned by Facilities team

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Mar 11, 2024

User Story or Problem Statement

The Address section of Service Locations has been reviewed in #14845 and #17342, but it still needs work before it's ready for engineers to implement.

Latest design

Description or Additional Context

Latest iteration:

Section content

Steps for Implementation

Acceptance Criteria

  • Improve help text
  • Consider possible combinations of required fields
  • Document recommendations in Figma
  • Update implementation ticket with specific updates
@davidmpickett davidmpickett added Needs refining Issue status UX Facilities Facilities products (VAMC, Vet Center, etc) Design CMS team practice area labels Mar 11, 2024
@davidmpickett davidmpickett changed the title Finalize design recoomendations for Service Location Address paragraph type Finalize design recommendations for Service Location Address paragraph type Mar 11, 2024
@davidmpickett
Copy link
Contributor Author

Found an older ticket that covers some of the this territory with some good insights from users: #8830

@thejordanwood
Copy link

I show this on the Locations headers page in the VAMC Master Figma file.

Status update:

  • It was decided in UX sync that the Name field is required, but the Building name / room number fields will not be required. That's shown in the mockups.
  • I've suggested different help text for the Name field for @davidmpickett and @laflannery to review. There is an open comment thread in Figma discussing this.

@jilladams
Copy link
Contributor

From discussion with Dave / Amanda:

  • We are proposing a pattern for CMS design system, to add input placeholder text
  • Implementation ticket will wait til we have discussed that with Marisa for CMS Team reference.

We'll keep this ticket open to track those steps.

@davidmpickett
Copy link
Contributor Author

From discussion with Dave / Amanda:

  • We are proposing a pattern for CMS design system, to add input placeholder text
  • Implementation ticket will wait til we have discussed that with Marisa for CMS Team reference.

We'll keep this ticket open to track those steps.

So turns out that placeholder text is an accessibility no-no. So we won't be pursuing that. But I think the new UX is a lot clearer than the current implementation

@aklausmeier this is ready for your approval. After you have signed off I will update the implementation ticket.

@thejordanwood
Copy link

@aklausmeier had a small update to this that I've made on the mockups.

@davidmpickett I've updated the implementation ticket to show specific changes, but please feel free to review.

@davidmpickett
Copy link
Contributor Author

Thanks @thejordanwood! I just went through and updated the implementation ticket to be a little more Drupal developer friendly. I also took out the bullet point about making field_clinic_name required. That will have broader content model implications and should be a separate piece of work. All of the other changes are still improvements and can be implemented ASAP

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CY24-Q2 Calendar year Q2 2024 priority Design CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide UX VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

3 participants