[
https://issues.apache.org/jira/browse/FOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joao Goncalves reassigned FOP-3282:
-----------------------------------
Assignee: Joao Goncalves
> PDF Accessibility - Table overflow tagging issue
> ------------------------------------------------
>
> Key: FOP-3282
> URL: https://issues.apache.org/jira/browse/FOP-3282
> Project: FOP
> Issue Type: Bug
> Affects Versions: 2.11
> Reporter: Russell Kay
> Assignee: Joao Goncalves
> Priority: Major
> Attachments: Table-03-FOP-01-v1.png, Table-03-FOP-02-v1.png,
> Table-03-FOP-PAC-01-v1.png, Table-03-Other-01-v1.png, fop-pdf-ua.xconf,
> table-03.fo, table-03.pdf, table-03.xml, table-03.xsl,
> table-14.pdf-PAC-Report-01-v1.png, table-14.pdf-PAC-Report-02-v1.png,
> table-14.pdf-acrobat-accessibility-checker-v1.png,
> table-14.pdf-acrobat-accessibility-tags-v1.png, table14.pdf
>
>
> Sorry guys ... another PDF Accessibility issue!
> I’m using the following setting to create a PDF/UA PDF file:
> * {{<accessibility keep-empty-tags="false">true</accessibility>}}
> * <pdf-ua-mode>PDF/UA-1</pdf-ua-mode>
> * <version>1.7</version>
> _(fop-pdf-ua.xconf attached)_
> I have found that where a table overflows the page, the "tagging" process
> creates a "new, separate table" within the "tag" structure:
> !Table-03-FOP-01-v1.png!
> First "tagged" table structure contains Rows 1-2-3 and the second "tagged"
> table structure contains Rows 4-5-6
> The "new, separate table" from a "tagged" perspective for Rows 4-5-6 doesn't
> have any "TH" elements.
> This means the PDF/UA fails validation in Acrobat Pro:
> !Table-03-FOP-02-v1.png!
> and PAC:
> !Table-03-FOP-PAC-01-v1.png!
> If I build the same file using a "different" FO Processor, it creates a
> single "tagged" instance of the Table:
> !Table-03-Other-01-v1.png!
> Which passes PDF/UA validation.
> *Expected Result:* I "think" it needs to build a single "tagged" instance of
> the Table in the tagged structure!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
