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

Option names present for combobox are not announcing for screen readers

XMLWordPrintable

      Issue Summary

      On the “Create Issue” modal dialog (which appears on activating “Create” button) the options present for the “Epic link” and “Sprint“ custom comboboxes are announced for screen reader users.

      Steps to Reproduce

      1. Navigate to the any “Jira (Server/Data Center)” page.
      2. Navigate to the “Create” button present in the header section and activate it.
      3. Observe a “Create Issue“ modal dialog gets added on the page
      4. Using screen reader, navigate to the mentioned custom combobox and enter a value in the input field.
      5. Observe that suggestions get dynamically added below.
      6. Listen that there is no indication to understand about the suggestions getting added below.

      Actual Results

      Following issues are found with “Epic link” and “Sprint“ custom comboboxes:

      • As soon as users start entering data in the input field, the suggestions get added below. Although the dynamic change is easier to understand for sighted users, it may not be intuitive for screen reader users.
      • The “Showing 100 of 4028 matching epics“, “Suggestions“, “All Epics“ and so on suggestion interactive elements are not operable with a screen reader. This made it difficult for screen reader users to access the suggestions.
      • Screen reader users should be made aware of the update in the suggestions below while entering data in the input field.

      Since these fields are not accessible with use of assistive technology, then screen reader users might not be able to complete this field successfully.

      Screen recording

      Screen Recording 2024-06-06 at 4.39.47 PM.mov

      Expected Results

      To make the mentioned “Epic link” and “Sprint“ custom comboboxes accessible for screen readers.

      Apply the following changes:

      • Modify scripts to ensure that the combobox options are operable with a screen reader.
      • Add a single role="listbox" to the parent <div> tag containing all the options.
      • Provide role="group" and "aria-labelledby" attribute to each <div> tag containing the group of options.
      • Specify "id" attribute with unique value to <h5> tag containing the text "Showing 100 of 4028 matching epics".
      • Reference "id" attribute value of <h5> tag containing the text to "aria-labelledby" attribute.
      • Reference "id" attribute value of the option which receives the keyboard focus to "aria-activedescendant" attribute.

      For more reference you can visit to the following link.

      Workaround

      Workaround for epics dropdown

      On backlog page, navigate to the “show epics panel” button and press enter to open the epic panel. From the popup navigate to the “Actions” button present after the epic in which you want to create new issue, it will open a menu, press tab and navigate to “view epic details” link, it will open that epic page

      On this page, navigate to the “Create issue in epic” link and press enter, it will open a modal dialog “Create issue in epic : <epic name>”, fill all the details, you don’t need to select epic it will be selected by default.

       

      Workaround for “sprint” dropdown.

      On the backlog page, if you have multiple sprints apart from current active sprint, at the end of each sprint section there is a button “create issue”, you can navigate to that button and press enter to create issue in that particular sprint directly.

      If you want to create new issue in current sprint, it’s little exhausting, follow the below steps

      • create the new issue in any other sprint
      • navigate to that issue
      • turn off the jaws virtual cursor
      • press space to pick up
      • press up arrow key to move the issue within the sprints
      • keep pressing the up arrow keys. until you hear “you have reached the bottom of the <your active sprint name>”
      • now press space again to drop the issue in current sprint.

              b5681d69ff53 Maciej Szarecki
              4b5b126a48d0 ssuryavanshi (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: