-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
9.12.2
-
- 1.3.2
- Level-A
- WCAG21
- a11y-triaged
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-high-priority
- ax-jira-dc-vpat
- ax-jira-dc-vpat-Backlog
- ax-jiradc-backlog
- ax-jiradc-vpat-2025
- ax-jiradc-vpat-2025-backlog
- ax-jiradc-vpat-2025-reused
- ax-jiradc-vpat2024
- ax-jiradc-vpat2024-backlog
- ax-jiradc-vpat2024-pg09
- ax-qa
- ax-shipped-pre2024
-
9.12
-
Severity 3 - Minor
-
Issue Summary
The Combo box options present in the "Operation" modal dialog does not have an appropriate reading order.
Steps to Reproduce
- Open the "Backlog" page.
- Navigate to any "issue" present in the backlog and select it.
- Navigate to the "More actions" button and press the "." key.
- Observe that the "Operation" modal dialog will appear.
- Navigate to the mentioned combo box with a screen reader and activate it.
- Arrow down to the options from the combo box.
- Note that the content associated with it is available at the end of page.
Screenshot
Actual Results
The list-box options such as "In progress“, "To do", and so on, are present in the "Operations" modal dialog, available at the end of the page for screen reader users. This is because this content is not coded directly after the interactive element in the DOM. It is instead coded at the end of the page.
This inappropriate reading order might disorient the users of screen readers. That the content is available at the end might confuse or mislead them.
Expected Results
Content must have an appropriate reading order. Assistive technologies navigate content using the order in which elements appear in the DOM. Hence, make sure that the content is programmatically ordered in such a way that it provides an appropriate reading order to the users of assistive technologies.
Make sure that the content is announced when the "List-box" of the combo box receives keyboard focus and is coded directly after it in the DOM. This will create an appropriate reading order for the users of assistive technologies.
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available
Environment
MacBook Pro (16-inch, 2021)
macOs Sonoma 14.3
Chrome - Version 120.0.6099.109 (Official Build) (arm64)
Firefox- Version 92.0 (64-bit)
Safari- Version 17.3 (19617.2.4.11.8)
JAWS- Version 2023
NVDA- Version 2021.2
Voiceover - Version Latest
- is resolved by
-
A11Y-109 You do not have permission to view this issue
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|