While customising templates/CSS, I noticed the .trv-parameters-wrapper div as follows:

<div tabindex="300" class="trv-parameters-wrapper" aria-label="Parameters area. Contains 4 parameters.">
<div class="trv-parameter-container k-card"></div>
</div>

I’m working on a project that requires generating Section 508-compliant PDFs, and I’m using Telerik Reporting to build the accessible reports. However, I’ve run into a problem with how screen readers—specifically NVDA—are interpreting table content.

In my report’s table, some values like 12/01/2023 aren’t being read as dates, and values like (192,340.00)—which represent negative numbers—aren’t being interpreted as “negative” or addressing the parenthesis.

When using screen reader applications like JAWS or Narrator, those tools read accessible reporting PDFs in an incorrect order. For example, if I have two items in the report, the reader will read the second item first.

Additionally, images whose AccessibleDescription I have set may be read multiple times..

My report has a Text Watermark as part of the PageSettings, and is configured for Accessibility. The report contains a Page Header and Page Footer. In the Page Footer, there are two TextBoxes.

When I generate an accessible PDF with Telerik Reporting and use the Adobe Reader > Read Out Loud functionality, it doesn't read the content of the second TextBox in the Page Footer.

When an HtmlTextBox contains a large HTML ordered list that exceeds a single page height, the generated PDF is cut at the pixel-level page boundary rather than at a text line boundary. This results in a line of text being visually split mid-glyph — part of the line appears at the bottom of one page, and the remainder is orphaned at the top of the next page.

To reproduce, create an HtmlTextBox that contains an <ol> with lots (>40) <li> items, so they span more than one physical page and export to PDF. Observe the page boundary where the list crosses a page — the split occurs mid-line.

Expected behaviour:
The renderer splits the HtmlTextBox content at a complete line boundary, consistent with how a plain TextBox behaves.

Actual behaviour:
The split occurs at the pixel-level page margin, cutting through a rendered text line.

Please note the spelling error in the k-notificaiton-error class name. Should be k-notification-error:

<div class="trv-parameter-error k-notification k-notificaiton-error" style="">
                <span class="k-notification-status k-icon k-i-x-outline"></span>
                <span class="trv-parameter-error-message k-notification-content">Parameter value cannot be empty.</span>
            </div>

Because of this, error messages are rendered with incorrect color (should be red):

I am using the ObjectDataSource component of the Standalone Report Designer. However, I get errors mentioning that types from `System.Private.CoreLib` cannot be loaded. This used to work in version 19.3.26.121. The workaround in the latest version is to manually register the `System.Private.CoreLib` assembly in the designer through `assemblyReferences` (File -> Options -> Add).

Currently, the GetDesignerResource endpoint of the Web Report Designer service is case-insensitive, which can lead to issues if the URL is made lowercase at some point, such as by a URL rewrite rule, or similar scenarios.

For example, the following reference to the Web Report Designer script will load return the file:

<script src="api/reportdesigner/designerresources/js/webReportDesigner"></script>

But if lowercase is used, for example, like this:

<script src="api/reportdesigner/designerresources/js/webreportdesigner"></script>

The request will return a 404(Not Found) response.

Using the text-indent CSS setting results in part of the text on the first line being cut off:

I cannot localize the messages of the Angular and React report viewers using the suggested approaches:

• Angular Report Viewer Localization - Telerik Reporting
• Localizing the React Report Viewer - Telerik Reporting

The only alternative is to use the approach from the Localization of the HTML5 ReportViewer Explained - Telerik Reporting article, which I can do only by loading the string resources script in index.html of the SPA.

If I try to drag & drop fields in the Standalone Report Designer for .NET, it does not allow me to paste the field, and the icon changes, indicating that the action is not allowed.

On the other hand, I can drag & drop the fields as expected when using the Standalone Report Designer for .NET Framework.

After updating to the Q1 2026 release of Reporting, I get the following error when passing the value of a DateTime parameter from the main report to a DateTime parameter of a report that I open via the Navigate To Report action:

CSharp.Net10.ReportingRestServiceCorsDemo Error: 0 : Parameter /Date(1771253073461)/ does not match Epoch regex format!
CSharp.Net10.ReportingRestServiceCorsDemo Error: 0 : Parameter /Date(1771253073461)/ does not match Epoch regex format!

The issue seems to occur only when directly passing the value of the DateTime report parameter, so as a workaround, I decided to create a new date using the Date() function. For example:

When using a report parameter of type string whose value resembles a date format (e.g., "3036-01"), the System.Text.Json serialization logic used by Telerik Reporting incorrectly treats the value as a date instead of a plain string. As a result, the parameter is serialized and displayed as a parsed DateTime value rather than the original text, leading to unexpected outputs such as "3036-01-01T00:00:00.0000000":

I have an image set to the checkbox through the CheckedImage property. When I export the report to Excel using the Skia graphics engine, the image is not present at all, or cut off.

The same issue is not present in the GDI engine or with the PictureBox item.