Some horizontal page breaks force report processing to create an invalid page clipping during paging. 

In my report, when the content fits in the page width, the PDF document is generated correctly. When there is a horizontal page break though, the content of the pages after the first one is clipped.

When exporting to PDF from Telerik Report Designer, single fields of information are broken out into separate tags (by line) rather than lumped into one tag. If possible, it would be better to have all data from the field sent to one Paragraph tag to facilitate reading via accessibility reading technology.

When exporting the tags for the document's Table of Contents Telerik Report Designer exports TOC leaders as distinct tags, requiring that they be removed when completing the accessibility tagging for the document. Leaders - the ellipses found in the Table of Contents (e.g., Introduction ...................... Page 3) between the TOC item and the page number will be read by assistive technology as "dot dot dot dot dot..." etc. They need to be deleted from the tag tree. Please Artifact them or (preferably) NOT tag them on the export. Thanks.

Reference: 

https://www.levelaccess.com/pdf-table-of-contents/

https://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140408/pdf.html 

When exporting to PDF from Telerik Report Designer the software creates a list of flat links for each TOC entry, but the links are separated in the structure from the TOC Label. While a good start, it would be better to use a main TOC tag under which each line in the TOC would receive a TOCI (Table of Contents Item) tag. Each TOCI would contain the label and link for the respective item. Attaching a few examples to assist.

<TOC>	Table of contents element is an element that contains a structured list of items and labels identifying those items; has its own discrete hierarchy.
<TOCI>	Table of contents item element is an item contained in a list associated with a table of contents element.

References:

https://www.hhs.gov/sites/default/files/pdf-tagging.pdf (page 29).

https://www.pdflib.com/pdf-knowledge-base/pdfua/the-pdfua-standard/ 

I don't seem to be able to place an HTMLTextBox into a Table cell using the Web Designer... Is this not possible yet?

Using the Default or Material Kendo Theme (v5.6.0) with the Telerik HTML5 Report Viewer, the Boolean parameter which uses a Checkbox for it's display, is not visible (this may affect other themes as well).

I confirmed an older version v4.40.0 has a height and width set for the k-checkbox CSS class as such:

https://unpkg.com/@progress/kendo-theme-material@4.40.0/dist/all.css

.k-checkbox {
    border-radius: 2px;
    margin: 0;
    padding: 0;
    width: 16px;
    height: 16px;
    line-height: initial;
    border-width: 2px;
    border-style: solid;
    outline: 0;
    box-sizing: border-box;
    background-position: center;
    background-repeat: no-repeat;
    background-size: contain;
    display: inline-block;
    vertical-align: middle;
    position: relative;
    cursor: pointer;
    -webkit-appearance: none;
}

while the latest v5.6.0 does not:

https://unpkg.com/@progress/kendo-theme-material@5.6.0/dist/all.css

.k-checkbox {
    margin: 0;
    padding: 0;
    line-height: initial;
    border-width: 2px;
    border-style: solid;
    outline: 0;
    background-position: center;
    background-repeat: no-repeat;
    background-size: contain;
    display: inline-block;
    flex: none;
    vertical-align: middle;
    position: relative;
    cursor: pointer;
    -webkit-appearance: none;
}

The checkbox is actually on the page, but is so small it's basically invisible and completely unusable, requiring a manual CSS override to fix.

Many documents have repeating information that is irrelevant and needs to be untagged, or artifacted, so that assisstive technology does not share the information multiple times. Common examples of this situation are headers, footers, page numbers, and decorative images. In most cases, it is not necessary to read these document elements on each page, so we untag the information to prevent repetition for the person reading the document with assistive technology. Is there a way to mark a report section - e.g., the page header or page footer - as Untagged or Artifacted, and have those tags be exported to the PDF? It would save a ton of time having to manually go through several hundred pages and untagging them manually.

Steps to reproduce the problem:

1. Open the attached report in EUD
2. Ensure its RuntimeSettings contain parameter "EnableAccessibility" set to True or add the setting before opening the designer in its configuration file
3. Preview the report and export it to PDF


EXPECTED:
The produced PDF is tagged (accessible) - check it in Acrobat Reader's file properties in the bottom left corner. The file size should be ~155KB
OBSERVED:
The produced PDF is not tagged (accessible). Its size is ~123KB.

When the SkipBlankPages property of the report is set to true, it throws a console error in the browser when there is no significant content in the report:

Hi, While the Report Designer exports tags to the PDF (with Accessibility enabled), the tags exported are not fully compliant with PDF/UA or 508 requirements. For example, my document has several hundred pages, each with two or three data tables on them. While the tags get exported, they are only Paragraph tags, and NOT Table tags. Is there a way to designate Table Header Rows, Header Columns, and Data Cells in Telerik Reporting such that upon export to PDF they get tagged properly?

Telerik Report Designer is one of the few report writing tools on the market that can export tagged PDF content. It's a major advantage of your solution. Why can it not be turned on by default, or enabled via a menu button. Better yet, how about including an Accessibility menu setting to allow for more detailed configuration of key elements?

Currently, Telerik Report Designer cannot export the style heading level to the tag structure in the generated PDF. It exports the headings, yes, but only as a paragraph tag. This request would require that a Heading Level (e.g., Heading 1, Heading 2, Heading 3 ) field be added to the Properties panel such that a text box could be tagged as H1, H2, H3, etc.  According to accessibility guidelines, PDF/UA-1, WCAG 2.1 and 508, the tag tree needs to contain a logical reading order and tag structure. Heading Levels are essential to that. There may be only one H1 - usually reserved for the document title, then major sections get H2, subsections, H3, etc. Can this be done?

I produce a lot of Accessible PDF documents that include many unique images - hundreds in most cases. Each image has alt text descriptions in it in the EXIF metadata of the image file itself. Most of the documents I generate a based on a one or two page template used for each record ID. The images are loaded programmatically based on the ID number for the template. Right now, with Accessibility Enabled, Telerik cannot read the image EXIF data. It would be ideal if it could be configured to pick up the descriptions already inside the image file itself. This applies to the stand alone Report Designer and the Visual Studio version.

Currently,  you can select multiple report items with the CTRL when you run the Web Report Designer on Mac, however, this is interpreted as a right-click. Please, check the attached video.

The correct behavior should be by using CMD.

I display the WPF Report Viewer control in a closable tab. To free the resources I invoke DisposeViewerResources on tab close as described here: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/wpf-application/disposing-the-report-viewer-resources

However, I see the following dialog every time. There is no way to capture this error or suppress the dialog.

Some corner case page size value force report processing to create an invalid page clipping during paging. 

Workaround: If you encounter such scenario, please experiment with changing the page size to another value, which is close to the original one.

Please add the Web Report Designer Item Template for VB.NET projects too

There seems to be no way to create a Style Rule with Style Selector in the Web Designer. The only option available is Type.

Consider adding functionality that allows for loading Assets into the Asset Manager from code. 

I would prefer to store assets in a database and load them up for a user.

Makes more sense than randomly loading them from whatever computer you are working on.

The SVG image from a PictureBox is displayed cut in the Html Viewer. When exporting to PDF it is fully shown.