Blocker for Accessibility

We want to reach a more handy application for colleagues with a handicap.

The most critical errors in handling are hidden functions for blind colleagues and features with could not reached by the keyboard.

The menu of the main navigation (2.2 A). It is possible to access with the  ENTER key but ther is no direct node in the source, instead it will shown in other list elements. Any screenreader will stay in the read mode. For blind users it isn't accessible directly

       ▪ within the menu "more" in the view of the issue the screenreader  will only read the first 6 options afterwards the focus will chane  (picture 1  mark D)

• The contents under the "Export" button in the issue view (picture 1 mark C)
• The menu for changing the display of the search view (picture 1 mark B)
•  Drop-down lists on the dashboard, e.g. the "..." menu
• The search field of the main navigation (picture 1 mark A)

The drop-down lists in the main navigation as well as the other highlighted drop-down lists can still not be operated completely with the keyboard, the selection options cannot be accessed using the keyboard. This problem persists.

The filter lists are now usable with keyboard.

However the focus shall stay in the list of options after choosing an option.

Using the keyboard and the context menu key you only get the browser's own context menu for the link. However, this does not correspond to the functionalities of the context menu, which can be obtained by right-clicking a backlog entry.

• It must be possible to call up the application's own context menu for both keyboard and mouse operation.

 Using the keyboard and the context menu key, you only get the browser's own context menu for the link. However, this does not correspond to the functionalities of the context menu that can be obtained by right-clicking on a backlog entry.

• It must be possible to shift the sprints with the keyboard as with the mouse

Missing focus retention of individual elements

• The “Boards” button in the submenu of the project view does not have focus (see picture 3, marker A). This is only implemented with a <div> element, which cannot be focused.
• The elements "Versions" and "Epics" in the backlog do not receive the focus because list elements (<li>) are only marked with role = button (see picture 3, marker B).
• The close button of the preview on the right side in the backlog or sprint board. This can only be opened / closed with the access key "t".

All control elements must also be accessible and operable via the keyboard.

Date entry when creating an issue

→ The date picker must also be usable using a keyboard and screen reader, or it must not be perceptible using a screen reader. In this case, a blind user can only enter the date using the input field

→ There must be a note for screen reader users about the format in which the date is expected.

Shortcut-Pop-up not scrollable   (picture keyboardshortcuts)

→ The area with the scroll bar should be focusable and included in the keyboard sequence so that the list can be moved up or down using the arrow keys.

Processing of individual fields   (picture 5)

The fields can be selected and edited directly in the overview with the mouse. The fields cannot be focused with the keyboard and cannot be edited directly in the overview. All content can be edited using the keyboard if the displayed issue is switched to edit mode using the edit button.

→ All fields that can be edited with the mouse in the overview mode should also be editable with the keyboard. For this it must be ensured that they can be focused and changed using the keyboard.

Additional information cannot be used by keyboard users (tooltips)  (picture 6-7)

→ The information contained in the tooltips must also be accessible using the keyboard. For this, the elements must be integrated into the focus sequence and when focus is retained, the respective tooltip must appear and be recorded and read out by the screen reader.

 1

2

3

4

5

6

7

-->Additional Information for the integration of keyboard usage: the elements must with <menu> and<menuitem>, or <combobox> and<option> flagged correct , to switch the screereader behavior from read to select. example https//www.w3.org/TR/wai-aria-practices/examples/menubar/menubar-1/menubar-1.html and https://www.w3.org/TR/wai-aria-practices/examples/combobox/aria1.1pat-tern/listbox-combo.html.