[
https://issues.apache.org/jira/browse/FOP-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Reischenbacher reassigned FOP-3273:
--------------------------------------------
Assignee: Matthias Reischenbacher
> [PATCH] PDF accessibility tagging stops after first fo/page-sequence
> --------------------------------------------------------------------
>
> Key: FOP-3273
> URL: https://issues.apache.org/jira/browse/FOP-3273
> Project: FOP
> Issue Type: Bug
> Affects Versions: 2.11
> Environment: Windows 11
> Reporter: Russell Kay
> Assignee: Matthias Reischenbacher
> Priority: Major
> Attachments: FOP-3273.patch, PDF-Tagging-WITH-fo-marker-v1.png,
> PDF-Tagging-WithOUT-fo-marker-v1.png, doc-page-sequence-02.fo,
> doc-page-sequence-02.pdf, doc-page-sequence-02.xml, fop.xconf,
> style-page-sequence-02.xsl
>
>
> I'm trying to create a PDF to comply with Accessibility requirements.
> In the "fop.xconf" (included with the bug) file I have accessibility set as
> follows:
> {{<accessibility keep-empty-tags="false">true</accessibility>}}
> And I am also using:
> {{<pdf-ua-mode>PDF/UA-1</pdf-ua-mode>}}
> When creating the Accessible PDF, I found PDF Tagging stops after the first
> <fo:page-sequence> element. In the test files there are three
> <fo:page-sequence> elements in total.
> I have managed to narrow the issue down to the <fo:marker> (XSL line 82).
> I need to include some text in the footer to mark the end of a Chapter, so I
> am using the <fo:marker> to output the "End of Chapter" text.
> If I remove the <fo:marker> (XSL line 82) then the "End of Chapter" text is
> NOT displayed (for obvious reasons) but all three <fo:page-sequence> elements
> are correctly fully tagged.
> {*}Expected result{*}: Entire PDF should always be Tagged
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
