3 ms·
Not sure I would make the "disabled" buttons stand out more brightly than a regular button. In fact I would swap the colors of those buttons, or maybe make the
by kmoser 3y ago
Not sure I would make the "disabled" buttons stand out more brightly than a regular button. In fact I would swap the colors of those buttons, or maybe make the disabled button greyed out.
- infotainment 3y agoAgreed. One thing that a lot of people miss when attempting to comply with WCAG contrast guidelines is that disabled controls are specifically exempt. With good reason, IMO — too much contrast and it’s not clear that an element is disabled.
- geraldwhen 3y agoAnd yet younguns with good eyes and no color blindness will be able to read the text, and others won’t. If you let a designer put grey on grey once, they’ll do it 10,000,000 times.
- louismerlin 3y agoI limited myself to black and white when creating the style-sheet, but maybe I should indeed add some kind of indicator for the "disabled" button, such as hatchings. edit: hatchings make the inner text unreadable, I'll play around with opacity and dotted lines, thank you to the users who proposed them. edit 2: went with dashed lines and published a new version. It even shaves off a couple of bytes off the minimized version :D
- krsdcbl 3y agothis could be a rare but very practical usecase for strike-through text
- yreg 3y agoWow, I love that!
- topicseed 3y agoOpacity maybe would help here.
- yreg 3y agoCould border-style dashed/dotted work?
- PetitPrince 3y agoHatching seems an excellent idea.
- kthartic 3y agoHmm I think the dashed lines still don't say to me "disabled" unless you told me. It looks more like a secondary button (eg "Go back" or "Cancel"). I really do think the use of reduced opacity would make sense here :)
- sn0wleppard 3y agoThe buttons also need a hover/focus state, easy win for accessibility there