What are focusable elements with role=presentation?

[JAWS-test]

https://rawgit.com/w3c/aria/master/#presentation:

If an element with a role of presentation is focusable, or otherwise interactive, user agents MUST ignore the normal effect of the role and expose the element with implicit native semantics, in order to ensure that the element is both understandable and operable.

What is a focusable element? E.g. input tabindex=-1 role=presentation: Focusable with mouse, but not with keyboard. Or: input tabindex=-1 role=presentation readonly: Not focusable with keyboard and not operable, but focusable with mouse.
h2 tabindex=0 role=presentation would be focusable with the keyboard - is here role=presentation ignored?
What is "otherwise interactive"? h2 role=presentation is not focusable with the keyboard, but could be interactive with JavaScript.

I would like to ask you to formulate the sentence more unmistakably and possibly give source code examples.

[JAWS-test]

For JAWS test results, see: FreedomScientific/standards-support#256

[JAWS-test]

Maybe the rule can also be abolished, because it doesn't apply to aria-hidden=true either. Moreover, it is poorly supported by assistive technology (NVDA and JAWS) and only confuses the simple concept of role=presentation.

[carmacleod]

What is a focusable element? E.g. input tabindex=-1 role=presentation: Focusable with mouse, but not with keyboard. Or: input tabindex=-1 role=presentation readonly: Not focusable with keyboard and not operable, but focusable with mouse.

These are focusable with javascript.

h2 tabindex=0 role=presentation would be focusable with the keyboard - is here role=presentation ignored?

Yes.

What is "otherwise interactive"? h2 role=presentation is not focusable with the keyboard, but could be interactive with JavaScript.

An example of "otherwise interactive" would be only mouse events on an element, or any crazy thing an author might do that may cause an AT to say "clickable". :)

it is poorly supported by assistive technology (NVDA and JAWS)

That may be a browser issue. See #1042 (comment)

Pull #852 is an attempt to clean up the wording in this section, so I am going to close this issue.