Disabled buttons should say why. Mine didn't, seven times.
Buttons in my design tool went grey while the AI assistant worked, and none of them said why. The disabled attribute was the reason they couldn't, and one small hook was the fix.

In this story3 sections
I asked the assistant in my design tool to rewrite something, and while it was thinking I went to do the next thing. Rewrite was grey. So was Suggest. I hovered. Nothing. No tooltip, no cursor change, nothing at all. I clicked it twice, the way you knock on a door you already know is locked.
I knew why, because I built it. The assistant was busy, and the app doesn't let you stack a second request on top of the first. Fine rule. But the screen didn't know how to say it. For a second it just felt broken, and if it felt broken to the person who wrote the code, it would feel broken to everyone else.
So I went looking for how many places did this. The answer was 7. The assistant's action buttons. Ask again and Rewind on its answers. Edit on my own messages. Make a visual, in two places, and Ask for changes on one. A practice card. And two menu items that didn't even go grey. They just disappeared while the assistant worked, and came back after.
The textbook way was the problem
Here's the part I got wrong. I had built every one of them the textbook way: the button's disabled attribute. It felt correct, even careful. But a natively disabled button is a dead end. It gets no hover, so a tooltip can't fire on it. It can't take keyboard focus, so someone tabbing through the panel skips right past it and never learns it exists. And my own tooltip made it worse: it only spoke up for icons, on the theory that a button with words already says what it does. The words said what it does. They didn't say why it won't.
So "off" had no way to talk. The hidden menu items were the same mistake, just more honest about it.
One hook for every control
The fix was one small hook that every one of those controls now uses. While the assistant works, a control stays where it is and stays focusable. It looks dimmed, and it's marked aria-disabled instead of disabled, so screen readers still announce it as unavailable. Hover it, or reach it with the keyboard, and the tooltip gives the reason, even over a button that has its own label. Tap it and you get the same line as a note, and nothing else happens.
busy ? { "aria-disabled": true, "data-reason": "", title: tip } : {}The reason itself is short: it's "still working on your last request," and the button will be ready when it's done. That's all anyone needs. What's going on, and what unlocks it. The menu items stopped vanishing and carry the same line.
The catch with aria-disabled is that the browser no longer stops the click for you. So the hook also wraps the action: if the assistant is busy, it shows the note instead of running. That's the trade. You take the job of saying no yourself, and in return you get to say why.
- Places that went grey with no word
- 7
- End-to-end tests green after the fix
- 343/343
A no should say why
I think about it differently now. A grey button is the interface saying no, and a no with no reason sends people guessing: is it broken, is it me, is it loading? Every one of those guesses costs more than one sentence would have.
Before you ship a control that can be off, hover it while it's off and tab to it with the keyboard. If neither tells you why it's off and what turns it back on, use aria-disabled with a reason instead of disabled.



