Hello Boby,

Thank you for the provided feedback.

I noticed that this is a duplicate ticket of another private one, but I will answer it again for visibility.

We can confirm that Grid accessibility and keyboard navigation function as expected.

The two reported warnings—“Scrollable region must have keyboard access” and “Certain ARIA roles must contain particular children”—are known issues and can be safely ignored for now.

We recognize that having zero accessibility warnings is an important metric, and we consistently strive to meet that standard for all Kendo Angular components. However, due to recent updates in Chrome and the fact that the Grid markup does not follow a standard HTML table structure, these warnings cannot be fully avoided for the Grid at this point.

Currently, there is no available workaround that can be suggested to resolve the warnings and keep the same keyboard navigation and accessibility level. The accessibility attributes are interconnected and depend on one another. Attempting to modify them to address the current warnings results in new warnings, while also degrading keyboard navigation behavior and accessibility reading levels.

We are still exploring opportunities for adjusting the Grid markup to comply with Axe, without breaking clients who already use and customize the Grid, while maintaining the current level of keyboard navigation and accessibility, or enhancing it.

Regards,
Martin Bechev
Progress Telerik