On the overview page for the branches within a repository, various contents are displayed in a table below a tab register structure. Navigation is done exclusively with the tab key, which means that keyboard users have to navigate through all tab registers to get to the content in the tab panels. This way of navigating is not efficient.

Suggested fix:

• The tab registers are usually operated with the keyboard in such a way that the first register is jumped to with the tabulator key, navigation between the tab registers is carried out with the arrow keys, while changing to the associated tab panel with the tabulator key button is done. This allows efficient navigation between the tab registers and the corresponding tab panels and the tab order is consistent.
• Note: Screen reader users cannot perceive the roles of the tab registers correctly, as the implementation uses input fields of type "Radio" with integrated links. See also result 9. → For a barrier-free implementation of tab registers, both the roles, attributes and in particular the keyboard operation must be converted to tabs in accordance with the WAI ARIA Authoring Practices.3