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

View issue in queue view & comments: Non-modal dialog is not programmatically defined

      Issue Summary

      The non-modal dialog that becomes available when user activates the "View voters" link.

      Steps to Reproduce

      1. Navigate to the "Issue" dropdown in the header.
      2. Select any issue from the dropdown.
      3. For example, select the "JSM-1 What am i looking at?" issue.
      4. Observe that "View issue in queue view & comments" page has been appeared on the screen.
      5. Navigate to the above mentioned link and activate it.
      6. Verify that the appearance of the non-modal dialog is not announcing.

      Screen Recording

      Screen Recording 2023-09-15 at 4.32.15 PM.mov

      Actual Results

      Following issue are found for the "View voters" non-modal dialog

      • "View voters" non-modal dialog is not specified with a programmatic role and accessible name.
      • This non-modal dialog content is placed at the end of the page. Which causes user to navigate the additional content unnecessarily.

      This resulted in difficulty for screen reader users to understand the presence of a dialog and traverse additional content.

      Expected Results

      Apply the following changes: * Add role="dialog", aria-modal="false" and "aria-labelledby" attribute to the <div> tag containing the dialog content.

      • Specify aria-label attribute containing the short description.
      • Change the order of the content in DOM, place the content right after the triggering element i.e. "View voters" link.

       
      For information on creating accessible modal dialog refer https://www.w3.org/WAI/ARIA/apg/example-index/dialog-modal/dialog.html

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Environment

      MacBook Pro (16-inch, 2019)
      macOS Ventura Version 13.3.1
      Chrome - Version 114.0.5735.198 (Official Build) (x86_64)
      Firefox- Version 112.0.1 (64-bit)
      Safari- Version 16.4 (18615.1.26.11.23)
      JAWS- Version 2022
      NVDA- Version 2020.3
      Voiceover - Version Latest

       

            [JSDSERVER-14333] View issue in queue view & comments: Non-modal dialog is not programmatically defined

            Martin Ma made changes -
            Resolution New: Tracked Elsewhere [ 15 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Martin Ma made changes -
            Assignee Original: Amisha - [ ad6a80463119 ]
            Martin Ma made changes -
            Link New: This issue is caused by JRASERVER-76568 [ JRASERVER-76568 ]
            Martin Ma made changes -
            Link New: This issue was cloned as JSDSERVER-14846 [ JSDSERVER-14846 ]
            Amisha - made changes -
            Assignee New: Amisha - [ ad6a80463119 ]
            Amisha - made changes -
            Status Original: Gathering Impact [ 12072 ] New: In Progress [ 3 ]
            Alex Cooksey (Inactive) made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Nayan Kamble (Inactive) made changes -
            Labels Original: 4.1.2 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jsm-dc-vpat ax-jsm-dc-vpat-Viewissueinqueueview&comments ax-qa New: 4.1.2 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jsm-dc-vpat ax-jsm-dc-vpat-Viewissueinqueueview&comments ax-jsm-dc-vpat-pg10 ax-qa
            Nayan Kamble (Inactive) made changes -
            Labels Original: 4.1.2 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jsm-dc-vpat ax-jsm-dc-vpat-Viewissueinqueueview&comments ax-jsm-dc-vpat-pg04 ax-qa New: 4.1.2 Level-A WCAG21 ax-at-user ax-bug ax-high-priority ax-jsm-dc-vpat ax-jsm-dc-vpat-Viewissueinqueueview&comments ax-qa
            Varsha Bansode (Inactive) made changes -
            Description Original: h3. Issue Summary

            The non-modal dialog that becomes available when user activates the "View voters" link.
            h3. Steps to Reproduce
             # Navigate to the "Issue" dropdown in the header.
             # Select any issue from the dropdown.
             # For example, select the "JSM-1 What am i looking at?" issue.
             # Observe that "View issue in queue view & comments" page has been appeared on the screen.
             # Navigate to the above mentioned link and activate it.
             # Verify that the appearance of the non-modal dialog is not announcing.

            h3. Actual Results

            "BBBBB" non-modal dialog is not specified with a programmatic role and accessible name. This resulted in difficulty for screen reader users to understand the presence of a dialog.
            h3. Expected Results

            akclk
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available
            New: h3. Issue Summary

            The non-modal dialog that becomes available when user activates the "View voters" link.
            h3. Steps to Reproduce
             # Navigate to the "Issue" dropdown in the header.
             # Select any issue from the dropdown.
             # For example, select the "JSM-1 What am i looking at?" issue.
             # Observe that "View issue in queue view & comments" page has been appeared on the screen.
             # Navigate to the above mentioned link and activate it.
             # Verify that the appearance of the non-modal dialog is not announcing.

            h3. Screen Recording

            [^Screen Recording 2023-09-15 at 4.32.15 PM.mov]
            h3. Actual Results

            Following issue are found for the "View voters" non-modal dialog
             * "View voters" non-modal dialog is not specified with a programmatic role and accessible name.
             * This non-modal dialog content is placed at the end of the page. Which causes user to navigate the additional content unnecessarily.

            This resulted in difficulty for screen reader users to understand the presence of a dialog and traverse additional content.
            h3. Expected Results
            Apply the following changes: * Add role="dialog", aria-modal="false" and "aria-labelledby" attribute to the <div> tag containing the dialog content.
             * Specify aria-label attribute containing the short description.
             * Change the order of the content in DOM, place the content right after the triggering element i.e. "View voters" link.

             
            For information on creating accessible modal dialog refer https://www.w3.org/WAI/ARIA/apg/example-index/dialog-modal/dialog.html
            h3. Workaround

            Currently there is no known workaround for this behavior. A workaround will be added here when available
            h3. Environment

            MacBook Pro (16-inch, 2019)
            macOS Ventura Version 13.3.1
            Chrome - Version 114.0.5735.198 (Official Build) (x86_64)
            Firefox- Version 112.0.1 (64-bit)
            Safari- Version 16.4 (18615.1.26.11.23)
            JAWS- Version 2022
            NVDA- Version 2020.3
            Voiceover - Version Latest

             

              Unassigned Unassigned
              c3f9a46dc7c4 Varsha Bansode (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: