-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.20.30, 9.12.2, 9.4.17
-
8.2
-
1
-
Severity 3 - Minor
-
Issue Summary
On the Review Changes In Jira page, the text such as "Review changes" is inappropriately defined as heading level 4.
Steps to Reproduce
- Navigate to the "Plans" in header section and activate any plan.
- Observe the "Plan" page appears.
- Navigate to the "Review Changes" button and activate it.
- Observe the "Review Changes" modal appears.
- Navigate to the mentioned text and inspect the code.
- Observe that the mentioned text has incorrect heading mark-up as per visual hierarchy.
Screenshot
Actual Results
Heading structure on the page is inappropriate, the “Review Changes" heading does not follow the visual structure of the page. It is inappropriately defined as heading level 4 instead of level 2. As a result, screen reader users found it difficult to understand the page’s content structure.
Expected Results
Use heading levels as per specification such as <h1> should be followed by <h2>, <h3> and so on.
Even though this is required at WCAG 2.1 at Level AAA, it is recommended that the discussed issue be addressed as screen reader users rely on headings heavily to understand the page structure. Provide an appropriate heading level for the mentioned heading text, such as <h2>.
Code snippet
<h2 class="_3esxK">Review changes</h2>
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
Environment
MacBook Pro (16-inch, 2021)
macOs Ventura 14.3
Chrome -Version 120.0.6099.71 (Official Build) (arm64)
Firefox- Version 92.0 (64-bit)
Safari- Version 17.1 (19616.2.9.11.7)
JAWS- Version 2023
NVDA- Version 2021.2
Voiceover - Version Latest
- links to
[JSWSERVER-25569] Review Changes In Jira: Inappropriate heading structure
| Labels | Original: 1.3.1 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jiradc-arj ax-jiradc-arj-vpat2024 ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg07 ax-jiradc-vpat-reviewchangesinjira ax-qa | New: 1.3.1 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jiradc-arj ax-jiradc-arj-vpat2024 ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg07 ax-jiradc-vpat-reviewchangesinjira ax-qa ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 963652 ] |
| Priority | Original: High [ 2 ] | New: Medium [ 3 ] |
| Support reference count | New: 1 |
| Introduced in Version | Original: 9.12 | New: 8.2 |
| Affects Version/s | New: 8.20.30 [ 106364 ] | |
| Affects Version/s | New: 9.4.17 [ 106909 ] |
| Labels | Original: 1.3.1 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg07 ax-jiradc-vpat-reviewchangesinjira ax-qa | New: 1.3.1 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jiradc-arj ax-jiradc-arj-vpat2024 ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg07 ax-jiradc-vpat-reviewchangesinjira ax-qa |
| Component/s | Original: Accessibility [ 62491 ] | |
| Component/s | Original: (Advanced Roadmaps) Other [ 73719 ] | |
| Component/s | New: (Advanced Roadmaps) Accessibility [ 74392 ] |
| Labels | Original: 1.3.1 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jiradc-vpat ax-jiradc-vpat-pg07 ax-jiradc-vpat-reviewchangesinjira ax-qa | New: 1.3.1 Level-A WCAG21 a11y-triaged ax-at-user ax-bug ax-dev-ready ax-high-priority ax-jiradc-vpat ax-jiradc-vpat-accessibilityassessmentroadmaps ax-jiradc-vpat-pg07 ax-jiradc-vpat-reviewchangesinjira ax-qa |
| Description |
Original:
h3. Issue Summary
On the Review Changes In Jira page, the text such as "Review changes" is inappropriately defined as heading level 4. h3. Steps to Reproduce # Open the "Review Changes In Jira" page. # Navigate to the mentioned text and inspect the code. # Observe that the mentioned text has incorrect heading mark-up as per visual hierarchy. h3. Screenshot !Screenshot 2024-01-30 at 10.10.46 AM.png|thumbnail! h3. Actual Results Heading structure on the page is inappropriate, the “Review Changes" heading does not follow the visual structure of the page. It is inappropriately defined as heading level 4 instead of level 2. As a result, screen reader users found it difficult to understand the page’s content structure. h3. Expected Results Use heading levels as per specification such as <h1> should be followed by <h2>, <h3> and so on. Even though this is required at WCAG 2.1 at Level AAA, it is recommended that the discussed issue be addressed as screen reader users rely on headings heavily to understand the page structure. Provide an appropriate heading level for the mentioned heading text, such as <h2>. *Code snippet* {code:java} <h2 class="_3esxK">Review changes</h2> {code} 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, 2021) macOs Ventura 14.3 Chrome -Version 120.0.6099.71 (Official Build) (arm64) Firefox- Version 92.0 (64-bit) Safari- Version 17.1 (19616.2.9.11.7) JAWS- Version 2023 NVDA- Version 2021.2 Voiceover - Version Latest |
New:
h3. Issue Summary
On the Review Changes In Jira page, the text such as "Review changes" is inappropriately defined as heading level 4. h3. Steps to Reproduce # Navigate to the "Plans" in header section and activate any plan. # Observe the "Plan" page appears. # Navigate to the "Review Changes" button and activate it. # Observe the "Review Changes" modal appears. # Navigate to the mentioned text and inspect the code. # Observe that the mentioned text has incorrect heading mark-up as per visual hierarchy. h3. Screenshot !Screenshot 2024-01-30 at 10.10.46 AM.png|thumbnail! h3. Actual Results Heading structure on the page is inappropriate, the “Review Changes" heading does not follow the visual structure of the page. It is inappropriately defined as heading level 4 instead of level 2. As a result, screen reader users found it difficult to understand the page’s content structure. h3. Expected Results Use heading levels as per specification such as <h1> should be followed by <h2>, <h3> and so on. Even though this is required at WCAG 2.1 at Level AAA, it is recommended that the discussed issue be addressed as screen reader users rely on headings heavily to understand the page structure. Provide an appropriate heading level for the mentioned heading text, such as <h2>. *Code snippet* {code:java} <h2 class="_3esxK">Review changes</h2> {code} 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, 2021) macOs Ventura 14.3 Chrome -Version 120.0.6099.71 (Official Build) (arm64) Firefox- Version 92.0 (64-bit) Safari- Version 17.1 (19616.2.9.11.7) JAWS- Version 2023 NVDA- Version 2021.2 Voiceover - Version Latest |
| Component/s | New: (Advanced Roadmaps) Other [ 73719 ] |