-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
AVT2 - The content of tooltip can't be focused and operable #4414
Comments
Please provide a reduced test case we can debug against. 🙏 Testing against our Tooltip example here I was unable to reproduce your issue. Can you confirm that this is the case? |
@dakahn OK, seems it is not carbon issue. Close this issue. |
@dakahn I believe this is a Carbon react tooltip issue. Steps:
It is not possible to activate the Learn more link or Create button using only the keyboard. So please reopen. Thanks! Also, please note:
|
@carmacleod @dakahn This issue also affected our AVT test, will it be fixed recently? |
@cmqchen Just so you know, I'm not on the Carbon team - I am "just a user". :) |
@cmqchen This issue is in our backlog with a priority of low. Legacy versions of Carbon are fixed as our bandwidth allows, but do not take priority over our v10 backlog. That said we're always accepting PRs if you need a fix sooner rather than later. |
@dakahn It is blocking accessibility compliance for GA. Hope this problem can be fixed as soon as possible. |
@emyarod This issue is also existed in Carbon 10. If it fixed, please push the fix into Carbon 10. Thank you! |
@emyarod which carbon versions have the fix? |
@icemanlily it looks like this fix was included in |
This issue can be closed. I just tried react and vanilla, and I can navigate to focusable content using keyboard in the "tooltip" (dialog). Esc closes. |
Environment
macOS Mojave version 10.14.6
Chrome Version Version 77.0.3865.90
Carbon v9 - React
Description
Use keyboard to open a tooltip
The content of the tooltip can't be focused and opeable
The text was updated successfully, but these errors were encountered: