fix(icons): use the non-shade alias color for info status icons

[astorije]

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)
• [ ] If applicable, have a visual design approval

PR Type

What kind of change does this PR introduce?

• [x] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] clarity.design website / infrastructure changes
• [ ] Other... Please describe:

What is the current behavior?

The current info status icons are colored with the shade variant, which gives the icon a very low contrast in dark theme.

This is particularly true for regular-sized icons (i.e. smaller than lg):

Issue Number: N/A

What is the new behavior?

This change aligns the info icons more closely with, well, most everything else such as cds-buttons which are displayed using the non-shade version, as well as non-info icons. As you can tell below, the impact on light theme is negligible, but in dark theme the contrast seems much better:

And on smaller icons:

Does this PR introduce a breaking change?

• [ ] Yes
• [x] No

[vmwclabot]

@astorije, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement. Reject reason:

Please provide city, state (or province), and country of residence or mailing address.

[github-actions[bot]]

👋 @astorije,

• 🙏 The Clarity team thanks you for opening a pull request
• 🎉 The build for this PR has succeeded
• 🔍 The PR is now ready for review
• 🍿 In the meantime, checkout out a preview of this PR
• 🖐 You can always follow up here. If you're a VMware employee, you can also reach us on our internal #clarity-support Slack channel

Thank you,

🤖 Clarity Release Bot

[vmwclabot]

@astorije, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed.

[vmwclabot]

@astorije, VMware has rejected your signed contributor license agreement. The merge can not proceed until the agreement has been resigned. Click here to resign the agreement. Reject reason:

Please provide a telephone number and full address. Please provide the name of the organization you are affiliated with or indicate none. Note: If you are a VMware employee please use your VMware email and you are then not required to execute the VMware CLA.

[vmwclabot]

@astorije, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed.

[vmwclabot]

@astorije, VMware has approved your signed contributor license agreement.

[astorije]

@kevinbuhmann and @colinreedmiller, friendly ping? :)

[kevinbuhmann]

@kevinbuhmann and @colinreedmiller, friendly ping? :)

I posted in our internal Slack channel for someone on our design team to review this.

[colinreedmiller]

@kevinbuhmann and @colinreedmiller, friendly ping? :)

I posted in our internal Slack channel for someone on our design team to review this.

We need to complete the token mapping evaluation across the themes to determine what the design guidance will be. The current use of --cds-alias-status-warning is problematic in dark theme barely meets contrast and the suggested fails to leverage the change to yellow for warning status - the info status is correct.

[astorije]

Thanks all!

[github-actions[bot]]

:tada: This PR is included in version 6.4.1 :tada:

The release is available on:

• GitHub release
• v6.4.1

Your semantic-release bot :package::rocket:

[github-actions[bot]]

Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed PRs after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary.