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

Object Overview Modal with default force mode graph : Graphical section Inaccessible by keyboard users

      Issue Summary

      The Object image elements are not accessible by keyboard alone in the Force graph for the Object overview modal.

      Steps to Reproduce

      1. Launch the URL
      2. In the main content area, click on the object link, just beside the "Affected Server:" area
      3. Then the "Object Overview" modal will display.
      4. Click on the "Show graph" icon button.
      5. Click on the "Force" button. Then the graph will display in the Force view.
      6. Try to interact with the graphical objects in the modal with a keyboard such as "oracledb-11g-prod".

      Screenshot

      Screen Recording

       Screen Recording 2022-05-20 at 6.39.15 PM.mov

      Actual Results

      Keyboard support is missing for the content that is available in the force graph section in the Object overview modal.
      For example, content such as "oracledb-11g-prod", "Payroll service", etc. is accessible with a mouse and the user can move the images in the area, but a keyboard user is not able to use this functionality. This made it difficult for keyboard-only and screen reader users to access the functionality associated with it.

      Expected Results

      Apply the following changes:
      • Modify the scripts to ensure that the content is available on focus as well as on hover. onfocus and onblur keyboard handlers can be used to ensure that the images are available for keyboard-only users. 
      • Specify key listeners to make sure that the content becomes visible when users press the Tab and Up/Down Arrow keys.
      • Add a hidden instruction for the benefit of screen reader users to inform them about the presence of the content. Add an instruction, such as "Press the tab key to access the content”. This instruction should be placed before entering the interactive objects area.

       

      Workaround

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

       

      Bug Ref: 745330

      Bulldog Ref: JSMDC-12574

        1. Screenshot 2022-05-20 at 7.12.50 PM.png
          1.43 MB
          Akhilesh Paradhi
        2. Screen Recording 2022-05-20 at 6.39.15 PM.mov
          19.14 MB
          Akhilesh Paradhi
        3. Object overview force modal.jpg
          576 kB
          Akhilesh Paradhi
        4. Object overview force modal.mp4
          2.61 MB
          Akhilesh Paradhi

            [JSDSERVER-11624] Object Overview Modal with default force mode graph : Graphical section Inaccessible by keyboard users

            Oleksandr Stoliar made changes -
            Resolution Original: Fixed [ 1 ] New: Cannot Reproduce [ 5 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Matthew Brennan made changes -
            Labels Original: 2.1.1 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-macos-safari ax-platform-dc ax-qa ax-qa-prioritised ax-qa-verified ax-vpat-critical ax-windows-chrome ax-windows-firefox New: 2.1.1 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-critical ax-critical-priority ax-dev-done ax-high-priority ax-jsm ax-macos-safari ax-platform-dc ax-qa ax-qa-prioritised ax-qa-verified ax-vpat-critical ax-windows-chrome ax-windows-firefox
            Matthew Brennan made changes -
            Labels Original: 2.1.1 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-macos-safari ax-platform-dc ax-qa-prioritised ax-qa-verified ax-vpat-critical ax-windows-chrome ax-windows-firefox New: 2.1.1 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-macos-safari ax-platform-dc ax-qa ax-qa-prioritised ax-qa-verified ax-vpat-critical ax-windows-chrome ax-windows-firefox
            Akhilesh Paradhi (Inactive) made changes -
            Description Original: h3. Issue Summary

            The Object image elements are not accessible by keyboard alone in the Force graph for the Object overview modal.
            h3. Tested URL

            [https://instenv-19536-ipiz.instenv.internal.atlassian.com/browse/IOP-9
            h3. Steps to Reproduce
             # Launch the URL
             # In the main content area, click on the object link, just beside the "Affected Server:" area
             # Then the "Object Overview" modal will display.
             # Click on the "Show graph" icon button.
             # Click on the "Force" button. Then the graph will display in the Force view.
             # Try to interact with the graphical objects in the modal with a keyboard such as "oracledb-11g-prod".

            h3. Screenshot

            !Screenshot 2022-05-20 at 7.12.50 PM.png|width=379,height=209!
            h3. Screen Recording
            h3.  [^Screen Recording 2022-05-20 at 6.39.15 PM.mov]
            h3. Actual Results

            Keyboard support is missing for the content that is available in the force graph section in the Object overview modal.
            For example, content such as "oracledb-11g-prod", "Payroll service", etc. is accessible with a mouse and the user can move the images in the area, but a keyboard user is not able to use this functionality. This made it difficult for keyboard-only and screen reader users to access the functionality associated with it.
            h3. Expected Results

            Apply the following changes:
            • Modify the scripts to ensure that the content is available on focus as well as on hover. onfocus and onblur keyboard handlers can be used to ensure that the images are available for keyboard-only users. 
            • Specify key listeners to make sure that the content becomes visible when users press the Tab and Up/Down Arrow keys.
            • Add a hidden instruction for the benefit of screen reader users to inform them about the presence of the content. Add an instruction, such as "Press the tab key to access the content”. This instruction should be placed before entering the interactive objects area.

             
            h3. Workaround

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

             

            Bug Ref: 745330

            Bulldog Ref: JSMDC-12574
            New: h3. Issue Summary

            The Object image elements are not accessible by keyboard alone in the Force graph for the Object overview modal.
            h3. Steps to Reproduce
             # Launch the URL
             # In the main content area, click on the object link, just beside the "Affected Server:" area
             # Then the "Object Overview" modal will display.
             # Click on the "Show graph" icon button.
             # Click on the "Force" button. Then the graph will display in the Force view.
             # Try to interact with the graphical objects in the modal with a keyboard such as "oracledb-11g-prod".

            h3. Screenshot

            !Screenshot 2022-05-20 at 7.12.50 PM.png|width=379,height=209!
            h3. Screen Recording
            h3.  [^Screen Recording 2022-05-20 at 6.39.15 PM.mov]
            h3. Actual Results

            Keyboard support is missing for the content that is available in the force graph section in the Object overview modal.
            For example, content such as "oracledb-11g-prod", "Payroll service", etc. is accessible with a mouse and the user can move the images in the area, but a keyboard user is not able to use this functionality. This made it difficult for keyboard-only and screen reader users to access the functionality associated with it.
            h3. Expected Results

            Apply the following changes:
            • Modify the scripts to ensure that the content is available on focus as well as on hover. onfocus and onblur keyboard handlers can be used to ensure that the images are available for keyboard-only users. 
            • Specify key listeners to make sure that the content becomes visible when users press the Tab and Up/Down Arrow keys.
            • Add a hidden instruction for the benefit of screen reader users to inform them about the presence of the content. Add an instruction, such as "Press the tab key to access the content”. This instruction should be placed before entering the interactive objects area.

             
            h3. Workaround

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

             

            Bug Ref: 745330

            Bulldog Ref: JSMDC-12574
            Akhilesh Paradhi (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Akhilesh Paradhi (Inactive) made changes -
            Labels Original: 2.1.1 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-dev-ready ax-high-priority ax-jsm ax-macos-safari ax-platform-dc ax-qa-prioritised ax-vpat-critical ax-windows-chrome ax-windows-firefox New: 2.1.1 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-high-priority ax-jsm ax-macos-safari ax-platform-dc ax-qa-prioritised ax-qa-verified ax-vpat-critical ax-windows-chrome ax-windows-firefox
            Akhilesh Paradhi (Inactive) made changes -
            Attachment New: Object overview force modal.mp4 [ 425074 ]
            Akhilesh Paradhi (Inactive) made changes -
            Attachment New: Object overview force modal.jpg [ 425073 ]
            Martin Ma made changes -
            Labels Original: 2.1.1 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-ready ax-high-priority ax-jsm ax-macos-safari ax-platform-dc ax-qa-prioritised ax-vpat-critical ax-windows-chrome ax-windows-firefox New: 2.1.1 Accessibility WCAG21 ax-at-NVDA ax-bug ax-bulldog-bl ax-dev-done ax-dev-ready ax-high-priority ax-jsm ax-macos-safari ax-platform-dc ax-qa-prioritised ax-vpat-critical ax-windows-chrome ax-windows-firefox
            Akhilesh Paradhi (Inactive) made changes -
            Description Original: h3. Issue Summary

            The Object image elements are not accessible by keyboard alone in the Force graph for the Object overview modal.
            h3. Tested URL

            [https://instenv-5971-nizh.instenv.atl-test.space/projects/JSM/queues/custom/31/JSM-111]
            h3. Steps to Reproduce
             # Launch the URL
             # In the main content area, click on the object link, just beside the "Affected Server:" area
             # Then the "Object Overview" modal will display.
             # Click on the "Show graph" icon button.
             # Click on the "Force" button. Then the graph will display in the Force view.
             # Try to interact with the graphical objects in the modal with a keyboard such as "oracledb-11g-prod".

            h3. Screenshot

            !Screenshot 2022-05-20 at 7.12.50 PM.png|width=379,height=209!
            h3. Screen Recording
            h3.  [^Screen Recording 2022-05-20 at 6.39.15 PM.mov]
            h3. Actual Results

            Keyboard support is missing for the content that is available in the force graph section in the Object overview modal.
            For example, content such as "oracledb-11g-prod", "Payroll service", etc. is accessible with a mouse and the user can move the images in the area, but a keyboard user is not able to use this functionality. This made it difficult for keyboard-only and screen reader users to access the functionality associated with it.
            h3. Expected Results

            Apply the following changes:
            • Modify the scripts to ensure that the content is available on focus as well as on hover. onfocus and onblur keyboard handlers can be used to ensure that the images are available for keyboard-only users. 
            • Specify key listeners to make sure that the content becomes visible when users press the Tab and Up/Down Arrow keys.
            • Add a hidden instruction for the benefit of screen reader users to inform them about the presence of the content. Add an instruction, such as "Press the tab key to access the content”. This instruction should be placed before entering the interactive objects area.

             
            h3. Workaround

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

             

            Bug Ref: 745330

            Bulldog Ref: JSMDC-12574
            New: h3. Issue Summary

            The Object image elements are not accessible by keyboard alone in the Force graph for the Object overview modal.
            h3. Tested URL

            [https://instenv-19536-ipiz.instenv.internal.atlassian.com/browse/IOP-9
            h3. Steps to Reproduce
             # Launch the URL
             # In the main content area, click on the object link, just beside the "Affected Server:" area
             # Then the "Object Overview" modal will display.
             # Click on the "Show graph" icon button.
             # Click on the "Force" button. Then the graph will display in the Force view.
             # Try to interact with the graphical objects in the modal with a keyboard such as "oracledb-11g-prod".

            h3. Screenshot

            !Screenshot 2022-05-20 at 7.12.50 PM.png|width=379,height=209!
            h3. Screen Recording
            h3.  [^Screen Recording 2022-05-20 at 6.39.15 PM.mov]
            h3. Actual Results

            Keyboard support is missing for the content that is available in the force graph section in the Object overview modal.
            For example, content such as "oracledb-11g-prod", "Payroll service", etc. is accessible with a mouse and the user can move the images in the area, but a keyboard user is not able to use this functionality. This made it difficult for keyboard-only and screen reader users to access the functionality associated with it.
            h3. Expected Results

            Apply the following changes:
            • Modify the scripts to ensure that the content is available on focus as well as on hover. onfocus and onblur keyboard handlers can be used to ensure that the images are available for keyboard-only users. 
            • Specify key listeners to make sure that the content becomes visible when users press the Tab and Up/Down Arrow keys.
            • Add a hidden instruction for the benefit of screen reader users to inform them about the presence of the content. Add an instruction, such as "Press the tab key to access the content”. This instruction should be placed before entering the interactive objects area.

             
            h3. Workaround

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

             

            Bug Ref: 745330

            Bulldog Ref: JSMDC-12574

              Unassigned Unassigned
              12b69dcabe29 Matthew Brennan
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: