2.1.1/2.1.3 Keyboard-usage for hoverable additional content on disabled buttons #3522
-
|
We are currently debating about deactivated interactive elements, such as buttons and input fields, where no visible labeling should be used (icon buttons). Active, interactive elements can be focused and hovered. A tooltip (conform to 1.4.13) is displayed as a label. Disabled interactive elements cannot be focused anymore, but can be hovered. We are currently showing the tooltip, it is accessible to screenreaders (linear reading) but not for keyboard-only-users. Here an example: https://public-ui.github.io/sample-react/#/button/basic?theme=zoll-v3 What do you say? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
Transmit the button information?
|
Beta Was this translation helpful? Give feedback.

Now you evaluate ... is the information shown in the tooltip important for somebody to know/perceive even if the control is disabled? If yes, it fails keyboard-related SCs - and authors need to think about how to bridge that particular gap (e.g. making the button/control not actually
disabled, still keyboard-focusable, but usingaria-disabled="true"and extra JS to suppress functionality.If not, it's arguably ancilliary, and a keyboard user is not disadvantaged for not getting the tooltip. suggest then as best practice to suppress the unnecessary tooltip for mouse/pointer users too ... if it's not important for keyboard users, then there's no point for those users to get it…