Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-26214

Burndown Chart: Inaccurate reading order

XMLWordPrintable

      Issue Summary

      On the Burndown Chart page, the content associated with the "Chart: Sample Sprint 2" and "Estimate type: Story Points" expandable buttons in the main content area do not have an appropriate reading order.

      Steps to Reproduce

      1. Open the "Burndown Chart" page.
      2. Navigate to the main content.
      3. Using screen reader, navigate to the mentioned buttons and activate any of these.
      4. Notice that the content associated with the mentioned buttons is getting update at the end of the page.

      Scree Recording

      SSPD board - Agile Board - InstEnv Jira - Google Chrome 2024-02-12 17-22-10.mp4

      Actual Results

      When the "Chart: Sample Sprint 2" and "Estimate type: Story Points" buttons are expanded, the expanded content of these buttons is available at the end of the page for screen reader users. This is because this content is not coded directly after the buttons 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 content that gets available on expanding the button is coded directly after the expandable buttons in the DOM. This will create an appropriate reading order for the users of assistive technologies. For instance, this will enable them to arrow down to the expanded content when the buttons are expanded.

      Workaround

      Required, if there is no workaround please state:
      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.3.1
      Chrome - Version 101.0.4606.81 (Official Build) (64-bit)
      Firefox- Version 93.0 (32-bit)
      Safari- Version 15.3 (17612.4.9.1.5)
      JAWS- Version 2022
      NVDA- Version 2020.3
      Voiceover - Version Latest

              4e432536cf93 Karol Skwierawski
              4cbd728b4726 Rinku Kumar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: