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

Create issue : Inappropriate heading structure

XMLWordPrintable

      Issue Summary

      The heading structure on the modal dailog is found to be inappropriate.

      Steps to Reproduce

      1. Open "Jira - Home" page.
      2. Navigate and activate "Create" button in header section.
      3. Navigate and activate "Configure Fields > Where is my field?" in the modal dailog.
      4. Navigate through the page using the down arrow (JAWS/NVDA) and VO+Left arrow/Right arrow (VoiceOver).
      5. Observe that the mentioned text has incorrect heading mark-up as per visual hierarchy.

      Screenshot

      Actual Results

      The heading structure is found to be inappropriate on the page. The texts such as "Where is my field?" is coded as <h2> instead of H1. which does not matches the visual hierarchy on the page. As a result, screen reader users found it difficult to understand the page's content structure.

      Expected Results

      The heading levels should be announced as per the visual hierarchy by the screen reader to understand the page structure for their users. Use heading levels as per specification such as <h1> should be followed by <h2>, <h3>, and so on. In this scenario provide <H1> element to the "Where is my field?" text.

      Code snippet

      <h1 id="jira-dialog2__heading" ...>Where is my field?</h1>

      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 Sonoma 14.7
      Chrome - Version 131.0.6778.265 (Official Build) (arm64)
      Firefox- Version 134.0 (64-bit) 
      Safari- Version 18.2 (19620.1.16.111.6, 19620)
      JAWS- Version 2023
      NVDA- Version 2021.2 
      Voiceover - Version Latest

              spanchenko@atlassian.com Serhii Panchenko
              fa4c360ae0ba Saiman Khan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: