Group position text incorrect

[jnurthen]

Section https://w3c.github.io/core-aam/#mapping_additional_position States

"Otherwise, if the role supports aria-posinset and aria-setsize, process the parent (DOM parent or parent defined by aria-owns), counting items that have the same role."

This is not correct. A menu should count all the menu items no matter the type (menuitem, menuitemcheckbox, menuitemradio) not just items of the same role

[aleventhal]

Maybe simple answer is to say same platform role? It will end up as menuitem on the platform. Or give the menuitemradio/checkbox as a special case.

[mcking65]

Kind of an aside, but does it really mean DOM parent? Shouldn't it be ancestor with the appropriate context role? There could be intervening DOM elements in the tree that are irrelevant and do not contain other elements of the same type.

[joanmarie]

Adding the F2FCandidate label because I think we want to discuss and achieve consensus regarding what we expect/want user agents to calculate.

[joanmarie]

Related: #49

[joanmarie]

@aleventhal: Regarding this:

Maybe simple answer is to say same platform role? It will end up as menuitem on the platform.

Some platforms have different roles for the various menuitem types. See https://w3c.github.io/core-aam/#details-id-46

[joanmarie]

Perhaps (from Matt): Counting items that have one of the required owned element roles within the context.

[joanmarie]

We also have to deal with: associationlistitemkey and associationlistitemvalue. Should these even support aria-posinset and aria-setsize?

[joanmarie]

Another thing which is incorrect about this text:

aria-level, aria-posinset, and aria-setsize are all 1-based. When the property is not present or is "0", it indicates the property is not computed or not supported. If any of these properties are specified by the author as either "0" or a negative number, user agents SHOULD use "1" instead.

We don't want user agents failing to expose aria-setsize set to -1 because that means the set size is unknown.

See related:

• Revisit aria-setsize="-1" authoring requirement aria#1759
• aria-setsize when set to -1 should suppress stating the total number of items.  nvaccess/nvda#9823

[joanmarie]

We also have to deal with: associationlistitemkey and associationlistitemvalue. Should these even support aria-posinset and aria-setsize?

Regarding the above, some implementation experience with the HTML equivalent convinces me that they not only should be supported, authors should be encouraged to provide values, and failing that user agents should calculate them. See related w3c/html-aam#415