G100 accessibility: contrast issues with danger/error tokens and active states on elevated layers #21437
ashokrulz20
started this conversation in
Accessibility
Replies: 1 comment 1 reply
-
|
Please refer below images attached. 1.Danger Tertiary button on elevated layers (G100)
2.Error text on Layer 03 (G100)
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment






Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Carbon Design team,
We are looking for clarification on a few G100 accessibility questions related to elevated layers, as we’re seeing WCAG 1.4.3 contrast failures in several valid-looking token/state combinations.
We want to confirm whether this is an understanding gap on our side, or if there is recommended guidance we should be following for these scenarios.
1) Danger Tertiary button on elevated layers (G100)
Danger Tertiary has no fill, so the label color sits directly on the background layer.
In our contrast checks:
Questions:
2) Error text on Layer 03 (G100)
When error messaging uses:
we see a color-contrast failure between the error text and the background.
Questions:
3) Contained List "Active" state contrast on Layer 3
On Layer 3, when a Contained List item is Active, we see:
layer-active-03 = #8D8D8Dtext-primary = #F4F4F4This results in ~3:1 contrast, failing WCAG 1.4.3 for normal-size text.
Questions:
Appreciate any guidance on the intended usage patterns here — especially around elevated layers — so we can align with Carbon’s accessibility expectations.
Beta Was this translation helpful? Give feedback.
All reactions