PDF/UA: Rectangle and Line elements not tagged as Artifact – PAC reports "Path object not tagged"

[sepkowskaanna-coder]

When generating PDF/UA-compliant reports with net.sf.jasperreports.export.pdf.tagged=true, any graphical elements such as , , or that are styled with net.sf.jasperreports.export.pdf.tag = Artifact still cause PAC 2021/2024 to fail with the following error:

"Path object not tagged"

This occurs even when all accessibility-related properties are properly configured in the .jrxml template.

Steps to reproduce:

1. Create a simple .jrxml file that includes a or component.

2. Add this property to the element:

3. Set the global export property in the report:

4. Export the report to PDF.

5. Open the result in PAC 2021 or PAC 2024 and run the accessibility check.

Expected behavior:
The graphic element should be correctly tagged as an Artifact in the PDF logical structure, and the PAC checker should not report it as untagged.

Actual behavior:
PAC reports an error:

"Path object not tagged"

This makes the generated PDF non-conformant with PDF/UA, even though the correct tagging property is used.
Tested on:

JasperReports Studio: 6.20.6 and 6.21.5

JasperReports library: same versions

PDF viewer: PAC 2024, Adobe Acrobat Pro DC