One of the most common accessibility issues I find (and fix) on client projects is dynamically disabled form buttons when a form is being submitted.
Today I want to talk about why developers do it, why it’s bad, and what you can do instead. Let’s dig in!
Why developers disable buttons Typically, I see the pattern used to prevent a form from being submitted a second time while waiting for the form is processed.

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

Discover why disabling buttons when a form is being submitted is bad for accessibility and learn a better approach to prevent multiple form submissions.

Don't disable buttons