-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
9.12.2
-
9.12
-
Severity 3 - Minor
-
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
- Using a screen reader or keyboard, activate the "Boards" menu pop-up link .
- Observe a dialog appears.
- Close the dialog using an Esc key and try to navigate further.
- 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
Form Name |
---|
[JSWSERVER-26217] Burndown Chart: Keyboard focus does not return to the triggering element of modal dialog
Labels | Original: 2.4.3 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-burndownchart ax-jiradc-vpat2024-pg18 ax-kb-user ax-qa ax-shipped-pre2024 | New: 2.4.3 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-high-priority ax-jira-dc-vpat ax-jira-dc-vpat-BurndownChart ax-jiradc-vpat2024 ax-jiradc-vpat2024-burndownchart ax-jiradc-vpat2024-pg18 ax-kb-user ax-qa ax-shipped-pre2024 |
Component/s | Original: Accessibility [ 62490 ] | |
Component/s | New: Reports [ 46796 ] | |
Component/s | New: Accessibility [ 62491 ] | |
Key | Original: JRASERVER-77359 | New: JSWSERVER-26217 |
Affects Version/s | Original: 9.12.2 [ 106456 ] | |
Affects Version/s | New: 9.12.2 [ 106455 ] | |
Project | Original: Jira Data Center [ 10240 ] | New: Jira Software Data Center [ 12200 ] |
Priority | Original: High [ 2 ] | New: Medium [ 3 ] |
Labels | Original: 2.4.3 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-burndownchart ax-jiradc-vpat2024-pg18 ax-kb-user ax-qa | New: 2.4.3 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-burndownchart ax-jiradc-vpat2024-pg18 ax-kb-user ax-qa ax-shipped-pre2024 |
Labels | Original: 2.4.3 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-burndownchart ax-jiradc-vpat2024-pg18 ax-kb-user ax-qa | New: 2.4.3 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-burndownchart ax-jiradc-vpat2024-pg18 ax-kb-user ax-qa |
Status | Original: Needs Triage [ 10030 ] | New: Ready for Development [ 10049 ] |
Priority | Original: Low [ 4 ] | New: High [ 2 ] |
Introduced in Version | New: 9.12 |
Labels | New: 2.4.3 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jiradc-vpat2024 ax-jiradc-vpat2024-burndownchart ax-jiradc-vpat2024-pg18 ax-kb-user ax-qa |
Description |
Original:
h3. 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. h3. Steps to Reproduce # Using a screen reader or keyboard, activate the "Boards" menu pop-up link . # Observe a dialog appears. # Close the dialog using an Esc key and try to navigate further. # Observe that focus moves to the beginning of the page. h3. Screen Recording [^Screen Recording 2024-02-09 at 4.38.37 PM.mov] h3. 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. h3. 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(). h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available h3. 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 |
New:
h3. 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. h3. Steps to Reproduce # Using a screen reader or keyboard, activate the "Boards" menu pop-up link . # Observe a dialog appears. # Close the dialog using an Esc key and try to navigate further. # Observe that focus moves to the beginning of the page. h3. Screen Recording [^Screen Recording 2024-02-09 at 4.38.37 PM.mov] h3. 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. h3. 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(). h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available h3. 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 |