Backlog - versions and epics panel: Filters are not accessible for keyboard & screen reader users.

Issue Summary

On the backlog page, the filter elements present inside "Versions" panel such as "All issues" , "Issues without versions", "Version 1", etc are not accessible for keyboard & screen reader users.

Panels "Epics" or "Versions" are not accessible with the keyboard if they aren't opened already.

Note: Similar issue is found for filter elements such as "All issues", "Issues without Epics", etc present inside "Epics" panel.

Issue id: 727062

Steps to Reproduce

1. Navigate to Jira dashboard page.
2. Navigate to any project inside Jira.
3. Navigate to the backlog page. 
4. Try to open either Epics or Versions panel with keyboard when they are closed.

Actual Results

Tab stop skips over the Epic/Versions panel.

While navigating with Keyboard inside the "Versions" panels, when user navigate to the filters such as "All issues" , "Issues without versions", "Version 1", etc does not receive Keyboard focus. Also the screen reader users are not aware when the filters are activated.

The filters are coded inside a <span> element with role="button" incorrectly.

Expected Results

Epics / Versions panel should receive a tab stop and allow keyboard users to access them.

Ensure that the filter elements such as "All issues" , "Issues without versions", "Version 1", are accessible with Keyboard as well. Also the screen reader users should be made aware about the current state of the filters.

• Mark the filters inside a native <button> elements instead of <span> elements.
• Provide aria-pressed="true" to the filter button which is activated by default.
• The value of aria-pressed should be toggled  between true/false as per user interactions.
• Provide an off-screen instruction such as "All issues filter applied", "Issues without versions filter applied", etc in an ARIA live region.
• The instructions should be announced by screen reader when user activates any of the filters.

Screen recording

Screen Recording 2022-02-28 at 4.19.50 PM.mov

Screenshot

Workaround

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