-
Notifications
You must be signed in to change notification settings - Fork 70
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
Comments
Found an older ticket that covers some of the this territory with some good insights from users: #8830 |
I show this on the Locations headers page in the VAMC Master Figma file. Status update:
|
From discussion with Dave / Amanda:
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. |
@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. |
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 |
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:
Steps for Implementation
Acceptance Criteria
The text was updated successfully, but these errors were encountered: