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.