-
Notifications
You must be signed in to change notification settings - Fork 67
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
Fix Alert colors #2339
Fix Alert colors #2339
Comments
Hey team! Please add your planning poker estimate with Zenhub @Andrew565 @ataker @harshil1793 @it-harrison @jamigibbs @micahchiang @nickjg231 @powellkerry @rmessina1010 @rsmithadhoc |
In addition, the following Alert colors are incorrect:
|
@humancompanion-usds I've noticed that like info alert others doesn't match with the USWDS colors. Would you like the other alerts to be fixed as well? |
@danbrady , since you're working on Alerts, can you chime in since Matt is out? |
Yeah, I think we should be updating all the colors in alert to the USWDS colors. You might want to check with @powellkerry who is working on updating the tokens/vars (#2324) which I think would be needed here? |
@danbrady, I've noticed that the tokens were already in place, and I'm able to use them. |
Description
Update colors in all Alert Banner status types
From Matt:
The info alert has 2 background colors, which you can't see until it reaches a certain width. In Figma we are using the component level tokens (vads-alert-color-background-info-on-light), which I realize adds a level of complexity because we're not yet using those in the components themselves. USWDS switched from primary-alt to info (state tokens: info, info-light, info-lighter, etc.) in Alert. We're not using those tokens yet either in the component itself. So we need to fix that so that our info Alert actually matches USWDS.
Details
Figma - Alert - https://www.figma.com/file/afurtw4iqQe6y4gXfNfkkk/VADS-Component-Library?type=design&node-id=539%3A4085&mode=design&t=nDqXz5T9BrUSbxTi-1
Tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: