[TreeView] Investigate if aria-activedescendant attribute is necessary

[LukasTy]

Created from: #12226 (comment)

It looks like the tree role is not listed to support aria-activedescendant attribute.
W3C examples seem to confirm it by not having this attribute in their examples.

To be confirmed with other libraries and checking the behavior after removing it.

Search keywords:

[flaviendelangle]

Found in https://www.w3.org/WAI/ARIA/apg/patterns/treeview/

The tree role supports the aria-activedescendant property, which provides an alternative to moving DOM focus among treeitem elements when implementing keyboard navigation. For details, see Managing Focus in Composites Using aria-activedescendant.

If a component container has an ARIA role that supports the aria-activedescendant property, it is not necessary to manipulate the tabindex attribute and move DOM focus among focusable elements within the container. Instead, only the container element needs to be included in the tab sequence. When the container has DOM focus, the value of aria-activedescendant on the container tells assistive technologies which element is active within the widget.

So, from what I understand, it was needed before, but no longer is since we focus the item directly

[LukasTy]

So, from what I understand, it was needed before, but no longer is since we focus the item directly

Yes, makes total sense. 👍

[github-actions]

⚠️ This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

@LukasTy: How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.