Show Advanced KnowledgeHide Advanced Knowledge

Proper Roles for Metabar

1 Initial Problem

The Metabar is tagged <nav> but its keyboard interface relies on tab, only. Arrows cannot be used.
The focus order is not sensible.

2 Conceptual Summary

The four entries of the main do not seem to be very similar.

1. For the notification center to become an actual menu it should have the entries "x Background Tasks", "x unread Mails Inbox", "2 Chat Conversation". All of those entries should be links and transport you to the respective component if clicked upon. Removing entries via the close button should not be possible.
2. The search is different from all other enries and should not be lumped together with the other three. The search should be its own animal and in first position. Role needs to be specified, "dialog" might be a candidate.
3. For the who-is-online entry the main menu entries are to be "Technical support", "All User" and so forth. The entries can be opened and closed and the list of users is shown when open. The filter is an obstacle to being a proper menu. The initial entry in the list of who-is-online-users should be a link calling a dedicated page of who-is-online-users above which is the filter (similar to the dedicated search page where the search form is located above the search results).
4. The avatar entry is cleary a menu and carries the menu role rightly.

The menu functionality of the Meta Bar entries "notificacion center", "who is online", and "avatar" follows the recommendation of the WCAG and BITV for the behaviour of web menus. Thus ...

• it bears the semantically correct HTML tags, e. g. the nav-tag for the navigation area, the ul/li-tags for nested unordered html lists, a.s.o.,
• keyboard control follows the recommendation for menus, such as
  • arrow keys for navigating the menu (up/down arrow keys for moving the focus within the menu, right/left arrow keys for opening and closing sub menus)
  • enter key for triggering hyperlinks and (in addition and alteratively to the arrow keys right/left) opening/closing sub menus.
• after triggering an entry in the Meta Bar or one of the submenus, ILIAS will take user to the requested content (from Meta Bar to a requested submenu, or from menuitem to requested "subsubmenu" or dedicated content). All slates disappear as menus usually do when an item is triggered and opens a dedicated content.

3 User Interface Modifications

3.1 List of Affected Views

• … { Please list titles of all views (screens) of ILIAS that should be modified, newly introduced or removed. }

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Wolfgang Schmidt-Sielex
  
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

Schmidt-Sielex, Wolfgang [WSS] 2023-07-20: Feature has been discussed by a sub-group of SIG accessibility. The sub-group renamed the request from 'Accessible Metabar' to 'Proper Roles for Metabar' and pushed it to 'suggested for 10'. Solution needs concept. Perhaps we need to divide it into smaller packeages like: just the search, just the user menu, ...
Further discussion needed.

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.