Carolyn MacLeod

@jlukosky > Since tooltips don't receive focus would your proposal be only for tooltip dialogs or are you proposing to make tooltips focusable? Good question, and I don't have a...

In case it's helpful, I opened https://github.com/w3c/aria-practices/issues/633 to try to address: > I am seeing more and more cases of authors who believe that _something_ must adhere to the APG...

See also Terrill Thompson's post about [Dropdown Navigation Menus](https://terrillthompson.com/1226) (Feb 2020).

@mcking65 You asked about the spec for tabindex: https://html.spec.whatwg.org/multipage/interaction.html#attr-tabindex

Yes, please link to the tooltip dialog pattern rather than the non-modal dialog section.

Regarding tooltip vs title: at present, I am not aware of any way for a sighted keyboard-only user to see the content of the title attribute (unless they are using...

The first sentence of the tooltip pattern is: "A tooltip is a popup that displays information related to an element when the element receives keyboard focus or the mouse hovers...

Regarding having [ESC close the tooltip](https://github.com/w3c/aria-practices/issues/128#issuecomment-299854925), if a tooltip is shown (and focused) when the user types a keyboard shortcut (such as F1, Shift+F1, or F2), then ESC can be...

> Having ESC close the tooltip allows you to close it if it is distracting. > For example, if there were a really big tooltip attached to something which obscures...

Our use case is a code editor. Users can open a tooltip anywhere in the editor, to show the comment for a method or variable, the detailed text of a...