Member-only story

Disabled controls

Never, ever disable buttons — Why not?

In this article, I’ll explain why you shouldn’t disable buttons and answer the inevitable objections. In a subsequent article, I’ll provide more accessible approaches.

Daniel Berryhill
UX Collective
Published in
9 min readNov 5, 2023

A toy cat with an angry face

Contents

Problems with disabling buttons

In this section, we’ll talk about why disabling buttons is a bad solution for your users, including the lack of communication it promotes and how it cannot be perceived by certain users.

Answering objections

We’ll discuss the more common objections to barring disabled buttons, including WCAG’s stance, special use cases, error prevention, and others.

Conclusion

Links

Problems with disabling buttons

User: “Why is it disabled?” Devs: “That’s your problem.”

There certainly are accessibility issues with disabling buttons (which we’ll get to), but even for those that don’t rely on assistive technology (AT), you’re telling them to take a flyin’ leap.

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Published in UX Collective

We believe designers are thinkers as much as they are makers. Curated stories on UX, Visual & Product Design. https://linktr.ee/uxc

Responses (33)

What are your thoughts?