Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-21933

Plan configuration - Stage details - Tasks : Inaccessible by keyboard and no conforming alternate.

XMLWordPrintable

      Issue Summary

      General - The element is not accessible by keyboard alone and there is no conforming accessible version of the same functionality reachable from the non-conforming page.

      Element name: Stages & jobs button

      Location of the element: Clickable Button, just below the "Default plan configuration" heading link, on the left side navigation section, in the main content.

      Additional details: While navigating with the tab key, the button mentioned above is not receiving the tab key focus.

      Steps to Reproduce

      1. Open the home page
      2. Navigate to the "Project" link and activate it.
      3. Select the project link from the main content and activate it.
      4. Navigate to the "Configure Plan" link to activate it 
      5. Observe that the "Stages & jobs" interactive element is not accessible with the keyboard.

      Actual Results

      Missing keyboard support for the "Stages & Jobs" interactive element. This made it difficult for keyboard-only and screen-reader users to access the interactive element.

      Expected Results

      • Mark up the mentioned interactive element using the native <button> element.
      • Modify the scripts to ensure the button is accessible with a keyboard and a mouse.
      • Set the "aria-expanded" attribute to "false" for the button by default as the button is in the collapsed state. Ensure that the value of the “aria-expanded” attribute changes on user interaction via scripting.

      Alternatively,

      If the above implementation is not possible,

      • Use custom role="button" and tabindex="0" to ensure that this button receives keyboard focus and has an interactive role. 
      • Set the "aria-expanded" attribute to "false" for the button by default as the button is in the collapsed state. Ensure that the value of the “aria-expanded” attribute changes on user interaction via scripting.

      Screenshot

      Workaround

      Not Available

      Bug Ref: 460079

              0e35c5b225a8 Bohdan Hulovatyi
              12b69dcabe29 Matthew Brennan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: