Progress® Kendo UI® for Angular Feedback Portal
Back to Feed
Request a Feature Report a Bug
Unplanned
Last Updated: 24 Apr 2026 08:04 by ADMIN
Kevin
Created on: 22 Apr 2026 15:54
Category: Kendo UI for Angular
Type: Bug Report
0
WCAG failure using axe DevTools for Kendo Angular Grid

You're docs say

Open the example in a new window to evaluate it with Axe Core or other accessibility tools.  for the Kendo angular grid

When i do that i see the attached error, which is the same issue i get in our product when running playwright axe

That suggests to me that it is not WCAG 2.2 compliant

 

Ensure elements with an ARIA role that require child roles contain them

more information Link opens in a new window

Element Location:

.demo-frame.loaded.demo-module--wrap--718a6 > .demo-module--demoWrap--d1437 > .demo-module--explorerWrap--4bf1f.flex-grow-1 > .demo-module--demoBody--97eee > iframe #k-fbe44131-4768-4755-93c3-e321b714780e
<div role="grid" kendodragtargetcontainer="" kendodroptargetcontainer="" mode="manual" class="k-grid-aria-root" id="k-fbe44131-4768-4755-93c3-e321b714780e" aria-label="Data table" aria-rowcount="62" aria-colcount="5">

To solve this problem, you need to fix the following:

Element has children which are not allowed: div[tabindex]

Related Node

<div tabindex="-1" class="k-grid-content k-virtual-content">
 
 

Attached Files:
1 comment
ADMIN
Martin Bechev
Posted on: 24 Apr 2026 08:04

Hi Kevin,

Thank you for the provided feedback. We can confirm that Grid accessibility and keyboard navigation function as expected.

The Grid produces two known warnings, which can be safely ignored for now —“Scrollable region must have keyboard access” and “Certain ARIA roles must contain particular children".

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

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Create an account Log In
View
Type
Status
Category