Hi Michael,

Thank you for the provided details and StackBlitz example.

From what I can observe in the example, custom <button> elements are rendered in the Grid cells, which is why the keyboard navigation does not behave as expected. To be more comprehensive, in order to include custom elements as part of the built-in keyboard navigation of the Grid, the developer can use the kendoGridFocusable directive and apply it to the respective elements.

More information about the basic concepts of the Grid's built-in keyboard navigation and how to register custom focusable elements (like buttons) within the Grid can be found below:

• https://www.telerik.com/kendo-angular-ui/components/grid/keyboard-navigation#basic-concepts

In this line of thought, I modified the shared StackBlitz example and applied the kendoGridFocusable directive to the <button> elements rendered in the cell template of the Grid:

• https://stackblitz.com/edit/angular-dadm5ywe-yfos2gzm

As a result, the buttons in the above example can be navigated using the Arrow keyboard keys since this is the built-in behavior of the Grid's keyboard navigation - the arrow keys move the focus between the cells. Then, the Tab key can be used to exit the Grid and navigate to the <button> rendered below the component.

With the above being said, the reported behavior of the Grid's keyboard navigation in the initially shared StackBlitz example is expected and not considered a bug on our side since all custom elements in the Grid that must be focusable should be registered as such by using the kendoGridFocusable directive.

I hope the provided information clears up the matter.

Regards,
Zornitsa
Progress Telerik