Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71496

WCAG Operable:2.1 - Keyboard operation and navigation - Result 4. Important content cannot be accessed and operated using the keyboard

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • 2.417

      Individual important content is only visualized as a tool tip when operated with the mouse. Keyboard users and screen reader users therefore have no way of having this information displayed or read out. The following examples stood out:

      • "Weather icon in Branches table: a tooltip above the icon shows a short report summarizing the results of the latest builds
      • Success message and log file in Stage View table: The success message "Success" and the option to open and display the log file are only displayed as a tooltip when using the mouse.
        • This means that blind users and users with motor disabilities are denied the opportunity to take a detailed look at the log file into the build process.
        • This is considered serious, as the usability test in particular has shown that the log file is an important tool for users.
        • After opening the log button, the log file is displayed.
        • Note: The log file is not in the correct tab order. Even if opening with the keyboard were possible, the focus must also be placed in the opened log file.
      • Legends for the trend charts: In the branch view, the various charts provide detailed information about the course, concrete values of the various graphs at specific times, and display pop-ups that can only be made visible when using the mouse.
        • Note: There is an alternative tabular presentation of the values for individual evaluations, provided that the corresponding menu items are selected and displayed, e.g. B. for "CheckStyle Warnings". For the representations of “Trend of the test results" and "Aggregated Analysis Results" this is not the case
      • Context menus offer additional options in various places, but can only be operated with the mouse
      • At one point on the branch page, the menu selectors are hidden even though they are there, as hovering brings to view
      • In the Stage View, the list of commits can only be visualized as a tool tip using the mouse:
        • The operation of an application should be enabled device-independent.
        • This means that all UI elements must be operable with both the mouse and the keyboard.
        • If individual elements only have a mouseover event, they cannot be operated using the keyboard.
        • All UI elements that can be operated with the mouse must also be accessible with the keyboard.
        • Corresponding events for keyboard operation may also have to be added for this purpose. In addition, the focus management must be adjusted so that the focus order corresponds to the order of operation.

          [JENKINS-71496] WCAG Operable:2.1 - Keyboard operation and navigation - Result 4. Important content cannot be accessed and operated using the keyboard

          Cristina Pizzagalli created issue -
          Cristina Pizzagalli made changes -
          Description Original: _This problem has been noticed at the following important points:_
           * _Operating the menu > new page content is not directly focused_
           * _Selection of radio buttons > focus is set to the top of the page_


          After selecting a menu item from the navigation menu and then loading the new pages, the keyboard focus is shifted to the top of the page. Screen reader users are not notified of the new content and must navigate again from the top of the page to the actual main content of the page.

          Since the main content area is not marked as a region either, the navigation menu here cannot be skipped.

          Even users with motor disabilities cannot navigate efficiently, since the keyboard focus is shifted to the top of the page after selecting a menu item.

          {*}Suggested fix:{*}{*}{*}

          For efficient navigation, the focus should be on the new content for dynamically displayed content using Java Script, so that blind and motorized users can see it directly.

          It makes sense to set the focus directly on the first heading in the new content, so that non-sighted keyboard users in particular receive an orientation reference to the new content. To do this, this heading must also be made focusable with tabindex="-1" so that the focus can be set via JavaScript.
          New: Individual important content is only visualized as a tool tip when operated with the mouse. Keyboard users and screen reader users therefore have no way of having this information displayed or read out. The following examples stood out:
           * "Weather icon in Branches table: a tooltip above the icon shows a short report summarizing the results of the latest builds
           * Success message and log file in Stage View table: The success message "Success" and the option to open and display the log file are only displayed as a tooltip when using the mouse.
           ** This means that blind users and users with motor disabilities are denied the opportunity to take a detailed look at the log file into the build process.
           ** This is considered serious, as the usability test in particular has shown that the log file is an important tool for users.
           ** After opening the log button, the log file is displayed.
           ** Note: The log file is not in the correct tab order. Even if opening with the keyboard were possible, the focus must also be placed in the opened log file.
           * Legends for the trend charts: In the branch view, the various charts provide detailed information about the course, concrete values of the various graphs at specific times, and display pop-ups that can only be made visible when using the mouse.
           ** Note: There is an alternative tabular presentation of the values for individual evaluations, provided that the corresponding menu items are selected and displayed, e.g. B. for "CheckStyle Warnings". For the representations of “Trend of the test results" and "Aggregated Analysis Results" this is not the case
           * Context menus offer additional options in various places, but can only be operated with the mouse
           * At one point on the branch page, the menu selectors are hidden even though they are there, as hovering brings to view
           * In the Stage View, the list of commits can only be visualized as a tool tip using the mouse:
           ** The operation of an application should be enabled device-independent.
           ** This means that all UI elements must be operable with both the mouse and the keyboard.
           ** If individual elements only have a mouseover event, they cannot be operated using the keyboard.
           ** All UI elements that can be operated with the mouse must also be accessible with the keyboard.
           ** Corresponding events for keyboard operation may also have to be added for this purpose. In addition, the focus management must be adjusted so that the focus order corresponds to the order of operation.
          Alexander Brandes made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/jenkins/pull/8262 (Web Link)" [ 28822 ]
          Alexander Brandes made changes -
          Assignee New: Markus Winter [ mawinter69 ]
          Alexander Brandes made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Markus Winter made changes -
          Assignee Original: Markus Winter [ mawinter69 ]
          Alexander Brandes made changes -
          Released As New: 2.417
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            Unassigned Unassigned
            cristinap Cristina Pizzagalli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: