A new ticket as PDFNET-47914 has been logged in our issue tracking system for the description of errors that you shared. We will let you know as soon as we have some updates regarding ticket resolution. Please spare us some time.
Any updates on the case Asad?
The recently logged ticket is still pending for an investigation. However, we will surely let you know as soon as it is resolved. Please spare us some time.
Any updates on the case Asad
If you can also provide steps on how to resolve the errors, it would really help
Regretfully the earlier logged ticket is not yet resolved. However, we have logged your recent concerns and comments along with the ticket and will inform you as soon as we have additional updates regarding its resolution. Please spare us some time.
We are sorry for the inconvenience.
Any updates on the case?
WCAG says that for PDF documents to bee comply with the accessibility, it must comply with the standard ISO 14289-1:2014 (PDF/UA).
The ISO 14289-1:2014 standard (PDF/UA) refers to the ISO 32000-1 (PDF) standard.
Errors and warnings PDF/UA validator generates according to specifications ISO 14289-1:2014(PDF/UA) and ISO 32000-1(PDF).
Validator’s PDF/UA errors and warnings table is given below. The column ‘PDF/UA Code’ contains paragraph number from the ISO 14289-1:2014 (PDF/UA) specification.
Errors and Warnings of PDF/UA validator (with PDF/UA specification codes)
|5:1||Error||5||PDF/UA identifier missing|
|6.2:1.1||Error||6.2||Structural parent tree: Inconsistent entry found|
|7.1:1.1(14.8.1)||Error||7.1||Document is not marked as tagged|
|7.1:1.1(14.8)||Error||7.1||[OBJECT_NAME] object not tagged|
|7.1:1.2(220.127.116.11)||Error||7.1||Artifact present inside tagged content|
|7.1:1.3(18.104.22.168)||Error||7.1||Tagged content present inside an artifact|
|7.1:2.1||Warning||7.1||Structure tree missing|
|7.1:2.2||Warning||7.1||‘Document’ structure element found which is not a root element|
|7.1:2.3||Warning||7.1||‘[ELEMENT_NAME]’ structure element used as root element|
|7.1:2.4.1||Warning||7.1||Possibly inappropriate use of a ‘[ELEMENT_NAME]’ structure element|
|7.1:2.4.2||Error||7.1||Invalid use of a ‘[ELEMENT_NAME]’ structure element|
|7.1:2.5||Warning||7.1||Possibly wrong nested ‘[ELEMENT_NAME]’ struct element into StructTreeRoot|
|7.1:3(14.8.4)||Error||7.1||Non-standard structure type ‘[TYPE_NAME]’ is neither mapped to a standard structure type nor to another non-standard structure type|
|7.1:4(14.8.4)||Warning||7.1||Standard structure type ‘[TYPE_NAME]’ is remapped to ‘[TYPE_NAME]’|
|7.1:5||Need check manual||7.1||Color contrast|
|7.1:6.1||Error||7.1||XMP metadata missing in document|
|7.1:6.2||Error||7.1||Title missing in document’s XMP metadata|
|7.1:6.3||Warning||7.1||Title is empty in document’s XMP metadata|
|7.1:7.1(12.2)||Warning||7.1||‘ViewerPreferences’ dictionary missing|
|7.1:7.2(12.2)||Error||7.1||‘DisplayDocTitle’ entry is not set|
|7.1:8(14.7.1)||Error||7.1||‘Suspects’ entry is set|
|7.1:9.1(14.7)||Error||7.1||‘StructParents’ key missing in page|
|7.1:9.2(14.7)||Error||7.1||‘StructParent’ entry missing in annotation|
|7.1:9.3(14.7)||Error||7.1||Entry for given ‘StructParents’ not found|
|7.2:1||Need check manual||7.2||Logical Reading Order|
|7.2:2(22.214.171.124.2)||Error||7.2||Characters in a text object cannot be mapped to Unicode|
|7.2:3.1(126.96.36.199)||Error||7.2||Natural language for text object cannot be determined|
|7.2:3.2(188.8.131.52)||Error||7.2||Natural language of alternative text cannot be determined|
|7.2:3.3(184.108.40.206)||Error||7.2||Natural language of actual text cannot be determined|
|7.2:3.4(220.127.116.11)||Error||7.2||Natural language of expansion text cannot be determined|
|7.2:4(14.9.4)||Error||7.2||Stretchable character no tagged using ActualText|
|18.104.22.168||Error||22.214.171.124||Character collection in CIDFont is not compartible with character collection of internal CMap|
|126.96.36.199||Error||188.8.131.52||CIDToGIDMap is not embedded or incomplete in font ‘[FONT_NAME]’|
|184.108.40.206||Error||220.127.116.11||CMap is not embedded for font ‘[FONT_NAME]’|
|18.104.22.168||Error||22.214.171.124||CIDSet is missing or incomplete for font ‘[FONT_NAME]’|
|126.96.36.199||Error||188.8.131.52||Glyphs missing in embedded font ‘[FONT_NAME]’|
|7.21.6||Error||7.21.6||Non-symbolic TrueType font ‘[FONT_NAME]’ has no cmap entries|
|7.21.6||Error||7.21.6||Encoding entry prohibited for symbolic TrueType font ‘[FONT_NAME]’|
|7.21.6||Error||7.21.6||Incorrect encoding is used for TrueType font ‘[FONT_NAME]’|
|7.21.6||Error||7.21.6||Incorrect “Differences” array for non-symbolic TrueType font ‘[FONT_NAME]’|
|7.3:1(184.108.40.206)||Error||7.3||‘[ELEMENT_NAME]’ element on a single page with no bounding box|
|7.3:2||Error||7.3||Alternative text missing for ‘[ELEMENT_NAME]’ structure element|
|7.3:3||Error||7.3||Caption accompanying figure missing|
|7.3:4(220.127.116.11)||Error||7.3||Graphics object is appear between the BT and ET operators|
|7.4.2:1||Error||7.4.2||First heading is not on the first level|
|7.4.2:2||Error||7.4.2||Numbered heading skips one ore more heading levels|
|7.4.4:1||Error||7.4.4||‘H’ and ‘Hn’ structure elements found|
|7.4.4:2||Error||7.4.4||More than one ‘H’ structure element inside parent structure element|
|7.5:1||Warning||7.5||Irregular table row|
|7.5:2||Error||7.5||Table header cell has no associated subcells|
|7.5:3.1||Warning||7.5||Table headers missing|
|7.5:3.2||Warning||7.5||Table summary missing|
|7.6:1||Error||7.6||‘LI’ structure element must be a child of ‘L’ element|
|7.6:2||Error||7.6||‘Lbl’ and ‘LBody’ structure element must be children of ‘LI’ element|
Notes and references
|7.9:2.1||Error||7.9||ID missing in ‘Note’ structure element|
|7.9:2.2||Error||7.9||ID entry in ‘Note’ structure element is not unique|
|7.10:1||Error||7.10||‘Name’ missing in optional content configuration dictionary|
|7.10:2||Error||7.10||Optional content configuration dictionary contains ‘AS’ key|
|7.11:1||Error||7.11||‘F’ or ‘UF’ key missing in file specification|
|7.11:2||Warning||7.11||‘Desc’ key missing in file specification|
|7.13:1||Error||7.13||Signature form field ‘[FIELD_NAME]’ does not conform to the specification|
|7.13:2.1||Error||7.13||Natural language of an alternate name of a form field ‘[FIELD_NAME]’ cannot be determined|
|7.13:2.2||Error||7.13||Alternate field name entry missing in form field ‘[FIELD_NAME]’|
|7.14:1||Error||7.14||‘PrintField’ attribute missing in non-interactive form item|
|7.15:1||Error||7.15||PDF contains a dynamic XFA form|
|7.16:1(18.104.22.168)||Error||7.16||Security settings block assistive technologies from accessing document’s content|
|7.16:2(22.214.171.124)||Error||7.16||Conversion is not allowed by permission restrictions|
|7.17:1||Error||7.17||Document Outlines Error|
|7.17:2||Error||7.17||Natural language of outlines can be determined|
|7.17:3||Need manual check||7.17||Semantically appropriate Page Labels|
|7.18.1:1||Error||7.18.1||Natural language of Contents entry cannot be determined|
|7.18.1:2||Error||7.18.1||Alternative description missing for an annotation|
|7.18.1:3||Error||7.18.1||Annotation is not nested inside an ‘Annot’ structure element|
|7.18.2:1||Error||7.18.2||An annotation with subtype undefined in ISO 32000 does not meet 7.18.1|
|7.18.2:2||Error||7.18.2||An annotation of subtype TrapNet exists|
|7.18.3:1||Error||7.18.3||Tab order entry in page with annotations not set to ‘S’ (Structure)|
|7.18.4:1||Error||7.18.4||‘Widget’ annotation not nested inside a ‘Form’ structure element|
|7.18.5:1||Error||7.18.5||‘Link’ annotation is not nested inside a ‘Link’ structure element|
|126.96.36.199:1||Error||7.18.6||CT key is missing from the media clip data dictionary|
|188.8.131.52:2||Error||7.18.6||Alt key is missing from the media clip data dictionary|
|7.18.7:1||Error||7.18.7||File attachment annotation. ‘F’ or ‘UF’ key missing in file specification|
|7.18.7:2||Warning||7.18.7||File attachment annotation. ‘Desc’ key missing in file specification|
|7.18.8:1||Error||7.18.8||A PrinterMark annotation is included in logical structure|
|7.18.8:2||Error||7.18.8||The appearance stream of a PrinterMark annotation is not marked as Artifact|
|7.19:1||Need check manual||7.19||Actions were found. Need to check actions according to specification PDF/UA manually|
|7.20:1||Error||7.20||Reference XObject shall not be used in conforming PDF/UA file|
|7.20:2||Error||7.20||The content of Form XObject doesn’t incorporated into structure elements|
I didn’t understand. Where would I a description and solution of the error
Above is the shared list of all error messages. The ticket is still under investigation and not resolved yet as it requires additional investigation and new funcationality implementations. We will let you know as soon as the ticket is resolved. Please spare us some time.
We are sorry for the inconvenience.
Do we have an update on the ticket
Regretfully, the ticket is not yet resolved as it requires more time to investigate. We will surely inform you as soon as it is resolved. Please spare us some time.
We are sorry for the inconvenience.
Do we have an update. Actually we were on a deadline. It would really help if we get the solution soon
Any updates on the case?
We are sorry for the delayed response.
The investigation of earlier logged ticket is completed and we already have shared the error list and description with you. Regarding solution of these errors, please note that we need to implement several features and new functionalities in the API in order to offer solution to all errors. The task is quite long and needs significant amount of time.
We will further create more tickets/tasks in our issue tracking system and share with you. Please be patient and spare us time.
Some of the issues in the provided error list can be resolved smartly by converting PDF to PDF/UA. In order to do this, please visit “Working with Tagged PDF” section in the API documentation.
But many other errors that are listed above cannot be fixed in this way. They are involved with the lack of a logical structure of the document, alternative descriptions, markups, and other entities that only the author of the document understands. However, we have the ability to create PDF/UA compatible documents using TaggedPDF functionality.