Open jonseitz opened 3 years ago
This was held up because of accessibility concerns with using disabled
on buttons, as that can often hide the button from assistive technology without any indication that the button can be "enabled" at another point. It needs further review.
Our Button and Borderless Button components both accept a "disabled" prop that gets passed to the underlying
<button>
element, but that only prevents theonClick
handler from being fired -- it doesn't change the styling to signal to the user that the can't click the button, and the:hover
and:active
pseudo-classes still get applied so it just looks like something is broken.We should, at a minimum, set
cursor: not-allowed
on:hover
. We can also switch to a "ghosted" background/text for those buttons to provide a passive visual indicator, and one that will apply on mobile.