[jira] [Comment Edited] (FOP-3273) [PATCH] PDF accessibility tagging stops after first fo/page-sequence

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

Russell Kay edited comment on FOP-3273 at 10/23/25 1:46 PM:
------------------------------------------------------------

[~jgoncalves] ... the provided Test Data, broken into "Chapters", is a simplification of the issue to allow the good guys here in the Apache FOP Dev community to replicate the issue.

[~matthias8283] ... thank you for the update and thank you so much for your efforts!

{*}Additional Info{*}: In my live data, I have the option (an S1000D Business Rule Decision Point) to switch the <fo:marker> between either the "footer" or into the "body of the page" (BRDP-S1-00491). If the <fo:marker> is presented in the "footer" then the issue occurs ("tagging" stops after the first <fo:page-sequence>) but if the <fo:marker> is presented in the "body of the page" then the entire PDF is tagged. This would indicate, like you have mentioned, the issue is "connected" to the <fo:marker> and not the actual <fo:marker> itself.


was (Author: JIRAUSER310982):
[~jgoncalves] ... the provided Test Data, broken into "Chapters", is a simplification of the issue to allow the good guys here in the Apache FOP Dev community to replicate the issue.

[~matthias8283] ... thank you for the update and thank you so much for your efforts!

> [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)