-
Notifications
You must be signed in to change notification settings - Fork 143
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
feat(blade): rebranding whitelabel fix #1959
feat(blade): rebranding whitelabel fix #1959
Conversation
|
✅ PR title follows Conventional Commits specification. |
packages/blade/src/storybook-recipes/ThemePlayground/ThemeSelector.tsx
Outdated
Show resolved
Hide resolved
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 9cb5617:
|
Now that you mention it, I wonder if we should keep the focus ring color static and not tie it with brand color. The focus ring is an fundamental accessibility requirement, if brand color becomes very light then focus ring color won't be visible to the user and could cause accessibility issues. https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html |
Nope, rebranded carousel nav buttons icons are staticBlack. |
Done. |
Hmm. That is fair. I think that we can think about on its own but right now we're using primary color token for the focus ring ideally, it should use the primary color when it changes as well? |
@anuraghazra Tests are failing. Mostly looks good to me. Just need to check
|
Might be the wrong link. Checked again. Looks good |
I've standardized all components to use the |
No description provided.