Open lyubomir-popov opened 4 years ago
Treeview is used in jaas: https://jaas.ai/ceph-osd/310
Just a heads up this is going away in the near future.
Triaging: Effort high, impacts accessibility. It's a component with relatively small usage. Do we need to address it in v4?
To be discussed with team.
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/WD-15133.
This message was autogenerated
Let's consider it for new arch.
Keyboard support is required, but not implemented (https://www.w3.org/TR/wai-aria-practices/#keyboard-interaction-22). We decided to take this out of the scope of the accessibility audit. The remaining treeview issues are in #3228.
[ ] Each parent node contains or owns an element with role group. Each child node is contained in or owned by an element with role group that is contained in or owned by the node that serves as the parent of that child.
[ ] Each element with role
treeitem
that serves as a parent node has aria-expanded set to false when the node is in a closed state and set to true when the node is in an open state. End nodes do not have the aria-expanded attribute because, if they were to have it, they would be incorrectly described to assistive technologies as parent nodes.