Itqualityassurance
- Should a disabled button be clickable?
- When should you disable a button?
- Why you shouldn't use disabled buttons?
- Should you disable button UX?
Should a disabled button be clickable?
A disabled button is unusable and un-clickable. The disabled attribute can be set to keep a user from clicking on the button until some other condition has been met (like selecting a checkbox, etc.).
When should you disable a button?
A disabled button is used to visually communicate that the action is unavailable because certain conditions aren't met. However— when it lacks feedback, context, and guidance— the experience may feel frustrating, confusing, and inaccessible.
Why you shouldn't use disabled buttons?
Bad accessibility
Grey buttons with gray labels can easily fail to meet color contrast recommendations for text. Sometimes disabled buttons are designed in a way that they cannot be read by a screen reader (buttons are not focusable, and hence users can't reach them with a keyboard).
Should you disable button UX?
While designing the UI, avoid using a disabled button as it becomes hard to find out why it is disabled and what should be done to make it enable. It is better to keep buttons enabled all the time and highlight the field if users don't provide the required information.
