Implicit role=presentation except for Required Owned Elements

[JAWS-test]

I suspect that there are some elements whose child elements are implicitly output without role and status, except for the "Required Owned Elements". which means they have "Children Presentational: true" except for the "Required Owned Elements". An example would be treeitem, which may only contain treeitem or group, but certainly no links, buttons or checkboxes. Unfortunately this is often found in practice (e.g. treeitem with child element checkbox instead of aria-checked), because in my opinion the specification does not regulate this exactly. Maybe I overlooked such a regulation. But if not, this should be added to the specification.

[mcking65]

@JAWS-test commented:

I suspect that there are some elements whose child elements are implicitly output without role and status, except for the "Required Owned Elements". which means they have "Children Presentational: true" except for the "Required Owned Elements".

I am not sure what you mean by "output". If you are talking about screen reader output, this is a consequence of the fact that names are flat strings that do not have embedded semantic information.

An example would be treeitem, which may only contain treeitem or group, but certainly no links, buttons or checkboxes.

This is the question being asked by #1033 (Clarify "required owned element").

Unfortunately this is often found in practice (e.g. treeitem with child element checkbox instead of aria-checked), because in my opinion the specification does not regulate this exactly. Maybe I overlooked such a regulation. But if not, this should be added to the specification.

The spec does communicate that non-composite widgets cannot have focusable, interactive descendants. However, there are others asking for additional clarification of this rule. See #1028 (Each ARIA role entry characteristics table should have a "can have focusable descendants" entry).

I am pretty sure this issue duplicates #1033 and #1028. So, I am closing as a duplicate. If I am misinterpreting, please let me know and we can re-open it.

[JAWS-test]

@mcking65

The spec does communicate that non-composite widgets cannot have focusable, interactive descendants.

Where can I find it?

I am pretty sure this issue duplicates #1033 and #1028

#1033 and #1028 don't cover the same topic (I had read them before creating my ticket), but they are relatively similar (for example, I'm not only interested in interactive elements, but also in the question of whether elements other than the required ones can be included at all, e.g. a heading). In this respect the closing is ok.