Why users get stuck
Buttons signal clickability through shape and convention (Norman, 1999). A disabled button switches that signal off without saying why, a hidden affordance (Gaver, 1991) that sends users hunting. Friedman (2021) ranks greyed-out 'Next' buttons at the end of long forms among the most frustrating patterns. See affordance.
Keep it enabled and explain
Forms that state clearly what is wrong get completed more (Seckler et al., 2014). Often it is better to keep the button enabled and, on tap, scroll to the missing field with inline validation. As Flaherty (2024) distinguishes, this is a validation, not an indicator. With a sticky bottom button, a short note like 'Enter your name' near it also helps.
When disabling is right
Disable to prevent double submission during payment or when an option truly does not exist. Distinguish the state clearly (Gordon, 2025) and show the reason, such as 'Processing…'. WCAG 2.2 (W3C, 2023) exempts inactive components from 1.4.3 contrast, but overly faint buttons vanish for low-vision users. The HTML disabled attribute also removes keyboard focus, so consider aria-disabled with explanatory text.
FAQ
- Are disabled buttons always bad?
- No; they suit preventing duplicate submission or unavailable options, provided the reason is shown.
- disabled vs aria-disabled?
- disabled blocks focus and clicks; aria-disabled keeps focus so screen readers can announce the button and its reason.
Sources reviewed: 2026-10-27
References
- Friedman, V. (2021, August). Frustrating design patterns: Disabled buttons. Smashing Magazine. Cases and alternatives to disabled buttons.
- Gordon, K. (2025, April 25). Button states: Communicate interaction. Nielsen Norman Group. Distinguishing button states.
- Flaherty, K. (2024, January 17). Indicators, validations, and notifications: Pick the correct communication option. Nielsen Norman Group. Choosing indicators versus validations.
- Seckler, M., Heinz, S., Bargas-Avila, J. A., Opwis, K., & Tuch, A. N. (2014). Designing usable web forms: Empirical evaluation of web form improvement guidelines. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 1275–1284). ACM. Clear error guidance helps form completion.
- Norman, D. A. (1999). Affordance, conventions, and design. Interactions, 6(3), 38–43. Perceived affordances signal clickability.
- Gaver, W. W. (1991). Technology affordances. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 79–84). ACM. Hidden and false affordances.
- World Wide Web Consortium. (2023). Web Content Accessibility Guidelines (WCAG) 2.2. 1.4.3 exemption and 3.3.1 error identification.