Component Change: Update Pharos Marble Gray Tokens

[david-corneail]

What is the use case for the component change you're requesting?
Update 4 color tokens show in the screenshot and Figma link. They are the lightest 4 marble gray.

Landscape analysis
Figma link. Update the pink outlined sections for the related Pharos tokens.

Additional considerations
Make sure A11y considerations have been met and product teams have been notified of the change if automatically consumed

[david-corneail]

[brentswisher]

👍 They are still listed here so we are good to go, but just for shared knowledge, Pharos uses the HSL values when defining the color variables, not the hex ones

[brentswisher]

@daneah Can you verify my thinking that changing a color token like this is a minor version change, since it's just tweaking an existing color token slightly?

I was initially questioning it as:

• a consumer could be using thee css variable directly somewhere
• the change could then break accessibility rules (depending on the usage)

I'm thinking it's okay as a minor change given the subtle nature of the adjustment, and the alternative would be every time we change a color token we have to make it in a major release, which seems unsustainable.

Since it's the first time we've adjusted an existing token color since I've been here I wanted to see if you had any thoughts though.

[daneah]

@brentswisher Yeah, we've gone back and forth on this in similar situations in the past, for the fact that in some ways any visual change could be a breaking change depending on the magnitude of the change and how that treatment is used, but I have a hard time defending that in practice for changes like this. I will say that a major version bump has little risk, creating tedium, while a minor version bump creates little tedium but has this breakage risk. I would generally version toward risk rather than tedium, so maybe that's a defense of being a major version bump, but I truly don't feel it's a hill I'll die on.

[elisa-vargas]

Thanks for the clarification Brent - as I added these into the Pharos UI kit I found some discrepancies on the HEX values but no change to the HSL - so these are the affected values

NEW HSL
48 1 80 | Marble Gray 80
48 1 90 | Marble Gray
48 1 94 | Marble Gray 94
48 1 97 | Marble Gray 97

https://docs.google.com/spreadsheets/d/1hDK9x3ODGODDa45yXmdH1S6FBxymPM7rnwKfJLxt1tA/edit?usp=sharing