You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FWIW, it's not clear here if what needs to change is Figma or the component styles. I checked the va-checkbox component's error styling, and it's pulling from the .usa-error-message class, which is set at the same color as our vads-color-secondary-dark (see attached screenshot). We can easily override this color to whatever color we want, though, if we decide the component needs to change.
The key point is that USWDS uses $theme-color-error-dark (#b50909) for error text, borders, etc., and not$theme-color-error (#d54309). See USWDS color tokens.
I took a look at all components that have an error state and updated any that used the vads-color-error token to use $vads-color-error-dark instead (which maps to the USWDS value).
These are the components that were updated:
Form Elements:
Label
Error Text
Hint Text
Label Header
Date Input
File Input
Memorable Date
Privacy Agreement
Radio Buttons
Select and Select Element
Statement of Truth
Text Input and Text Input Element
Textarea and Textarea Element
(This list is also in the publishing notes on the Form Elements page.)
Bug Report
What happened
I was comparing output between figma and staging/production and noticed the error colors are not the same.
What I expected to happen
I expected figma and production to be using the same color for error messages
Reproducing
Steps to reproduce:
Here is a screenshot
The image on the left is from staging, on the right is a brand new component built using VADS component library.
It looks like Figma is using
vads-color-error
whereas the code is usingvads-color-error-dark
.Urgency
How urgent is this request? Please select the appropriate option below and/or provide details
Details
Estimating
Designers:
Provide your estimate of 1, 2, 3, 5, 8 or 13
@babsdenney
@danbrady
@LWWright7
The text was updated successfully, but these errors were encountered: