When I enable accessibility in my reports, the final PDF document becomes 20+ times bigger than without accessibility. The reports contain large amounts of data and result in 2000+ pages.
I need the images in my reports (usually only one logo) to have alternative text, so the screen readers can describe them. To achieve this, currently I have to enable accessibility for the entire report, hence the huge final documents.
It would be very useful for my scenario to add alternative text to the PictureBox without declaring the entire report as accessible.
The attached sample has a simple table with two row groups, and "header" rows created via "Insert Row -> Outside Group - above".
The groups have "keep together" set.
But despite this, the header rows render at the bottom of one page, with data rows on the following page. This should never happen, I can't think of any case it would be expected (it would be like having "Chapter 2" at the bottom of a page when the text for it starts on the next page).
I also have a sample with just 1 row group, but with 2 detail rows, and the same thing happens. It only appears to work when there's just 1 row group and 1 detail row.
When generating PDF/UA files, we need to have special objects that are read by an internal system but ignored by screen readers. This cannot be achieved with the existing functionality.
It would be beneficial if we could configure reports so that specific objects inside the generated document are ignored by screen readers. For example, by setting a special value to the AccessibleRole property of a text box.
In the Q3 2026 release, Telerik Reporting updated the kendo font icons used by the web report viewers. Those icons are loaded alongside the report viewers and are not scoped to them, so they override the icons for elements outside the viewers.
For example, the Telerik UI for AJAX product is currently using kendo font icon subset that is older, so when I load the HTML5/HTML% WebForms report viewer on the page, AJAX's icons are overridden and incorrect.
Migrate the web reports viewers to use Kendo SVG Icons instead of the current font icons implementation, as they allow for better flexibility and render more nicely on the page, and will avoid the issue with overriding font icons when the viewers are used with other Telerik products.
I am using the HTML5 report viewer and seeing 4 errors in the WAVE tool, along with multiple alerts. See: https://wave.webaim.org/report#/https://demos.telerik.com/reporting/product-sales
Please consider addressing them.
I have localized a report with a Graph in the 'ar-SA' culture.
When exporting to PDF from the viewer, the report is generated as expected. In the Report Viewer's Preview, though, the Graph Legend and Labels are not correct:
I am using Native Blazor Report Viewer, but the problem also reproduces in the HTML5-based web viewers, with all the themes I have tested.
Hello,
I see from support threads that Telerik really resists any changes to their concept of CSV rendering. And I also understand the reasoning in not changing any default behavior due to its potentially unwanted effect on established customers.
That said, I wonder if the ability to exclude hidden objects (TextBoxes for example) has been proposed and is in the list of potential enhancements. I wouldn't mind if it required a configuration setting like NoHiddenObjects = True where the default is False.
Has that been considered?
The Telerik.Reporting documentation mentions that the Telerik.Reporting.* libraries should be available on nuget.org with the most recent release. However, when I search for Telerik.Reporting in the NuGet Gallery, I am not able to find any Telerik.Reporting.* package. The other products we use (UI for WPF, Document Processing) seem to be available though.
-----------------------------------------
Staff note: On the Reporting side, our initial goal was indeed to make Telerik Reporting available through nuget.org, alongside the rest of the Telerik product portfolio. However, we are currently investigating an issue that is preventing us from publishing the Telerik.Reporting packages to nuget.org, which has delayed their availability.
Please use this feedback item to subscribe to updates and receive a notification as soon as the Telerik.Reporting packages become available on nuget.org.
On export to MS Word, a numbered list that spans two pages restarts at (1) on the second page. Instead, the numbered list should continue numbering from the first page.
For example, if a list has five items and the fourth item starts on a new page, when I export the report to MS Word, the first three items are numbered (1), (2), and (3), and the last two items are numbered (1) and (2) again. The last two items should be numbered (4) and (5).
In addition, if an item in a numbered list splits between two pages, the item is numbered twice: once at the beginning of the item and again on the first line that appears on the next page. The line at the top of the second page is numbered (1). This second number should not appear.
The attached file shows both these issues.
When exporting a report to Excel with the UseExtendedFormatting parameter set to False, the Standard DateTime Format Strings are hard coded as custom formats in the generated XLS/XLSX document.
The custom formats correspond to the current regional settings or, if the report is rendered with a specific culture, the default date format strings for the selected culture.
Double-click selection in the expression editor isn't context-aware. In almost every other application, double-clicking selects a token based on its surrounding context — a single field/identifier when clicking on a field, or the word boundary within a string literal when clicking inside quotes. The expression editor doesn't respect these boundaries, so its double-click behaviour is inconsistent with the standard expression-editor behaviour users expect.
Expected: Double-click selects the relevant token based on context (e.g. an individual field reference, or a word within a string literal).
Actual: Double-click selection ignores context and does not match the token/word-boundary behaviour found in virtually all other expression editors and text inputs.
Request:
Add a RedisStorage constructor overload that accepts StackExchange.Redis.IConnectionMultiplexer rather than only the concrete ConnectionMultiplexer.
Current behavior:
new RedisStorage(ConnectionMultiplexer connectionMultiplexer) requires the concrete type.
Problem:
Modern ASP.NET Core apps manage a single shared multiplexer through DI and expose it as IConnectionMultiplexer — the abstraction recommended by StackExchange.Redis, and the same type
Microsoft.Extensions.Caching.StackExchangeRedis uses via its ConnectionMultiplexerFactory (which returns IConnectionMultiplexer). To call RedisStorage we are forced to downcast our IConnectionMultiplexer back to
ConnectionMultiplexer. This is fragile and it prevents passing test doubles or decorators (e.g. for instrumentation/logging).
Proposed change:
Add RedisStorage(IConnectionMultiplexer connectionMultiplexer), plus a databaseNumber overload (RedisStorage(IConnectionMultiplexer connectionMultiplexer, int databaseNumber)). ConnectionMultiplexer already
implements IConnectionMultiplexer, so this is fully backward-compatible — existing callers that pass a concrete instance keep working unchanged. Everything RedisStorage needs is available on the interface
(GetDatabase for string operations and LockTake/LockRelease, GetSubscriber, GetServer).
Benefits:
- Clean dependency-injection integration with a shared, app-managed multiplexer.
- Unit-testability via a mocked IConnectionMultiplexer.
- Consistency with StackExchange.Redis guidance and Microsoft's own caching abstractions.
Note:
Please target the maintained Telerik.Reporting.Cache.StackExchangeRedis package (the .2 variant appears discontinued after 18.2.24.806 and has no 19.x/20.x release).