-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block controls: Show tooltip on hover, keyboard focus #531
Comments
If it's essential information, it should probably not be shown on hover, and if it isn't, should it be shown at all? (I know this is different in the current editor) |
I'd say on both, with the caveat that when a control gets clicked or activated with the keyboard, is stays "focused", unless focus is moved somewhere else. So there should be a way to hide the tooltip after the control activation. Worth noting visual tooltips can be built in an accessible way and using just CSS, using the content property and targeting the |
Thanks for pointing to the GitHub example @afercia , I think we could make something like this work for our case. Based on the styles, it appears they're capturing the |
Description of the ARIA tooltip pattern, still in development: |
Worth noting that also the block toolbars don't have any tooltip at the moment. Not even the "Classic Text" one, that uses the native TinyMCE controls: While the same controls in the old editor do have tooltips: Right now, they're also used to inform users about the associated keyboard shortcuts. That seems something valuable to me. |
It would also be good to add tooltips to the image toolbar so the user can understand what each icon does before clicking it. |
Considering this closed by #2293 |
Block controls have a
title
property associated with them (example). Currently this is only assigned as thearia-label
of the renderedIconButton
component. This isn't exposed when hovering the button, so it's hard to know what action is associated with a particular block control.The text was updated successfully, but these errors were encountered: