-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 8.13.0
-
Component/s: Accessibility
-
- 2.4.3
- Level-A
- WCAG21
- ax-bitbucket-dc-vpat-2025
- ax-bitbucket-dc-vpat-2025-reused
- ax-bitbucket-dc-vpat-2025-viewpullrequest
- ax-bitbucketdc-vpat
- ax-bitbucketdc-vpat-pg05
- ax-bitbucketdc-vpat-viewpullrequest
- ax-bitbucketdc-vpat2024
- ax-bitbucketdc-vpat2024-reuse
- ax-bitbucketdc-vpat2024-viewpullrequest
- ax-bug
- ax-high-priority
- ax-kb-user
- ax-qa
- ewt-rtb-service-operations-and-tech-entropy
-
Severity 3 - Minor
Issue Summary
The focus moves inappropriately to the triggering element "More Actions" instead of moving to the added reaction on the comment or task
Steps to Reproduce
- Navigate to the mentioned page.
- Navigate to the "Add reaction" button and activate it.
- Using the screen reader, navigate to the different reaction buttons and activate one of them.
- Observe that the focus moves to the "More Actions" instead of moving to the added reaction.
Screen Recording
Screen Recording 2023-10-05 at 4.33.23 PM.mov![]()
Actual Results
The focus moves inappropriately to the triggering element "More Actions" instead of moving to the added reaction on the comment or task.
As a result, keyboard-only and screen reader users will have to navigate the screen content again before accessing the content which is updated below.
Expected Results
Ensure that the keyboard focus moves to the added reaction on the comment or task which can be achieved via the JavaScript focus() method.
Workaround
Currently, there is no known workaround for this behaviour.
Environment
MacBook Pro (16-inch, 2019)
macOS 13.4.1 (c) (22F770820d)
Chrome - Version 115.0.5790.170 (Official Build) (x86_64)
Firefox- Version 114.0 (64-bit)
Safari- Version 16.5.2 (18615.2.9.11.10)
JAWS- Version 2023.2306.28
NVDA- Version 2022.2.2
Voiceover - Version Latest
- mentioned in
-
Page Loading...