Web Accessibility Cookbook

Disabling buttons can cause more problems for users than benefits.

Missing feedback

When you click a disabled button, nothing happens. The button doesn’t explain what’s wrong or help you fix the problem. It provides no helpful feedback. If the user thinks their answers are correct, not providing feedback can make the UI feel broken.

Missing focus

Disabled buttons are not focusable, so screen reader users who use the Tab key to navigate might not know that there even is a button. If the button’s styling isn’t obvious, it may confuse keyboard users trying to focus the button.

Low contrast

WCAG’s minimum contrast rule doesn’t apply to disabled controls, but they’re often hard to read, especially for people with low vision.

Deception

It’s not always apparent that buttons are disabled. Some users will try to click them; if nothing happens, they can feel irritated, confused, or disappointed. That may occur because the design isn’t distinct or because disabled buttons usually contain call-to-action words like “submit,” “send,” or “order,” which lure users into clicking them.

Solution

Don’t disable buttons. Users should always be able to interact with them and get feedback.