[
https://issues.apache.org/jira/browse/FOP-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038803#comment-18038803
]
Russell Kay commented on FOP-3282:
----------------------------------
[~jgoncalves]
Firstly ... thank you for your efforts!
I have checked your "table14.pdf" output in Acrobat Pro and PAC:
Your addition of the {{<THead>}} and {{<TBody>}} structure elements has now
kept the "Table Title" and "Column Headings" together in one place.
However:
They are in the wrong order, in that the first {{<TR>}} in the {{<THead>}} is
the "Column Headings" and the second {{<TR>}} is the "Table Title".
- Column Headings
- Table Title
I "think" it should be the other way around
- Table Title
- Column Headings
Also:
The table is still being broken into 2 separate tables in the "tagged"
structure. Rows 1-2-3 (on the first page of the PDF) are in the first "tagged"
table with the {{<THead>}} element but rows 4-5-6 (on the second page of the
PDF) are in the second "tagged" table WITHOUT any {{<THead>}} element.
!table-14.pdf-acrobat-accessibility-tags-v1.png!
This means the PDF "fails" Adobe Acrobat Accessibility Checker because the
second table (rows 4-5-6) doesn’t have any headings.
!table-14.pdf-acrobat-accessibility-checker-v1.png!
Your PDF didn't "Fail" the PAC process:
!table-14.pdf-PAC-Report-01-v1.png!
but it’s also not happy that the second "tagged" table (rows 4-5-6) has a
<TBody> without a <THead>.
!table-14.pdf-PAC-Report-02-v1.png!
Thank you again for your efforts and I’m happy to test anything else you pass
my way!
> 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
> 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)
