Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should user agents calculate aria-posinset and aria-setsize on treegrid row if there is no author-provided value? #1602

Open
joanmarie opened this issue Aug 20, 2021 · 5 comments
Milestone

Comments

@joanmarie
Copy link
Contributor

joanmarie commented Aug 20, 2021

In ARIA 1.2, aria-posinset and aria-setsize became supported properties of row if that row lives in a treegrid.

I have to confess that I don't understand the difference between aria-posinset and aria-rowindex in the context of a treegrid row. Ditto for aria-setsize versus aria-rowcount.

Assuming the author and user do understand these differences, exposing it to ATs is fine. But the spec also says under aria-posinset:

If all items in a set are present in the document structure, it is not necessary to set this attribute, as the user agent can automatically calculate the set size and position for each item.

For user agents that DO this calculation for other roles, e.g. menuitem, listitem, tab, etc., should they be doing so for row?

Personally that strikes me as leading to potential chattiness. Then again, it might be seen as weird to not calculate on row but calculate it on all the other roles.

Some guidance in the spec would be useful. Also, if the answer is calculate it, how is the calculation different from that of rowindex and rowcount?

@joanmarie
Copy link
Contributor Author

joanmarie commented Aug 20, 2021

Just found #1303 and w3c/aria-practices#1442.

In the latter, Matt says:

It does seem like we have made aria-rowindex redundant with aria-posinset in treegrids.

And in the former, he says:

We should consider prohibiting aria-rowcount and aria-rowindex on rows in a treegrid. Using them instead of or in addition to aria-posinset and aria-setsize could create problems.

So silly me has a new question: Why exactly did we add aria-posinset as a supported property on treegrid row in ARIA 1.2 (on 21 Aug 2018, according to the list of Substantive changes) when aria-rowindex was already a supported property on it in ARIA 1.1?

But I'm starting to think that the answer to the question I asked in the opening report is: "Yes, user agents should calculate them using the very same calculation as they would for rowindex and rowcount"

@joanmarie
Copy link
Contributor Author

Here's the issue where aria-setsize and aria-posinset were added to row descending from treegrid: #558

@jnurthen
Copy link
Member

@aleventhal can you please help.

@joanmarie
Copy link
Contributor Author

joanmarie commented Dec 9, 2021

Straw poll done during today's ARIA WG meeting:

Yes: 9
No: 0
Abstention: 1

@jnurthen
Copy link
Member

@jnurthen jnurthen removed the Agenda label Dec 15, 2021
@pkra pkra added this to the ARIA 1.3 milestone Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants