When exporting with  TaggingStrategyType.Build, automatic table detection can include surrounding content in the table and generate rows, cells, and header associations that do not match the document’s logical structure. Headings may become table-cell content instead of remaining separate elements.

The exported PDF may pass automated accessibility validation despite having incorrect semantics for screen readers.

Provide a public API for setting the Scope attribute on explicitly created table-header (TH) structure elements.

Currently,  StructureElement.Attributes,  StructureElementTableAttributes, and  TableScopeAttribute are internal. Applications can create TH elements but cannot directly specify whether headers apply to a row, column, or both.

This prevents PDF/UA-1 compliance when table relationships are not defined through Headers and IDs.

Incorrect CID font resolution corrupts text after import-export.

Add a setting to choose whether import continues or throws when invalid structure-tree data is detected. Default behavior continues import, skipping invalid entries without repairing them.

Exception "Format string is not in the correct format" is thrown when importing a file with the following format string: "US$"#,##0.0"m";($#,##0.0)

The exception is thrown in the ValidateDateTimeFormatDescriptor method. 

Using the PdfStreamSigner to set signature Properties like Name, Location, Reason, and ContactInfo is not respected after export.

Add support for Linked Timestamp Correctness.

Invalid structure tree triggers NullReferenceException instead of InvalidStructureTreeException.

Concurrent PDF export in a fresh process may hang, throw exceptions, or produce incorrect font embedding.

Handle duplicate annotation references across pages during import.

RtfFormatProvider: Merged cells with preferred widths narrower than their full column spans lose their spans on export.

Add support for LT/LTA validation.

Add support for PAdES-B-LTA and renewal.

Add support for PAdES-B-LT / LTV evidence embedding.

Add support for conforming PAdES-B-B/B-T signing profiles.

Currently the format codes in SpreadStreamprocessing are set formatted according to the the current culture. It would be beneficial to have the option to directly set the invariant format code, the way it would appear in the open XML model.

Image export throws IndexOutOfRangeException decoding JPX images with embedded alpha and MCT;
Adobe renders same PDF. Decode and export correctly, preserving pixels and alpha.

Incorrect character spacing when importing CID fonts with the same BaseFont and different width tables.

NullReferenceException is thrown when importing a tagged document that contains a structure element with a /C attribute class but no /ClassMap.

NullReferenceException: 'Object reference not set to an instance of an object.' Telerik.Documents.Fixed.FormatProviders.Pdf.Import.StructureElementsImportContext.ClassMap.get returned null.

The signature field preserves information about the time of signing through the TimeOfSigning property of Signature.Properties. However, the DateTime object doesn't keep info about the time zone the document has been signed in. Some customers need to obtain this information.