Itqualityassurance
Yes. Disabled buttons should be focusable. Not only because accessibility, but also to explain in alerts why it is disabled.
- Should disabled elements be focusable?
- Are disabled buttons bad for accessibility?
- Should screen readers read disabled buttons?
- Should a disabled button be clickable?
Should disabled elements be focusable?
Disabled controls should be removed from the focus order, because this is the behavior dictated by the native web pattern for the disabled attribute. This is the built-in behavior, it is familiar to users, and it would require deliberate intervention to change the pattern.
Are disabled buttons bad for accessibility?
Bad accessibility
Sometimes disabled buttons are designed in a way that they cannot be read by a screen reader (buttons are not focusable, and hence users can't reach them with a keyboard). No need to explain that users with disabilities will face problems with such behavior.
Should screen readers read disabled buttons?
Screen readers ignore disabled controls, so screen reader users won't hear the message. Add some nearby visible help text for the button. This would work for sighted users, but not necessarily for low vision users or blind users using a screen reader.
Should a disabled button be clickable?
A disabled button is unusable and un-clickable. The disabled attribute can be set to keep a user from clicking on the button until some other condition has been met (like selecting a checkbox, etc.).
