Recent searches
Search options
At GOV.UK we avoid disabling buttons.
If the user submits a form with a problem, they get a useful error message telling them how to fix it.
Disabled buttons are hard to make accessible for people with low vision, and can't easily be focused using the keyboard
@joelanman I like this but find myself being pushed to disable buttons. Have you explored using the button space to show any errors where the user will be looking in order to progress –they might avoid a failure and the wait for a new page to load?
Interested in what you think and if you’ve tried it.
@del Yeah I think people who disable buttons often want to rely on inline validation but it's such a hard pattern to get right. When are people done with their input? How do you make sure screen reader users are definitely aware of it. You have to keep it synced up on terms of rules with your back end validation. It adds to page weight. So many things to navigate for little value
@del and still you can't be sure some people won't try and click the button and get no feedback, and some people can't even read it if it's disabled