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
In the current version (0.2.5), draggable items are automatically assigned the role="option". This role assignment creates accessibility issues when draggable items contain nested interactive elements, such as buttons or links. Since role="option" implies a selectable item within a listbox, it restricts interactive behavior inside the item.
Problem:
Nested Elements Conflict: Interactive elements (e.g., buttons, links) within the draggable item are not accessible as expected when role="option" is enforced.
Lack of Customization: There is no option to disable or customize the assigned role, which limits the flexibility of the package in complex UIs.
Proposed Solution:
Allow developers to customize or disable the role for draggable items.
Automatically set a more appropriate role (e.g., role="group") when nested interactive elements are detected.
Example Use Case:
In our application, we have draggable taskbar items containing a link and a remove button. The current role assignment prevents proper accessibility and usability of these nested buttons. Our axe integration test fails due to this issue.
The text was updated successfully, but these errors were encountered:
In the current version (0.2.5), draggable items are automatically assigned the role="option". This role assignment creates accessibility issues when draggable items contain nested interactive elements, such as buttons or links. Since role="option" implies a selectable item within a listbox, it restricts interactive behavior inside the item.
Problem:
Proposed Solution:
Allow developers to customize or disable the role for draggable items.
Automatically set a more appropriate role (e.g., role="group") when nested interactive elements are detected.
Example Use Case:
In our application, we have draggable taskbar items containing a link and a remove button. The current role assignment prevents proper accessibility and usability of these nested buttons. Our axe integration test fails due to this issue.
The text was updated successfully, but these errors were encountered: