Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-73413

Search Issue : Filter checkbox elements are not accessible to screen reader users

XMLWordPrintable

      Issue Summary

      On Issue search page, the checkbox elements such "Basic s/d (BS)", "Kanban project(kp)", etc present under the "Project" filter popup are not announced as checkboxes by the screen reader. Also the state checked/unchecked is also not announced by screen reader.

      Note: Similar issue is observed for the all checkbox elements present under following filter popups.

      • Type
      • Status
      • Assignee
      • More

      Steps to Reproduce

      1. Navigate to the Jira system dashboard page.
      2. Navigate to "Issues" button in header section & activate it.
      3. Activate "Search for issues" link from the menu.
      4. Navigate to Filter buttons such as "project", "Type", "Status", etc.
      5. Navigate to the checkbox elements inside filter popup.

      Actual Results

      While navigating with screen reader, when user navigate inside "Project" filter popup and use up/down arrow keys, the checkbox elements such as "Basic s/d (BS)", "Kanban project(kp)", etc are announced as text element. Also the state of the checkbox i.e checked/unchecked is not announced by screen reader software.

      Additionally the the checkbox elements are wrapped inside listbox & option elements incorrectly. Also when the user activates any checkbox element the focus goes to the background content inappropriately.

      Expected Results

      The screen reader should announce the checkbox elements correctly & should also announce the state checked/unchecked. Apply following fixes.

      • Remove the role="listbox" from the <div> element.
      • Remove the role="option" from the <li> element.
      • Remove the tabindex="-1" attributes from the <input> checkbox elements.

      Screenshot

      Screen Recording

      Screen Recording 2022-03-24 at 5.53.49 PM.mov

      Workaround

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

      Bug Ref: 723898

              a955dc6cda19 Oleksandr Stoliar
              12b69dcabe29 Matthew Brennan
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: