Kanban board : Issue key not identified by the screen reader user

Issue Summary

 In the Kanban board, the screen reader reads out the whole issue content and the user is not able to differentiate between the issue key and the issue.

Tested URL

https://instenv-18749-knjm.instenv.internal.atlassian.com/secure/RapidBoard.jspa?rapidView=4&projectKey=SKP&selectedIssue=SKP-3 

Steps to Reproduce

1. Launch the URL
2. Keeping the screen reader on, navigate to the main content area where the issues are present in the swimlane.
3. Try to operate/navigate with the screen reader with normal Tab and Shift-Tab and also in the read mode.

Screenshot

Screen recording

Screen Recording 2022-05-05 at 1.46.05 PM.mov

Actual Results

In the Kanban board swimlane, when the screen reader user navigates in between the issues, they find difficulty in differentiating the issue and its issue key. The screen reader reads out the whole content and when in read mode issue key is announced but it is difficult to understand the context of it. 

Expected Results

The issue key should be announced separately when the user's focus is available on the issue. 
The following suggestions could be implemented to make the issue more accessible and understandable to the assistive technology user.

• Add aria-label or aria-labelledby to the Issue key such as aria-label="Issue key SS-7" to indicate the element is an issue key in the issue block.
• The issue key could receive focus separately when the user tabs in the swimlane.

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available