WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Managing disabled state of buttons

for

From: Jared Smith
Date: Jan 23, 2019 5:55AM

While Birkir's recommendation makes the button navigable, it
introduces a separate problem. Something that is navigable with the
keyboard inherently means that it is functional. In this case the
button would not be functional, but would be disabled (which is why
the browser removed it from the navigation flow to begin with). So
then the user may confused by interacting with something that doesn't
do anything.

A much more comprehensive analysis of the difficulties of disabled
buttons can be found at https://axesslab.com/disabled-buttons-suck/
I'd stick with Glen's recommendation to not disable the button, and if
you do, know that it's likely to pose difficulties for lots of users.

Jared Smith
WebAIM.org