1. Meta Nav

   • the nav has a role="tablist" hence the nav is not announced as navigation = will check
   • links should be in a list (ul > li) = will check
   • there should be aria-labels on the nav tags to distinguish between "meta", "main" and "sub" navigations
     • i guess the labels are not understandable by the users, moreover we need all the tranlstions for them

2. Main nav

   • when the flyout is opened, the first element inside should be in focus
     • all tabs are workling the same way, we should not change the behaviour of one case

3. Meta Nav Popups

   • users are currently stuck in the popup , when navigating via Screenreader (Keyboard) to a button, link, input field.
     • user can navigate with the keyboard to the close element on the top right or even just click escape

Hi @mmarinkov,

1. Meta Nav
   we can use translation keys for the aria-label, but first we need to know, if those aria-labels already exists or need to be added by you.

2. main nav
   Since the main nav is a core feature of the page, it requires a high level of accessibility. So the focus order needs to be correct and mouse operation should equal key operation. Therefore we should think of adding this case or find an alternative to provide this functionality.

3. Meta nav popup
   This is a voiceOver Screenreader issue only. I tested this on macOS, voiceOver, Chrome. The user can't navigate back to the close button once the focus is on a link or button. This is especially an issue for the search popup since there is a tab componenten below the button which the screenreader user can never reach. It would be great if you could find a fix for this.

3. is a standard safari behaviour. when enabling the options it works

/cib

Branch feat/issue-1621 created!

Summary ticket

1. Has been implemented the only part missing is:

• the right naming conventions and translations for the meta/mai nav from IBM

2. Focus in Flyout

• we should follow this example:https://www.ibm.com/de-de. In our nav we cannot navigate inside the flayout

3. Is a standard safari behaviour. when enabling the options it works