Unplanned
Last Updated: 12 Nov 2025 13:13 by ADMIN
Taarti
Created on: 27 Jul 2022 15:53
Category: Grid
Type: Bug Report
28
Grid Column Headers accessibility compliance

In the case of a sorted column, NVDA is not narrating the correct column name and narrating the incorrect Roles for the column headers.

In the case of an unsorted column, NVDA is narrating the column name twice and repeating the information.

4 comments
ADMIN
Hristian Stefanov
Posted on: 12 Nov 2025 13:13

Hello,

Accessibility remains a constant focus for our team. During implementation, we discovered that the required changes were broader and more intricate than initially anticipated, extending the scope beyond this release cycle.

As a result, we’ll be continuing the work into the next quarter to ensure a thorough and well-tested solution. Please rest assured that this item is still in progress and remains a priority for us. Updates will follow here publicly.

Please excuse us if this causes any inconvenience - your patience and understanding are highly appreciated.

Regards,
Hristian Stefanov
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.

Alexander
Posted on: 12 Nov 2025 12:06

Hello all,

I was just checking version 12.0.0 and nothing happened in the meantime in regards to this issue, right?

Regards,
Alex

ADMIN
Hristian Stefanov
Posted on: 13 Aug 2025 08:32

Hi Alex,

Rest assured that accessibility remains one of our priorities. In this release, we hit a blocker that pushed the fix delivery a bit, and our new target is the end of this month.

Please keep tracking the item—work on it hasn’t stopped.

Regards,
Hristian Stefanov
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.

Alexander
Posted on: 12 Aug 2025 10:27

Hello Telerik team,

would you mind giving us some explanations for why the status has been changed from "Planned" to "Unplanned" yesterday? This item is marked as duplicating a few other items. This item has also been linked to from a few bug reports we submitted as support tickets with the comment that all of these will be resolved once this gets resolved, as well as a promise that the fix will be included in the upcoming quarterly release:

What can we expect to get in the next release? No improvements? A few improvements? Is accessibility no longer a priority? What do we tell our screen reader users?

Regards,

Alex