@AlekseiSemenchenko : As you mentioned this would be fixed in 25.8, it’s already 25.9. Can you confirm when can we get this fix available?
@amitdash : It’s not useful for us to integrate today then.
Hello @pankajgupta !
Alexey will be back from vacation on Wednesday and we will be able to review with him what can be done there.
Can you please share the exact files and scenario that is not yet covered or supported?
that would help us to focus on your specific issues
hey @yuriy.mazurchuk : Files are same as above. With 25.7 , the accessibility of pdf document post merge has maximum number of supported standards/tags from file rather than max from any file. Let’s say you have 10 pdf files o merge, first file used to define the max criteria for accesibility post merge even if other than first(let’s say second) file has maximum no of tags/ standards.
Hi @pankajgupta!
Thank you for your patience. Our team is working on this topic, we are cerfully reviewing sample files you shared. Most documents showed accessibility validation issues after merging, mostly related to structure tree / tagged PDF content.
The current merge logic uses the first document as a base and then appends pages from others, which does not fully preserve accessibility metadata.
We are now implementing a new merging approach using PDF facades, which allows a more granular processing of tagged content and should improve accessibility preservation. This work is still in progress.
We will update this thread as soon as we have a test build available.
Thank you for your cooperation and patience!
Hi @pankajgupta !
Please be aware that we are preparing new GroupDocs.Merger for Java 25.12 release with fixes should be ready early next week,