Keyboard accessibility limits in Program Board drag-and-drop workflows
0 reputation · 08 Dec 2023, 13:29 UTC
0 reputation · 08 Dec 2023, 13:29 UTC
Jira Align aims for WCAG 2.1 Level AA compliance, but current Accessibility Conformance Reports (ACRs) indicate gaps in interactive elements. A primary concern involves the Program Board, specifically regarding the movement and ranking of features and dependencies.
The current interface relies heavily on pointer-based interactions for feature ranking and dependency line creation. According to documented conformance gaps, these workflows lack full keyboard alternatives, creating a barrier for users who cannot use a mouse.
While standard navigation is supported, the specific action of reordering items or mapping dependencies via drag-and-drop does not consistently provide a keyboard-operable equivalent that meets WCAG 2.1.1 (Keyboard) and 2.5.1 (Pointer Gestures) standards.
What are the documented keyboard-equivalent methods for ranking features on the Program Board? Is there a configuration to enable accessible alternatives for dependency mapping?
34775 reputation · 08 Dec 2023, 21:46 UTC
No documented keyboard-equivalent method exists for ranking features on the Program Board, and there is no configuration or feature toggle to enable an accessible alternative for dependency mapping in current releases.
Atlassian's published Accessibility Conformance Report for Jira Align, VPAT 2.4, lists Program Board drag-and-drop reordering of features and dependency line creation as non-conformant to WCAG 2.1.1 Keyboard and WCAG 2.5.1 Pointer Gestures. The report states the workflows lack full keyboard equivalents.
Confirmed: the gap is documented and remains open. Atlassian accessibility statements indicate ongoing work on interactive elements, but no keyboard alternative has shipped for Program Board ranking or dependency drawing.
Likely, not confirmed: the gap persists because Program Board components are locked-down React surfaces that are not exposed to ScriptRunner or Forge extensions for custom keyboard handlers. This is a product limitation, not a misconfiguration.
Assumption: you are on Jira Align SaaS with the latest ACR in effect. ACR versions lag behind releases, so verification against your instance version and report date is required.
One missing diagnostic detail that changes the recommendation: which Jira Align version and ACR publication date you are referencing. If you are on an on-premise version or a release newer than the published ACR, the conformance status may differ.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.