INTRODUCTION
Every product has one: a pale grey Continue button at the bottom of a form. You tap it. Nothing happens. No message, no shake, no hint. Somewhere above, a field is missing or a box is unticked, and the button knows which one. It just will not say.
A disabled button feels like help. It stops people from submitting something incomplete, and it looks tidy in a design review. In practice, it often turns a simple rule into a riddle. This piece is about when to disable a button, and when to leave it alone and explain instead.
What disabled actually does
In HTML, the disabled attribute does more than change a colour. As MDN documents, a disabled control cannot be focused, does not receive clicks and is not submitted with the form. Someone moving through the page with a keyboard or a screen reader can skip right past it and never learn it exists, let alone why it is off.
Then there is contrast. WCAG’s minimum-contrast rule explicitly exempts text in an inactive user interface component. That exemption is reasonable for a control that genuinely does not matter right now, but it means designers are free to make the most important button on the screen the hardest one to read.
The GOV.UK Design System puts it plainly: disabled buttons have poor contrast and can confuse some users, so avoid them if possible, and only use them if research shows they make the interface easier to understand.
The real cost is the missing reason
A disabled button encodes a rule the person cannot see. “You need to accept the terms.” “The postcode is not valid yet.” “Choose a delivery slot first.” The product knows the rule and the current state, and it compresses both into a single grey rectangle.
An active button that validates on submit does the opposite. The person presses it and the product answers: this field, this problem, this fix. It costs one round trip, and it turns a mystery into an instruction. The same logic applies to buttons that are enabled and disabled as people type: the state flickers while they are still working, which is noise rather than guidance.
When disabling is right
There are honest cases for it. The clearest is preventing a second submission while the first request is still in flight. GOV.UK’s button offers a double-click guard, and its guidance adds two caveats worth keeping: protect against duplicates on the server too, and tell people what is happening on slow connections. We made the server-side half of that argument in A retry button is a promise your backend has to keep.
The second case is an action that genuinely does not apply in the current context, such as Paste with nothing on the clipboard, inside a menu or toolbar. There, the WAI-ARIA Authoring Practices suggest keeping disabled items focusable with aria-disabled="true", so keyboard and screen-reader users still discover them.
The serious counterargument is that an active button invites people to submit broken forms, and a wall of errors feels worse than a quiet grey button. That is true when the errors are badly written. The answer is a better error message, not a hidden one. If your research shows a disabled state really is clearer for your audience, GOV.UK’s condition is met; most teams have simply never tested it.
A worked example
Imagine a sign-up form whose Create account button stays disabled until a terms checkbox is ticked. On a small phone, the checkbox sits just below the fold, under the keyboard. People fill in their name, email and password, see a grey button, tap it a few times and leave. Nothing is broken. The form is working exactly as designed.
Keep the button active instead. When it is pressed with the box unticked, move focus to the checkbox, scroll it into view and show one sentence next to it: “Accept the terms to create your account.” The rule is the same. The person now knows it. This example is hypothetical; it describes a pattern, not a client.
What to do this week
List every disabled primary button in your product. For each one, write down the rule that disables it, in a sentence a customer would understand. If you can write that sentence, the product can say it, at the moment the button is pressed. Keep disabled states for requests in flight and for actions that truly do not exist yet, and even then make sure people can find out why.
Sources checked on 16 November 2026: GOV.UK Design System button guidance, WCAG 2.2 Understanding 1.4.3, MDN’s disabled attribute reference and the WAI-ARIA Authoring Practices keyboard guide.