Created attachment 168981 [details] Example odt from which the pdf is created Description: The new PDF/UA export function allows to export PDFs which comply with the PDF/UA standard. When images or frames are added to the header the pdf export creates pdfs which violate PDF/UA. PAC3 says that these images/paths/texts are objects which are not tagged. The elements in the header should be tagged as artifact (as far as I know). At the moment VoiceOver (default macOS screenreader) with Adobe Acrobat ignores the elements in the header (as it should be), but to comply the standard they should be tagged as artifacts. Tested: Tested on 7.0.3.1 and dialy master build which contains the fix from bug #139643. Steps to reproduce: 1. Open new Writer document and add a title in the preferences. 2. Add Header and add an image, also set alternate Text for that image. 3. Add a frame with an example text to the header. 3. "Export as PDF..." with "Universal Accessibillity (PDF/UA)" enabled. 4. Test document with PAC3: Image/Text/Path object not tagged. 5. Accessibility check with Adobe Acrobat shows also issues with the image and frame object in header. Reproducible: Always, all OSs Attachments: - Example odt - Created pdf - Screenshot of issues in pac3 (I do not know why the issues itselfs are in german but in english they are: Image object not tagged, Text object not tagged, Path object not tagged)
Created attachment 168983 [details] Created pdf
Created attachment 168984 [details] Screenshot of pac3 issues
I can confirm the bug. This also occurs reproducibly with us.
Adding some background information from the PDF Association's "Tagged PDF Best Practice Guide: Syntax" (Version 1.0, June 2019): Subchapter 3.7.1: Header and footer content Page headers and footers are usually placed automatically as a function of pagination. As such this content is not part of the reading-order of the document and is not considered to be “real content. Subchapter 3.7.2: Page numbers Page numbers must be marked as artifacts in marked-content sequences with a property list entry Pagination (see ISO 32000-1, Table 330 – Property list entries for artifacts) property). Accessible page enumeration is enabled through use of the Page Labels (ISO 32000-1, 12.4.2). It is semantically appropriate to have Page Label values match the visible page number.
The same issues arise when defining borders for paragraph or page styles. This yields Path Object not tagged errors.
confirmed in comment 3
Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/72b69b422d33308809070e98a6ea8daad93e16d2 tdf#139736 sw: PDF/UA export: flys in header/footer are Artifacts It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
fixed on master
Michael Stahl committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/f91da6e6063e0494559a015a0ec6ea38fcb30baa tdf#139736 sw: PDF/UA export: flys in header/footer are Artifacts It will be available in 7.4.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Created attachment 183412 [details] File edited by Dustin with LO 7.4.4.DEV
Created attachment 183413 [details] New File edited with LO 7.4.4DEV
Created attachment 183414 [details] PDF created with LO 7.4.4.DEV
Affected users are encouraged to test the fix and report feedback.: I installed LO 7.4.4. DEV and have performed the Tests. Then exported as PDF and checked with PAC 2021: There were no error messages in the test log
I can confirm that the bug is fixed on current 7.4.4 dev. Thanks a lot for fixing!
Setting verified per latest comments. Thanks for testing!