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

treeitem scope should allow group with accessibility parent tree #2014

Open
pkra opened this issue Aug 29, 2023 · 3 comments · May be fixed by #2094
Open

treeitem scope should allow group with accessibility parent tree #2014

pkra opened this issue Aug 29, 2023 · 3 comments · May be fixed by #2094
Assignees
Labels
clarification clarifying or correcting language that is either confusing, misleading or under-specified Role Content Model
Milestone

Comments

@pkra
Copy link
Member

pkra commented Aug 29, 2023

Extracted from #2010 (comment)

We currently only have group with a treeitem parent but the group can have a tree parent as well.

@pkra pkra added the clarification clarifying or correcting language that is either confusing, misleading or under-specified label Aug 29, 2023
@pkra pkra added this to the ARIA 1.3 milestone Sep 2, 2023
@mcking65 mcking65 linked a pull request Dec 17, 2023 that will close this issue
8 tasks
@mcking65
Copy link
Contributor

mcking65 commented Dec 17, 2023

@pkra

Didn't you mean the opposite? the current editor's draft allows group as a child of tree, but that is inconsistent with the definition of treeitem. I submitted #2094 to fix this.

Trees do not have a concept similar to optgroup. If you want to group treeitems, they need a parent treeitem.

All the accessibility children of a tree need to be either parent treeitems or end node treeitems.

Even if a tree is partially virtualized, it seems to me that the rendered nodes should have their hierarchy represented in the DOM. If it were not, the tree would be inoperable.

I was inspired to investigate this by @WilcoFiers moment of confusion described in w3c/aria-practices#2887.

@pkra
Copy link
Member Author

pkra commented Dec 18, 2023

@mcking65 I was primarily concerned with the inconsistency. I have no strong opinion on how to resolve that inconsistency.

@MarioBatusic
Copy link
Contributor

In my opinion, the only problem in the spec 1.3 is, that the tree role allows group role additionally to the treeitem role. What schould this group represent at all?
All other stuff is OK and correct - and works now for years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification clarifying or correcting language that is either confusing, misleading or under-specified Role Content Model
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants