For keyboard users who don't have a specific Context Menu key (see https://en.wikipedia.org/wiki/Menu_key), they typically need to use the Windows standard SHIFT+F10 hotkey to trigger a contextmenu event. For example: 1. In IE, load http://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/columns/context-menu/defaultcs.aspx 2. Tab to a column header link 3. Press SHIFT+F10 (standard Windows/IE hotkey to open context menu) 4. Notice the context menu displays, however, the focus is really on the IE menubar. IE supports F10 to open the menubar, but is also seeing SHIFT+F10 too. Or 1. In FireFox, load http://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/columns/context-menu/defaultcs.aspx 2. Tab to a column header link 3. Press SHIFT+F10 (standard Windows/IE hotkey to open context menu) then press down arrow 4. Notice the context menu displays, however, the focus is really on FireFox's application system menu in the upper left. Chrome does not have this issue - it opens the grid context menu only. We need IE and FireFox to also only open the grid's context menu, and not trigger default browser behavior. According to https://yuilibrary.com/yui/docs/event/contextmenu.html, it is possible to correct this behavior by calling event.preventDefault() when SHIFT+F10 is pressed, but then trigger a synthetic contextmenu event anyway. As a workaround, we know users can press Escape to close the browser's default menu and bring focus back into the HTML document (and thus the grid's context menu), but this throws off the user experience and becomes a training issue.