Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-15958

View issue in queue view & comments: Inaccurate reading order

XMLWordPrintable

      Issue Summary

      The expanded content containing "Viewable by All Users" and "Administrators" in the main content area do not have an appropriate reading order.

      Steps to Reproduce

      1. Navigate to the header section. Using "Tab" key, navigate to the "Issue" dropdown.
      2. Navigate to any of the issue as "JSM-1 What am i looking at?" and activate it.
      3. Observe that "View issue in queue view & comments" page has been appeared on the screen.
      4. Using a keyboard 'Tab' key, navigate to the "Click to add comment" text field.
      5. Navigate and activate "Viewable by All Users" button using VO+left/right arrow keys (up/down in Windows).
      6. Use Space/Enter to activate it.
      7. Navigate and inspect the expanded content.
      8. Note that the associated content is available at the end of the page.

      Screenshot

      Screen Recording

      Screen Recording 2024-12-23 at 11.29.55 AM.mov

      Actual Results

      When users activate the "Viewable by All Users" the expanded content such as "Viewable by All Users" and "Administrators" are available at the end of the page for screen reader users. This is because this content is not coded directly after the button in the DOM. It is instead coded at the end of the page.

      This inappropriate reading order might disorient the users of screen readers. That the content is available at the end might confuse or mislead them.

      Expected Results

      Content must have an appropriate reading order. Assistive technologies navigate content using the order in which elements appear in the DOM. Hence, make sure that the content is programmatically ordered in such a way that it provides an appropriate reading order to the users of assistive technologies.

      Make sure that the available expanded content is coded directly after the triggering element in the DOM. This will create an appropriate reading order for the users of assistive technologies. For instance, this will enable them to navigate onto the associated expanded content when the expanded content is available.

      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.86 (Official Build) (arm64)
      Firefox- Version 92.0 (64-bit) 
      Safari- Version 17.0 (19616.1.27.211.1)
      JAWS- Version 2023
      NVDA- Version 2021.2 
      Voiceover - Version Latest

       

              Unassigned Unassigned
              88a173d72595 Sojal Shende
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: