Valid children for Focusable?

[Faithfinder]

I'm trying to migrate some of our legacy code to RAC Tooltip, and there's a use case that's puzzling me.

We're sometimes showing a tooltip with full version of truncated text. I don't mind making it focusable for accessibility, but I don't know what the correct role is, or where to look. Googling doesn't really help, unfortunately.

[snowystinger]

We typically recommend using the role "button" which would allow you to expand support to touch users as well potentially who ordinarily cannot access a tooltip.

Some other options might be to create a button that's just the ... as suggested here:
https://stackoverflow.com/questions/17206815/accessibility-using-title-attribute-for-truncated-text

Not using text truncation, such as discussed in https://www.tpgi.com/the-ballad-of-text-overflow/

Unfortunately this page isn't finished yet https://www.w3.org/WAI/ARIA/apg/patterns/tooltip/ but hopefully it'll have more information in the future about this pattern.

[Faithfinder]

Sure, I also dug in the source code for a list of accepted tags and roles, but could that be added to the docs? While I understand the list isn't entirely arbitrary, I don't think it's googlable

[snowystinger]

We do show it on a native button and applying role = button in our tooltip docs. We don't show others, but I think it would heavily depend on the use case.

It would need to be a role that supports interactions https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles#widget_roles but where the interactions don't conflict. I realise that is a bit nebulous, so maybe we could clarify what all Focusable and Pressable include in terms of used interactions. But I think it's fairly safe to assume that focus/blur/pointer/keyboard are the events we use. Fortunately we don't use too many keys for the keyboard, so not too much to look out for there.

We could add some other instances where we think it might be common for people to use tooltips. But we've also gotten feedback that our docs are too verbose already, so would like to err on small single examples where possible.

[Faithfinder]

I did get used to the docs at this point =P But yes, they are super verbose for a newbie.

Not everything has to be on the "main" docs page though. There's asides, expanders etc for extra information that would be overload for a normal person. A link to the list in source is even fine for me :)

I don't want more examples. I'm just saying that "Hmm, my use case doesn't look like a button, what else can I use?" is a question that's super natural to ask, and the list isn't googleable.