Open 1Copenut opened 2 years ago
Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)
Pinging @elastic/kibana-accessibility (Project:Accessibility)
this is provided by the used code editor in this case so it's not something we can offer in the popover ... what kind of interactions are possible in this case? is this information necessary?
Pinging @elastic/kibana-app-services (Team:AppServicesUx)
Relabeling, because it's related to Monaco, the shared code editor in Kibana
Pinging @elastic/appex-sharedux (Team:SharedUX)
We are considering keeping it a tooltip, but making the text 3x shorter. @1Copenut WDYT?
@1Copenut To adress the concern that the user might miss that it is possible to interact with this content, is there any other possibility to achieve that, instead of making it a popup?
Summary Some of the popovers have a secondary tooltip that opens with instructions how to interact with content. I think it would be beneficial to bring those instructions forward so users have a cue that the content is not just read only.
Relevant WCAG Criteria: Understanding Success Criterion 1.3.1: Info and Relationships - Level A