{"id":772,"date":"2017-11-29T13:15:52","date_gmt":"2017-11-29T18:15:52","guid":{"rendered":"https:\/\/blogs.library.unt.edu\/digital-humanities\/?p=772"},"modified":"2017-11-22T13:22:09","modified_gmt":"2017-11-22T18:22:09","slug":"creating-and-maintaining-accessibility-pdfs-part-2","status":"publish","type":"post","link":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/2017\/11\/29\/creating-and-maintaining-accessibility-pdfs-part-2\/","title":{"rendered":"Creating and Maintaining Accessibility: PDFs (Part 2)"},"content":{"rendered":"<span style=\"font-size: 12pt;\">\u00a0 \u00a0 \u00a0 This is the second half of the blog posts on Accessible PDFs. Part one covered why we should strive to make PDFs accessible, where to purchase Adobe Acrobat Pro DC, and how to make Accessible PDFs. This post continues with that creation process, but looks at Forms and interactive PDFs. It also discusses the Repair Workflow feature, and Accessibility Checker, and hits a few more characteristics to keep in mind when creating accessible PDFs.<\/span>\r\n\r\n<span style=\"font-size: 12pt;\">Let&#8217;s jump right back into it.\u00a0<\/span>\r\n<h2><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><strong>Forms and Interactivity<\/strong><\/span><\/h2>\r\n<span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 The last post ended with a discussion about Document Tags and proper reading order. These are especially important if you are creating a form, and\/or wish for the document to allow interaction. Meaning that people who access the form or document can fill out parts.<\/span>\r\n<ol>\r\n \t<li><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><strong>Labeled form fields with accessible messages and no timing<\/strong>; to be <a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/creating-accessible-forms.html\">accessible form fields<\/a> must allow a value to be input into them; this means the form field is interactive. There should also be a defined logical tab order to allow for easy navigation.\u00a0<\/span><span style=\"font-family: helvetica, arial, sans-serif;\">The simplest way to do forms is to leverage the application. Under Tools is a button that says Prepare Form. This is a wizard that will help you create an interactive and accessible form. It will even work with existing documents from PDF, Word, or Excel. You need to verify that the wizard correctly detected any existing data as fields with the proper labeling.\u00a0<\/span><\/li>\r\n \t<li><span style=\"font-family: helvetica, arial, sans-serif;\"><strong>Hyperlinks and Navigational Aids<\/strong>;\u00a0navigational aids includes links, bookmarks, headings, table of contents, and preset tab orders. Bookmarks are useful and should be added; it&#8217;s super easy and handy to create these from the document headings.\u00a0<\/span><\/li>\r\n<\/ol>\r\n<!--more-->\r\n<h2><span style=\"font-size: 12pt;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/acrobat-pro-dc-pdf-accessibility-repair-workflow.html\"><span style=\"font-family: helvetica, arial, sans-serif;\"><strong>Repair Workflow<\/strong><\/span><\/a><\/span><\/h2>\r\n<span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">For existing PDF files using this wizard is easy:<\/span>\r\n<ol>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/pdf-repair-examine.html\">Examine the PDF document<\/a>\r\n<\/span><\/li>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/pdf-repair-add-document-properties.html\">Add document properties and interactive features<\/a>\u00a0this takes care of the navigational aids and such.\r\n<\/span><\/li>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/acrobat-pro-dc-pdf-accessibility-repair-workflow.html\">Identify scanned text and repair<\/a>, runs Optical Character Recognition (OCR).<\/span><\/li>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/pdf-repair-add-form-fields.html\">Add form fields and buttons with labels and accessible names<\/a>\r\n<\/span><\/li>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/pdf-repair-set-document-language.html\">Set the document\u2019s language<\/a>.\r\n<\/span><\/li>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/pdf-repair-add-tags.html\">Add tags to the PDF file<\/a>\u00a0if it has not been tagged.\r\n<\/span><\/li>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/pdf-repair-repair-tags.html\">Determine if the PDF file has been properly tagged<\/a>. Verify tagged elements are properly sequenced and applied.<\/span><\/li>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/pdf-repair-add-alternative-text.html\">Add Alternative Text<\/a>.\u00a0<\/span><\/li>\r\n \t<li><span class=\"text-light\" style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><a href=\"http:\/\/www.adobe.com\/accessibility\/products\/acrobat\/pdf-repair-use-accessibility-checker.html\">Check the document with the Acrobat Accessibility Checker<\/a>.\u00a0<\/span><\/li>\r\n<\/ol>\r\n<h2><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\"><strong>Accessibility Checker<\/strong><\/span><\/h2>\r\n<span style=\"font-family: helvetica, arial, sans-serif; font-size: 12pt;\">\u00a0 \u00a0 This makes sure that the document complies with Adobe&#8217;s interpretation of accessibility guidelines (<span style=\"text-decoration: underline;\"><strong>NOTE<\/strong><\/span>: It does <span style=\"text-decoration: underline;\"><strong>not<\/strong><\/span> check against all possible accessibility criteria), and is the last thing you run to complete your document. Also check:<\/span>\r\n<ol>\r\n \t<li><span style=\"font-family: helvetica, arial, sans-serif;\">Use Reflow view to quickly check reading order and zoom readability.<\/span><\/li>\r\n \t<li><span style=\"font-family: helvetica, arial, sans-serif;\">Use the Read Out Loud to experience the document as it will be heard by readers<\/span><\/li>\r\n \t<li><span style=\"font-family: helvetica, arial, sans-serif;\">Save the document as accessible text and then read the saved text file in a word-processing application<\/span><\/li>\r\n<\/ol>\r\n&nbsp;\r\n\r\n<span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">There are additional characteristics of accessible documents including:<\/span>\r\n<ul>\r\n \t<li><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">Don&#8217;t rely on color or sensory characteristics alone to convey meaning, this can cause problems for those with color blindness, low-vision, or are completely blind.<\/span><\/li>\r\n \t<li><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">Use of color combinations that provides a sufficient degree of contrast; this makes it easier for people who need a gray-scale display, or have trouble differentiating color shades, or have low vision.<\/span><\/li>\r\n \t<li><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">Controls for audio; this allows for use of headphones, or manipulation up, down, or off as the user needs. Make sure if there is audio or video that you also provide captions for videos, and transcripts for audio.<\/span><\/li>\r\n \t<li><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">Use of text instead of images of text; if an image does have text add it to the alternate text of the image.<\/span><\/li>\r\n \t<li><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">No use of flashing or blinking elements; this can trigger photosensitive epilepsy\u00a0<\/span><\/li>\r\n \t<li><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">No focus changes without user initiation; this can throw those low vision and those with cognitive disorders.<\/span><\/li>\r\n \t<li><span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">Consistent navigation and identification of elements; this makes it predicable for those using screen readers and those with cognitive disorders who rely on patterns to navigate and process data.<\/span><\/li>\r\n<\/ul>\r\n&nbsp;\r\n\r\n<span style=\"font-size: 12pt; font-family: helvetica, arial, sans-serif;\">This seems like a lot and the first few times it might take some time, but it is worth it not only for your colleagues who use assistive technologies, but it makes it easier for you in the long run. Once you get a system, know what to include, and what to avoid; it&#8217;ll become automatic to make all of your documents fit the standard, and it will take very little time. Use the tools available in Adobe that have been discussed. They take care of some of the time consuming stuff with just a few clicks.\u00a0<\/span>","protected":false},"excerpt":{"rendered":"\u00a0 \u00a0 \u00a0 This is the second half of the blog posts on Accessible PDFs. Part one covered why we should strive to make PDFs accessible, where to purchase Adobe Acrobat Pro DC, and how to make Accessible PDFs. This post continues with that creation process, but looks at Forms and interactive PDFs. It also&#8230;  <a href=\"https:\/\/blogs.library.unt.edu\/digital-scholarship\/2017\/11\/29\/creating-and-maintaining-accessibility-pdfs-part-2\/\" class=\"more-link\" title=\"Read Creating and Maintaining Accessibility: PDFs (Part 2)\">Read more &raquo;<\/a>","protected":false},"author":77,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"More on creating and maintaining #accessibility for PDFs","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[55,64,9],"tags":[151,5,179,180],"class_list":["post-772","post","type-post","status-publish","format-standard","hentry","category-digitization","category-services-resources","category-tools-and-toys","tag-digital-accessibility","tag-how-did-they-make-that","tag-non-html-content","tag-pdf"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8keRV-cs","_links":{"self":[{"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/posts\/772","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/users\/77"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/comments?post=772"}],"version-history":[{"count":4,"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/posts\/772\/revisions"}],"predecessor-version":[{"id":787,"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/posts\/772\/revisions\/787"}],"wp:attachment":[{"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/media?parent=772"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/categories?post=772"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.library.unt.edu\/digital-scholarship\/wp-json\/wp\/v2\/tags?post=772"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}