[ https://issues.apache.org/jira/browse/FOP-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joao Goncalves closed FOP-3152. ------------------------------- Resolution: Cannot Reproduce > DisplayDocTitle true for accessible PDFs even when PDF/UA is not enabled > ------------------------------------------------------------------------ > > Key: FOP-3152 > URL: https://issues.apache.org/jira/browse/FOP-3152 > Project: FOP > Issue Type: Improvement > Components: renderer/pdf > Affects Versions: 2.9 > Reporter: Juhani Laiho > Priority: Major > Labels: accessibility > > I noticed that the document title check fails in Acrobat Pro accessibility > checker when [accessibility element is > true|https://xmlgraphics.apache.org/fop/2.9/accessibility.html#Enabling-accessibility] > in fop.xconf but [pdf-ua-mode > element|https://xmlgraphics.apache.org/fop/2.9/accessibility.html#fop-xconf] > is omitted. When, in addition to setting accessibility to true, I include > pdf-ua-mode in fop.xconf with the value PDF/UA-1, the Acrobat Pro check > passes. > Based on comparing the decoded original PDF and a decoded PDF fixed by > Acrobat Pro, the difference in failing and passing lies in the inclusion of > DisplayDocTitle (with value true). [WCAG 2.1 technique page > PDF18|https://www.w3.org/WAI/WCAG21/Techniques/pdf/PDF18] supports this > conclusion. > Is setting DisplayDocTitle to true tied to PDF/UA mode instead of > accessibility in general on purpose? If not, could DisplayDocTitle be true > whenever accessibility is enabled? My thinking is that some might not target > PDF/UA compliance but would like to minimize the failures in accessibility > checks nevertheless. > Source files that are relevant in this to my understanding: > fop-core/src/main/java/org/apache/fop/pdf/PDFRoot.java > fop-core/src/test/java/org/apache/fop/pdf/PDFUATestCase.java > Relevant Adobe Acrobat Pro support page (see heading "TITLE"): > https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html#check_accessibility_of_PDFs -- This message was sent by Atlassian Jira (v8.20.10#820010)