Hi,

Having an empty table cell seems to cause PDF/UA-1 validation to fail in PDFs 
generated with FOP version 2.11. This type of table passes in FOP version 2.10 
PDFs. See attached tablecols.fo.

veraPDF 1.28.1 PDF/UA-1 validation fails for PDF generated with FOP 2.11:

<rule specification="ISO 14289-1:2014" clause="7.2" testNumber="43" 
status="failed" failedChecks="1" tags="structure,table">
<description>Table rows shall have the same number of columns (taking into 
account column spans)</description>
<object>SETable</object>
<test>numberOfRowWithWrongColumnSpan == null || wrongColumnSpan == null</test>
<check status="failed">
<context>root/document[0]/StructTreeRoot[0](26 0 obj PDStructTreeRoot)/K[0](28 
0 obj SEDocument Document)/K[0](31 0 obj SEPart Part)/K[0](32 0 obj SESect 
Sect)/K[0](33 0 obj SETable Table)</context>
<errorMessage>Table rows 1 and 2 span different number of columns (2 and 1 
respectively)</errorMessage>
</check>
</rule>

...but passes for PDF generated with FOP 2.10 from same FO.

PDF Accessibility Checker (PAC) 24.4.2 states that "it's possible that some 
PDF/UA requirements aren't met" and reports an "irregular table row" in FOP 
2.11 PDF pointing to R2C2 cell. When checking the FOP 2.10 PDF, PAC reports 
that "the PDF/UA requirements checked by PAC are fulfilled".

If I test again with no empty cells in tablecols.fo (by uncommenting "R2C1"), 
PDF/UA-1 validation passes for FOP 2.11 PDF with both veraPDF and PAC.

Changes I have made to the configuration file (attached fopPDFUA.xconf):
- Added accessibility element with value true with keep-empty-tags attribute 
set to false.
- Changed default-page-settings to A4 size.
- Added pdf-a-mode element with value PDF/A-2a
- Added pdf-ua-mode element with value PDF/UA-1
- Added version element with value 1.7
- Added font elements for Arial to enable embedding required by PDF/A on my 
Windows installation.
- Disabled font auto-detection.

PAC: https://pac.pdf-accessibility.org/en
veraPDF: https://verapdf.org

Could this be a regression? Or should I somehow change my source FO when 
upgrading to FOP 2.11?

Best regards,
Juhani Laiho

Attachment: fopPDFUA.xconf
Description: fopPDFUA.xconf

Attachment: tablecols.fo
Description: tablecols.fo

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to