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

      1. Navigate to the "Plans" in header section and activate any plan.
      2. Observe the "Plan" page appears.
      3. Navigate to the "Review Changes" button and activate it.
      4. Observe the "Review Changes" modal appears.
      5. Navigate to the mentioned text and inspect the code.
      6. 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

            [JSWSERVER-25569] Review Changes In Jira: Inappropriate heading structure

            There are no comments yet on this issue.

              Unassigned Unassigned
              1266eee53fd7 Shivani More (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated: