-
Bug
-
Resolution: Fixed
-
Medium
-
8.20.30, 9.4.17, 9.12.2
-
- 4.1.2
- Level-A
- WCAG2.1
- ax-at-JAWS
- ax-at-NVDA
- ax-at-user
- ax-bug
- ax-critical-priority
- ax-desktop
- ax-dev-ready
- ax-jiradc-arj
- ax-jiradc-arj-vpat2024
- ax-jiradc-vpat
- ax-jiradc-vpat-accessibilityassessmentreleases
- ax-jiradc-vpat-accessibilityassessmentroadmaps
- ax-jiradc-vpat-pg05
- ax-qa
- ax-qa-fixed
- ax-qa-verified
-
8.2
-
Severity 3 - Minor
-
Issue Summary
On the Accessibility Assessment - Releases page, the instructions to drag and drop the “JIRADC”, “JIRAD 1”, “test2”, etc. are not communicated to the users of screen reader in windows.
Steps to Reproduce
- Open the "Accessibility Assessment - Releases" page.
- Navigate to the main content.
- Using screen reader, navigate to the mentioned elements.
- Observe that the announcement for drag and drop is not beeing for screen reader users
Screen Recording
test - Advanced Roadmaps - InstEnv Jira - Google Chrome 2024-02-05 16-01-23.mp4![]()
Actual Results
The “Draggable element. Ensure your screen reader is not in brows mode…” instructions to drag and drop the elements are not communicated to the users of a screen reader. When screen reader users navigate to the draggable element, the instructions as to how to drag and drop a particular element is not announced. As a result, screen reader users may not be able to comprehend that the elements are draggable in nature and may not access the functionality associated with the elements.
Expected Results
Make sure that the instructions related to drag and drop are communicated across all the platforms. In this scenario, make sure that when screen reader users navigate to the draggable elements, the instructions such as “draggable element. Ensure your screen reader is not in brows mode…” is communicated along with the accessible name and role of the elements. The drag and drop items are coded in src/packages/servicedesk/portal-request-groups/src/ui/portal-group/index.tsx and GroupList is the relevant item.
Workaround
Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available
Environment
Chrome - Version 101.0.4606.81 (Official Build) (64-bit)
Firefox- Version 93.0 (32-bit)
JAWS- Version 2022
NVDA- Version 2020.3
- mentioned in
-
Page Loading...