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
Running the toolkit on a page with a disabled button, the toolkit shows an error and identifies that button as not having enough color contrast (the button is light gray with white text).
Sufficient color contrast is not needed for disabled elements, according to WCAG 2.0.
To Reproduce
Identify any steps required to reproduce the behavior and/or link to a test case that demonstrates the issue.
Create or find a webpage with the following markup: <button disabled>Test</button>
and with the following styling: button:disabled { background-color: #e8e5e1; color: #ffffff; }
Run the ARC toolkit to confirm error.
Expected behavior
There should be no error regarding color contrast for disabled buttons.
Screenshots
Markup of button:
Version information
Browser and version: Chrome 120.0.6099.71
ARC Toolkit version: 5.6.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Thank you for looking into it! I also just learned another team we're working with found the same issue with a disabled checkbox, so I just want to flag that all disabled HTML elements should not get an insufficient color contrast error.
Describe the bug
Running the toolkit on a page with a disabled button, the toolkit shows an error and identifies that button as not having enough color contrast (the button is light gray with white text).
Sufficient color contrast is not needed for disabled elements, according to WCAG 2.0.
To Reproduce
<button disabled>Test</button>
and with the following styling:
button:disabled { background-color: #e8e5e1; color: #ffffff; }
Expected behavior
There should be no error regarding color contrast for disabled buttons.
Screenshots
Markup of button:
Version information
Additional context
The text was updated successfully, but these errors were encountered: