• Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 2.1
    • controller
    • False
    • Hide

      None

      Show
      None
    • False

      Ansible Automation Platform fails some 508 compliance standards

      For reference: Red Hat 508 Compliance by Application

      2.1.1 & 2.1.2 Criteria (A)

      AAP would benefit from a skip nav feature. In order to access open windows in the right panel you must tab through all items on the left menu.  (move from the left side menu to open the window). Testing resulted in nearly every element being reachable via keyboard-only input. The one exception I found was an inability to access the Jobs>Workflow> visualizer window elements w/o mouse input.

      2.4.1 Criteria (A)

      The user is forced to tab through numerous navigation elements before getting to content and/or links. No visible skip link is provided.

      3.2.2 Criteria (A) & 4.1.3 Status Messages (AA)

      When a workflow is executed a sub-window opens and progressively shows the success or failure of the jobs in real-time. But JAWS is unable to read or detect the job status as it displays.

      2.2.2 Criteria (A)

      A running job is simply displaying log output to the screen in near real-time and this cannot be stopped or paused while the job is running.

      1.3.1 Criteria (A)

      JAWS is unable to read the 'Type'  column heading when tabbing through the Jobs table listing.

      3.3.2 & 3.3.3 Criteria (A/AA)

      input fields are labeled as you move from window to window etc. However, when you launch a job and it fails while running in real-time JAWS (Screen Reader) is not notified leaving the user unaware.

              bcoursen@redhat.com Brian Coursen
              jbird@redhat.com Jeffrey Bird
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: