Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-26217

Burndown Chart: Keyboard focus does not return to the triggering element of modal dialog

      Issue Summary

      On the “Burndown Chart | Create an Agile board modal” page, the focus does not return to the element that triggered the content when the new content is closed.

      Steps to Reproduce

      1. Using a screen reader or keyboard, activate the "Boards" menu pop-up link .
      2.  Observe a dialog appears.
      3. Close the dialog using an Esc key and try to navigate further.
      4. Observe that focus moves to the beginning of the page.

      Screen Recording

      Screen Recording 2024-02-09 at 4.38.37 PM.mov

      Actual Results

      On closing the modal dialog, the programmatic focus does not return to the triggering element. Instead the focus is updated to the beginning of the page. This required screen reader users and keyboard-only users to tab pass the content on the page before they can interact with the content after the triggering element.

      Expected Result

      The programmatic focus of users should be set on the triggering element of the dialog as soon as the dialog is closed.
      Set the keyboard focus to the triggering element of the dialog using the JavaScript .focus().

      Workaround

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

      Environment

      MacBook Pro (16-inch, 2019)
      macOs Sonoma 14.3
      Chrome - Version 113.0.5672.63 (Official Build) (x86_64)
      Firefox- Version 92.0 (64-bit)
      Safari- Version 16.4 (18615.1.26.110.1)
      JAWS- Version 2022
      NVDA- Version 2021.2
      Voiceover - Version Latest

            [JSWSERVER-26217] Burndown Chart: Keyboard focus does not return to the triggering element of modal dialog

            No work has yet been logged on this issue.

              Unassigned Unassigned
              83061a15f038 Nayan Kamble
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated: