Object Overview Modal with default force mode graph : Keyboard focus order is not logical.

XMLWordPrintable

    • Severity 2 - Major

      Issue Summary

      Keyboard focus order is not logical in such a way that it affects the meaning or operability of the content.

      Elements name:
      1. Force and Tree buttons
      2. Elements in the "oracledb-11g-prod" heading section.
      Ex: INITSM-21, oracledb-11g-prod, Solaris 11.3,..... etc.
      3. "Hide", "Info", "Configure", "Unlocked" links, in the left navigation.

      Location of the elements: Elements, in the "Force" view, in the "Object overview" modal.

      Current focus order:
      1. Force and Tree buttons
      2. Elements in the "oracledb-11g-prod" heading section.
      Ex: INITSM-21, oracledb-11g-prod, Solaris 11.3,..... etc.
      3. "Hide", "Info", "Configure", "Unlocked" links, in the left navigation.

      Suggested focus order:
      1. Force and Tree buttons
      3. "Hide", "Info", "Configure", "Unlocked" links, in the left navigation.
      2. Elements in the "oracledb-11g-prod" heading section.
      Ex: INITSM-21, oracledb-11g-prod, Solaris 11.3,..... etc.

      Steps to reproduce:
      1. Click on the "oracledb-11g-prod" button, just beside the "Affected Server:" text, in the "Can we get this server request approved?" page.
      2. Then the "Object Overview" modal will display.
      3. Click on the "Show graph" icon button.
      4. Click on the "Force" button. Then the graph will display in the Force view.

      Tested URL

      https://instenv-5971-nizh.instenv.atl-test.space/projects/JSM/queues/custom/31/JSM-111

      Steps to Reproduce

      1. Step 1

      Actual Results

      Actual results

      Expected Results

      Fix Information
      RULE :
      The visual state of an active user interface component MUST have sufficient contrast of 3 to 1 with the adjacent background. Exceptions exist.

      HOW TO FIX:
      Fix this issue by adjusting the visual focus indicator or state indicator (e.g. selected, checked, pressed, etc.) of the user interface component and/or background to increase the contrast with either the inner or outer adjacent background to at least 3 to 1.

      REFERENCE:
      WCAG Understanding document: https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast

      BACKGROUND:
      People who have low vision or are colorblind may have difficulty perceiving that an element is interactive or what its state is - e.g. whether it has keyboard focus, is selected/checked/pressed, etc. - if the contrast between the element boundaries and/or state indicators and its background or adjacent colors is insufficient. When an interactive element's visual boundaries and state indicators have adequate contrast, people who have low vision or are colorblind are more likely to be able to perceive which elements on the screen are interactive and what their current state is.

      Screenshot

      Screen Recording

      screen recording

      Workaround

      workaround

      Bug Ref: 745229

      Bulldog Ref: JSMDC-12562

            Assignee:
            Unassigned
            Reporter:
            Matthew Brennan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: