Issue View: H1 element misused as a container element

XMLWordPrintable

    • Severity 3 - Minor
    • Accessibility

      Issue Summary

      The <h1> element is being misused as a container for controls such as "SlAs", "Details", "More fields", and similar UI elements.

      Steps to Reproduce

      1. Open the JSM Cloud instance.
      2. Navigate to the header section, activate the "Projects" control, and open any project.
      3. Navigate to "Queues" in the side navigation, activate it, and open any issue.
      4. Navigate to the mentioned instances in the main content area and inspect the code.
      5. Observe that the <h1> element is being misused as a container.

      Screenshot

       

      Screen Recording

       

      Actual Results

      When screen reader users navigate the "Issue View" page using the "Down Arrow" key, they encounter an issue where expanding the "SLAs", "Details", "More fields", and similar controls causes the entire section to be announced as a heading.

      This issue occurs because the <h1> element is being used as a parent container for each <details> element within these controls.

      The incorrect nesting results in inappropriate announcements for screen reader users, making navigation confusing.

      As a result, this creates a poor experience for screen reader users.

      Expected Results

      Ensure that the misuse of semantic elements is avoided.

      In this case, since the functionality is implemented using the native HTML <details> and <summary> elements, it's important to ensure the correct markup is used so that the content is announced appropriately by all screen readers.

      Apply the following changes:

      • Remove the <h1> element from the container of the mentioned instances.
      • Use the <div> element as the parent container for each <details> element.
      • Use CSS to maintain the visual presentation of the page.

      Code Snippet:

      <div>

      <details>
        <summary>
      SLAs
        </summary>
      .....
      </details>

      </div>

      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.5
      Operations - Windows11
      Chrome - Version 135.0.7049.42 (Official Build) (64-bit)
      Safari- Version 18.4
      Firefox- Version 135.0 (64-bit)
      JAWS- Version 2023
      NVDA- Version 2024.4.2
      VoiceOver - Version Latest

            Assignee:
            Unassigned
            Reporter:
            Chirag Goyal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: