Yes, you have now grasped what I had hoped I was explaining clearly. While PDF Exchange Viewer will "play well" to a limited extent with JAWS it, like so many other programs, encounters issues either because it is not coded for accessibility or because JAWS hasn't been coded to work with it (and it's clear to me that there is a LOT of stuff in JAWS that is very one-purpose and one-program customization) or both. When my clients get a PDF document that they know, based on the source, which is usually their online course management systems, has to actually be text but that was originally scanned as an image PDF I wanted them to be able to independently do the conversion in a timely manner. I have encouraged them, when this is necessary, to donate the resulting file back to the source so that it could be used in the future. I can't really even blame the people putting up the image files because some of these are ancient and most folks have no idea that there exists a difference between an image PDF and an accessible PDF with a text layer because, wait for it, they literally don't see it and because they can see they don't have reason to encounter a barrier. They just pass along what they have. I'm trying to make the people I tutor become effective advocates for accessibility not just for themselves but for those who are sure to follow later.