Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.1, 2.2
-
None
-
None
-
CentOS 7, virtualized hardware
Description
When adding the role="artifact" attribute to <fo:static-content>, accessibility tagging is suspended after the first <fo:page-sequence> element. In testing, this occurs when the contents of the first <fo:page-sequence> output more than one page of content. Testing was conducted in FOP 2.2 and 2.1, using Adobe Acrobat Pro to validate tagging. Attached samples:
- acrobat-noartifact.jpg - Acrobat Pro's tag view when role="artifact" is not present
- acrobat-artifact.jpg - Acrobat Pro's tag view when role="artifact" is present (note only one "<Part>", which maps from <fo:page-sequence>)
- fo-test-22-noartifact.xml & fo-test-22-noartifact.pdf - fo and corresponding PDF generated using FOP 2.2 with role="artifact" not present
- fo-test-22-artifact.xml & fo-test-22-artifact.pdf - fo and corresponding PDF generated using FOP 2.2 with role="artifact" present