[jira] [Commented] (FOP-3165) [PATCH] FOP tags Tables in PDF 1.4 style if PDF/UA-1 mode active

    [ https://issues.apache.org/jira/browse/FOP-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17932174#comment-17932174 ] 

Greg K. commented on FOP-3165:
------------------------------

The problem is that with PDF/UA-1 mode active, table row groups {_}are not tagged at all{_}, so while footer rows are _drawn_ in the right place on the page they are not _spoken_ in the correct order by screen readers. This needs a higher priority and a fix in 2.11.

> [PATCH] FOP tags Tables in PDF 1.4 style if PDF/UA-1 mode active
> ----------------------------------------------------------------
>
>                 Key: FOP-3165
>                 URL: https://issues.apache.org/jira/browse/FOP-3165
>             Project: FOP
>          Issue Type: Bug
>    Affects Versions: 2.9
>         Environment: Windows 10, PAC 2021 for tagging analyzes.
>            Reporter: Nico Kutscherauer
>            Priority: Major
>              Labels: Accessibility, Table, Tagging
>         Attachments: FOP-3165.diff, table-14.jpg, table-ua.jpg, table.jpg
>
>
> Hi,
> this small GitHub project shows the problem:
> [https://github.com/nkutsche/fop-pdf-ua-table-tagging-issue]
>  
> A [table|https://github.com/nkutsche/fop-pdf-ua-table-tagging-issue/blob/main/table.fo] is rendered to PDF using FOP 2.9 with three different configs. The differences are:
> [Config 1: PDF 1.5 is requested|https://github.com/nkutsche/fop-pdf-ua-table-tagging-issue/blob/main/config/fop-config.xml].
> [Config 2: PDF 1.5 is requested and PDF/UA-1 mode is active.|https://github.com/nkutsche/fop-pdf-ua-table-tagging-issue/blob/main/config/fop-config-ua.xml]
> [Config 3: PDF 1.4 is requested.|https://github.com/nkutsche/fop-pdf-ua-table-tagging-issue/blob/main/config/fop-config14.xml]
>  
> I analyzed the result PDFs with PAC 2021 - this are the screenshots focosing the table footer:
>  
> ||Config 1: PDF 1.5||Config 2: PDF/UA-1||Config 3: PDF 1.4||
> |!table.jpg|width=481,height=200!|!table-ua.jpg|width=386,height=200!|!table-14.jpg|width=468,height=200!|
>  
>  
> You see that if the {{PDF/UA-1}} mode is *active* the tagging of {{{}TBody{}}}, {{THead}} and {{TFoot}} are lost and the {{TFoot}} row is missplaced (at least on my point of view).
> The reason for adding the PDF 1.4 version was, that PDF 1.4 knows only the tags {{{}Table{}}}, {{{}TR{}}}, {{TH}} and {{TD}} (See [PDF 1.4 specification|https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/pdfreference1.4.pdf] Table 9.22). With PDF 1.5 {{{}TBody{}}}, {{THead}} and {{TFoot}} was introduced (see [PDF 1.5 specification|https://opensource.adobe.com/dc-acrobat-sdk-docs/pdfstandards/pdfreference1.5_v6.pdf] Table 10.22).
> *Conclusion:* FOP tags tables in PDF 1.4 style if PDF/UA-1 mode is *active* even if PDF 1.5 is generated. If PDF/UA-1 mode is *inactive* it tags tables in PDF 1.5 style even if PDF 1.4 is generated.
> Am I correct that this is not the desired behavior? I think we could live with the PDF 1.4 style if the table footer wouldn't be on top of the body. On my point of view this is also in the PDF 1.4 style wrong.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)