This generally speaks to HTML buttons being disabled using the disabled attribute. - Disabled buttons fool users into clicking because they often match what people want to do. When nothing happens, it is frustrating and can cause them to feel stupid. - Disabled buttons are often difficult to see because they don't have enough contrast. - 99% of disabled buttons do not provide feedback as to why they are disabled. If the user doesn't have permission to use the button, tell them. - On forms, you cannot expect users to understand that the reason the submit button is disabled is because they haven't filled out all required fields. - “Users don't want to think about your interface, they want to complete tasks with as little effort as possible.” - Related: Don’t Make Me Think by [[Steve Krug]] - Screen readers and switches are usually unable to navigate to disabled buttons because they simulate keyboard navigation, creating a significant [[Accessibility]] issue. - Instead of disabling the button, provide it with an alternate style. Put focus on an error message if it’s clicked or there's something wrong. --- ## Reference [[Hampus Sethfors]]. “Disabled Buttons Suck.” *Axess Lab*, 7 July 2017, [axesslab.com/disabled-buttons-suck/](http://axesslab.com/disabled-buttons-suck/). Accessed 31 Mar. 2020. ## Read later [Frustrating Design Patterns: Disabled Buttons — Smashing Magazine](https://www.smashingmagazine.com/2021/08/frustrating-design-patterns-disabled-buttons/?ref=sidebar?ref=uxdesignweekly)