> If the button is the current item in focus when you add the disabled attribute (for example, if someone just pressed it to submit the form), the element actua

> If the button is the current item in focus when you add the disabled attribute (for example, if someone just pressed it to submit the form), the element actually loses focus, which shifts to the document element. > For a screen reader user, this is particularly jarring, as now you’re in a totally different place on the page. This just feels like an argument to abandon a very useful, well understood, and built-in tool (disabling to preventing double form submission) in order to make things better for a small subset of users of a particular tool. Why can't this just be the problem of screen readers? Why is the "solution" to not use or remove a widely used and well understood web standard?