JSM Ticket Table: New window links were not identified

XMLWordPrintable

    • Severity 3 - Minor
    • Accessibility

      Issue Summary

      The tickets links such as "ACT-4", "ACT-3", "ACT-2", and so on that open in a new tab are not identified as new window links.

      Steps to Reproduce

      1. Open a Confluence page containing the JSM ticket table.
      2. Using a screen reader, navigate to the "ACT-4", "ACT-3", and so on links in the "Key" column.
      3. Observe there is no indication of links opening a new window.

      Screenshot

      Screen Recording

      https://www.loom.com/share/cba52fc714b4457987a3e2850f77bf32

      Actual Results

      The ticket links such as "ACT-4", "ACT-3", and so on, open in a new browser tab on activation. The users are not informed about links opening a new window in advance.

      This might cause difficulties for mobility impaired, low vision, screen reader and cognitive users.

      Expected Results

      Users should be informed in advance about the functionality of the link.

      Inform users in advance about links opening in a new window. This can be done by providing an image icon depicting a new window beside the link text. The image icon must be inside the <a> element and specify alt as "Opens in a new tab".

      Alternatively, provide visually hidden text such as "Opens in a new tab" within the <a> element beside the link text.

      Code Snippet 1:

      <a href="https://...browse/ACT-4" target="_blank">
        ACT-4
        <img src="new-window-icon.svg" alt="Opens in a new tab">
      </a> 

      Code Snippet 2:

      <a href="https://...browse/ACT-4" target="_blank">
      ACT-4
      <span class="visually-hidden">(opens in new tab)</span> 
      </a> 

      Note: This code example is intended only as a general illustration of how to address the violation and should not be considered a complete or production-ready solution. If you have any questions, please attach this ticket to a #help-accessibility request.

      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 26.5.2
      Windows - 11 pro
      Chrome - Version 150.0.7871.187 (Official Build)
      Microsoft Edge - Version 150.0.4078.99 (Official Build) 
      JAWS - Version 2026
      NVDA - Version 2024.4.2.35031
      Voiceover - Version Latest

              Assignee:
              Unassigned
              Reporter:
              Anusooya .
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: