The article seems to discourage disabled buttons for accessibility reasons also. The article uses the wording “re-enable the button after the API responds”, bu

The article seems to discourage disabled buttons for accessibility reasons also. The article uses the wording “re-enable the button after the API responds”, but doesn’t elaborate on failure/timeout. There’s other stuff you may want to do, like persist form data. Or if you go with the article’s recommendation of preserving the button, but make it inert, perhaps add some indication to what the request is doing. There is nothing as a “sufficiently smart” website that altered the browser’s visual language of page loading progress. Meetup.com is doing this to me lately; some links I just don’t know if they’re broken, or my net is being slow, and I’m being impatient.