Issue Summary

      On the "Backlog" page, the text "Scrum", and "SCRUM-14" (that appears on activating the "Issue Key: SCRUM-10", "Issue Key: SCRUM-17 Issue with status done", "Issue Key: SCRUM-14", and so on, links") inappropriately use description list semantics.

      Steps to Reproduce

      1. Navigate onto the above mentioned page.
      2. Navigate onto the "Issue Key: SCRUM-10", "Issue Key: SCRUM-17 Issue with status done", "Issue Key: SCRUM-14", and so on, links and activate any of them.
      3. Navigate onto the mentioned instances and inspect their code.
      4. Observe that these elements inappropriately use description list semantics.
      5. Observe that these elements do not share key and value relationship.

      Actual Results

      The text "Scrum", and "SCRUM-14" use description list semantics, such as <dl>, <dt>, and <dd> elements. However, these elements do not have key and value relationship. As a result, users of screen reader will not be able to understand the page's content structure.

      Expected Result

      Use CSS to style the content. Do not use description list semantics tags, such as <dl>, <dt>, and <dd>, unless the content has a key and value relationship. Use neutral tags that do not have any structural meaning, such as <div>, <span>, and <p> tags.

      Screenshot

      Code snippet

      <span>Scrum</span>
      <h2>Scrum-14</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 Monterey Version 12.4
      Chrome - Version 103.0.5060.134 (Official Build) (arm64)
      Firefox- Version 93.0 (32-bit)
      Safari- Version 15.5 (17613.2.7.1.8)
      JAWS- Version 2022
      NVDA- Version 2020.3
      Voiceover - Version Latest

          Form Name

            [JSWSERVER-26234] Backlog : Elements use description list semantics inappropriately

              Unassigned Unassigned
              773dd3a38dd5 Cynthia Singh
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated: