You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the user moves between TreeSelect options using arrow keys, the screenreader will always read out the value of the active node. It would be much better for accessibility (and more flexible), if I as a developer could decide to use labels for aria-live content instead of the values.
What does the proposed API look like?
New prop would be labelInAriaLive, and it would be false by default. This prob would then be used to decide whether to use the value or label of the selected item, when rendering the aria-live tag of the component.
Using the component with the implemented feature:
<TreeSelect
labelInAriaLive={true} // This is the new prop
treeDefaultExpandAll
treeData={[{ value: 'parent', label: 'parent-label', children: [{ value: 'child', label: 'child-label' }] }]}
multiple
/>
The text was updated successfully, but these errors were encountered:
juhoValkonen
changed the title
TreeSelect: Add "labelInAriaLive"-property for better accessibility
[Feature Request] TreeSelect: Add "labelInAriaLive"-property for better accessibility
May 24, 2022
What problem does this feature solve?
If the user moves between TreeSelect options using arrow keys, the screenreader will always read out the value of the active node. It would be much better for accessibility (and more flexible), if I as a developer could decide to use labels for aria-live content instead of the values.
What does the proposed API look like?
New prop would be
labelInAriaLive
, and it would befalse
by default. This prob would then be used to decide whether to use the value or label of the selected item, when rendering the aria-live tag of the component.Using the component with the implemented feature:
The text was updated successfully, but these errors were encountered: