So the real question is: when will browsers get around to more advanced support for PDF? After all, once upon a time browsers didn’t support PDF at all today all browsers include some degree of native support for PDF. The difference between what the PDF provides and the capabilities of viewing software is important to bear in mind. That’s a choice made by browser implementers, not a fact about PDF. You don't often get email from Learn why this is important Very useful information and clearly presented. Subject: Re: Re: SC 1.4.10 Reflow and PDFs On Dec 1, 2023, at 10:16, Steve Green > wrote:ĭuff, are you saying that PDFs automatically pass the Reflow success criterion on the basis that PDF viewers could reflow the content, even if they currently don’t? Sidenote: this issue reflects a more general problem with applying extant WCAG criteria to technologies beyond those for which they were designed (HTML/CSS/JS)… but that’s a digression from your question. On the above basis it may be claimed that since content in PDF can be reflowed the format, in itself, therefore “automatically” passes the criterion… but I fully acknowledge that this claim is subject to accessibility support. Rather, the question is subject to what is “accessibility supported” at a given point in time. I start with the fact that nothing about PDF excludes reflow, and indeed, that for >20 years PDF has included features (tagged PDF) specifically intended to enable semantically-correct reflow.Īn example of a file format that does exclude reflow would be a image format (JPEG, PNG, whatever) representing, for example, a scanned (or output) page-image.Īccordingly, I’m saying that PDF does not automatically fail the Reflow success criterion. I am distinguishing between the format and implementations thereof. Now there are numerous PDF readers that don’t support reflow, I am less sure. When Adobe Reader was pretty much the only PDF reader, I think it would have been perfectly reasonable to say that reflow was accessibility supported. Is this sufficient to claim that the reflow success criterion is met in an accessibility supported manner? WCAG ducks this question completely. Once you have fixed a PDF so it reflows nicely in Adobe Reader, there is a new question. If anyone knows how either of these issues can be fixed in Acrobat, I would be very interested to hear. There are workarounds for most, but we sometimes encounter paragraphs that are centred or right-justified for no apparent reason.Īlso, paragraphs sometimes overlay each other vertically, and my experience has been that this cannot be fixed in Acrobat – it can only be fixed in the source document. With a bit of effort it is possible to get PDFs to display very well in Adobe Reader’s Reflow mode, but there are a number of gotchas. Display the image in Reflow mode and also provide the text alternative as described above. It will then be visible in Reflow mode.ģ. Provide the text alternative by some means such as hiding it behind the image in the normal view. When the page is zoomed, the images never exceed the page width, so they do not cause a horizontal scrollbar.Īlternate Text is not displayed in Reflow mode, so if an image is not decorative you have at least three options:Ģ. Whether you want them to be displayed in Reflow mode will depend on the context. To return to Mark’s original question, images are displayed in Adobe Reader’s Reflow mode as long as they have a bounding box and were not marked as decorative in the source document. Thanks Duff, that is indeed very helpful. RE: SC 1.4.10 Reflow and PDFs from Steve Green on from October to December 2023)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |