But, there is no evidence yet that they removed anything.
It’s quite possible (I’d say likely) that ABBY’s PDFs were corrupt all along.
Preview may have tolerated them not because of a special feature which was then removed, but because it happened not to depend on correctness before.
In this case, Apple wouldn’t have been in a position to even know about the problem.
You know who would? ABBY, who have had free access to Big Sur for months. You’d think that even cursory testing at their end would have shown this problem.
They have had months to fix it, months to work with Apple on the issue, any months to publicize it it really is Apple’s fault.
Even if ABBY does have a bug and fixes it then people will still have a bunch of older documents they will want to read.
This is in principle impossible.
If it turns out that there is a widespread problem with many kinds of document that no longer work properly, I’ll be more inclined to say Apple is at fault.
But as it stands, it just seems like ABBY has been producing bad PDFs.
I think it is. Preview used to correctly handle the thing, and now it doesn't. Users cannot be expected to inspect the raw PS code of their PDFs to determine standards compliance. What they can do is assume that something that works yesterday, and appears to work today, is in fact working.
The PDFs didn't change, the application did. It's the application's fault.
If you have compatible behavior that you remove, it's on you to alert the user of the reduced functionality.