Content
View differences
Updated by Alexander Coles about 1 month ago
##73473 presents a potential accessibility regression that should be investigated.
Copilot left the [following comment on the associated PR](https://github.com/opf/openproject/pull/22838#discussion_r3118662508):
> Removing the dedicated drag handle also removes the only explicit, labelled control for drag-and-drop (previously a focusable button with an aria-label). In handle-less mode, mouse dragging works, but assistive-technology and keyboard users lose a clear affordance/announcement that the item is draggable. Consider keeping a drag handle button for accessibility (it can be visually hidden / only shown on focus) while still allowing handle-less dragging for pointer users.
as well as [this comment](https://github.com/opf/openproject/pull/22838#discussion_r3124523794) in a follow up review:
> Removing the dedicated drag handle means there is no longer any labelled, focusable element that communicates “this card is draggable” to assistive technologies. In handle-less mode this can be a UX/a11y regression because dragging becomes pointer-only with no explicit announcement/instructions. Consider adding an accessible affordance (e.g., a visually-hidden drag handle/button with an aria-label, or an aria-describedby/roledescription on the draggable row) while still allowing pointer dragging from the whole card. <br>
Copilot left the [following comment on the associated PR](https://github.com/opf/openproject/pull/22838#discussion_r3118662508):
> Removing the dedicated drag handle also removes the only explicit, labelled control for drag-and-drop (previously a focusable button with an aria-label). In handle-less mode, mouse dragging works, but assistive-technology and keyboard users lose a clear affordance/announcement that the item is draggable. Consider keeping a drag handle button for accessibility (it can be visually hidden / only shown on focus) while still allowing handle-less dragging for pointer users.
as well as [this comment](https://github.com/opf/openproject/pull/22838#discussion_r3124523794) in a follow up review:
> Removing the dedicated drag handle means there is no longer any labelled, focusable element that communicates “this card is draggable” to assistive technologies. In handle-less mode this can be a UX/a11y regression because dragging becomes pointer-only with no explicit announcement/instructions. Consider adding an accessible affordance (e.g., a visually-hidden drag handle/button with an aria-label, or an aria-describedby/roledescription on the draggable row) while still allowing pointer dragging from the whole card.