Hi,

      There is a cascading bug that we found in a scenario, where Telerik keeps adding default TabIndex of 0 which causes navigation problems, and removing it produces odd behavior with the JAWS Screen Reader in different browsers as mentioned under point 2. 

When the TabIndex is set :
1. The Radmenu adds tabindex=0 attribute to its rendered HTML and it causes some keyword navigation issues. 
Currently, the following navigation issues are noted when using Radmenu without removing the tab index attribute. The issues are present in keyboard and screen reader navigations.
• When tab key is pressed once the focus is on the entire menu and focus goes to the first menu item only on the second tab press. So tab has to be pressed twice to get focus on the first menu item. This is noted in all browsers.
• When using multiple Radmenus, the last item on the first Radmenu keeps highlighted after moving to the second menu. This issue is found in all browsers except IE11.

In order to fix the above:
The below javascript fix was applied. It removes the tabindex attribute from the menu using JS.

//Removes the tabindex attribute of RadMenu.
function RemoveRadMenuTabIndex() {
$telerik.$(".RadMenu[tabindex=0]").removeAttr("tabindex");
Sys.Application.remove_load(RemoveRadMenuTabIndex);
}
Taken from:

https://feedback.telerik.com/aspnet-ajax/1377202-unable-to-move-focus-away-from-radmenu-with-tabindex-0-when-tab-shift-tab-is-pressed

2. But now, when the JAWS screen reader is running:
That the tabindex gets removed via the above the JS Function, and hence the following problems occur when the TabIndex is not set :
- Using the screen reader with Edge browser, the submenu items are not showing (will not open at all) when using Radmenu with default render mode.
- The screen reader won't read the sub-menu items in any browser.

https://www.freedomscientific.com/Downloads/JAWS
Tested with screen reader JAWS 2018 (demo/trial version runs well in 40-minute mode).