Details
-
Bug
-
Resolution: Fixed
-
High
-
8.20.1
-
- 2.4.3
- AXSR-15
- Level-A
- WCAG21
- accessibility
- ax-bug
- ax-customer-escalated
- ax-desktop
- ax-dev-ready
- ax-esc-boa
- ax-high-priority
- ax-jira
- ax-jira-dc-vpat
- ax-kb-user
- ax-macos-safari
- ax-platform-dc
- ax-qa
- ax-qa-bl
- ax-qa-prioritised
- ax-windows-chrome
- ax-windows-firefox
- axsr-high-priority
- axsr-march-22
- ozghonnyk
-
8.2
-
Severity 2 - Major
-
Description
Steps to reproduce:
- Navigate to and activate "Projects" link from the banner region and select any project.
- Navigate to and activate the "Issues" link from the left navigation menu.
- Navigate to and activate "Order by Priority" link.
- While the focus is on "Order by Priority" link, activate "Tab" key and observe the focus.
Screenshot:
Actual behaviour:
The focus moves incorrectly to the address bar while navigating with Tab key. When the search input receives keyboard focus, pressing Tab key takes the focus to the address bar instead of next interactive element in order.
This is due to the code of the "order by" popup is placed at the end of the DOM order incorrectly.
Expected result:
Focus should move to next interactive element on tab key activation.
The code of the "order by" popup should be placed right after the code of "order by" <button> in the DOM order.
AXQA Ref:AXQA-119
Attachments
Issue Links
- relates to
-
COM-18 Loading...