![]() ![]() The Micrososft recommendation is great but In my opinion is too technical and highly advanced for the average computer user. Image below show the Accessibility Checker full report with all passed results: The headings were exported and tagged as searchable text, not images. ![]() If you notice my slide above it exported to PDF correctly. In the slide below I'm using Header 1 in my text document: I saved as PDF from Word, used the PDF Maker Add-in to convert the document to PDF, opened the MS Word (.docx) file directly in Adobe Acrobat, and also tried to manually import the file to PDF from Acrobat. In none of these procedures the final PDFs showed the MS Word heading as an image in my resulting PDFs. ![]() I recreated the same scenario like yours and I don't have this issues though. I do apologize for not getting back to you on this in a timely manner. Can you explain a little more fully what I need to do? Thanks!ĭon't forget to mark your solution as correct so that other community users who experience this issue can find it quickly. But none of the options under PDF Fixups seem to have anything to do with getting my headings to be text instead of images. I managed to select Preflight and, in the list of profiles, to find PDF Fixups. I was completely unfamiliar with the Print Production tools. However, Heading 1 through Heading 5 still produce the same accessibility error about missing alt text (because Acrobat still calls them images in the Reading Order pane and the Tags pane). ![]() In particular, the Reading Order tool shows pages broken into bite-sized pieces instead of giant chunks, making it much easier to tweak reading order as needed. Opening the Word document in Acrobat seems somewhat better than using Word's tools. Using Print to PDF was worse: the resulting file has no tags and therefore no structure at all. Oddly enough, both of these have the heading numbers and the heading text in the Bookmarks pane, but on the page they are still tagged as images and still produce the same errors for missing alt text. That file looks to be the same as the one created by exporting. Then, as you suggested, I used File > Save as.PDF in Word. I originally used File > Export > Create a PDF/XPS Document in Word to generate the PDF. Just remember to save a copy of the original work and performs these fixups on a copy that you can continue to test and practice with. Select "Pre-flight" -> PDF Fixus-> "Analyze and Fix".īe watchful of certain additional settings that are also customizable with the Pre-flight options and the Print production tool. So your next step should be to use the Print Production tool. You already spotted some failed evaluations in the Full Report. If this still is an issue, then use the Accessibility checker in Acrobat. If that was also an issue, just open the MS Word file directly in Acrobat and let Acrobat handle the optimization and conversion to PDF automatically (I believe this involves the Distiller part ). In addition, you need to identify what steps were used in your export workflow.įor example, If using the PDF Maker add-in in MS Office to convert to PDF caused the issue try Save As PDF from Word. You'll never go wrong with Arial, for example. You should run the Accessibility Checker in MS Word first to spot discrepancies and change Font type and encoding as necessary. Both MS Office and Adobe Acrobat have Accessibility Checkers. Verify the workflow that was used during export. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |