Why we consider disabled buttons to be an anti-pattern

1. They block action without explaining why
A disabled button tells you something’s wrong… but not what. Users end up guessing

2. They provide zero feedback
Click, and nothing happens. Without an error or guidance, the user can easily get frustrated.

3. They feel like bugs
If a user thinks everything is valid but the button stays disabled, the UI feels broken or unresponsive.

4. They hurt accessibility

Low contrast: hard to see

Not focusable: keyboard/screen reader users get blocked

5. They increase cognitive load
It is rude to waste visual and mental energy for users to see UI that is not relevant or not possible in their situation.

What works better

Keep buttons enabled, or don't show a button that cannot be pressed

Validate on click, and show clear, immediate error messages

References

Smashing Magazine: Disabled Buttons UX analysis

Adam Silver: The problem with disabled buttons

Smart Interface Design Patterns: Disabled buttons UX

Nielsen Norman Group: Button states & interaction