Basic PDF Accessibility Remediation Demonstration How to Remediate a PDF for Accessibility This video is a demonstration of basic PDF remediation techniques using Adobe Acrobat Pro. The methods in the video address some of the most common fixes needed to make a PDF converted from Microsoft Word accessible. This includes: How to access document properties, and which fields you should fill out. How to run the accessibility checker and why it is always necessary to check the checker’s results. The difference between tag structure and logical reading order. How to create new sections in a PDF. How to move and change tags. Speaker Emily Lapayowker, Assistant Director, Web Content, ASTHO Transcript - Video - Basic PDF Remediation Demonstration Adobe Remediation Cheat Sheet This section serves as a quick reference for the skills included in the demonstration. Note that both the demonstration and this resource use a mouse to navigate Adobe Acrobat Pro. The processes will be different for those using keyboard navigation. Document Properties Menu Document Properties (toward the bottom of the Menu) Description Tab: Title Author (optional) Subject & Keywords – These fields make it easier for screen reader users to search for and identify your document. Advanced Tab: Language (in the Reading Options section) - Make sure the language selected matches the language in which your document is written. This is how screen readers know what language to use. Save changes by selecting the OK button on the Document Properties dialog box. Accessibility Checker The Adobe Acrobat Pro version used in this demonstration is 2026.001.21529. Other versions may have a different layout, but the functionality for all recent versions should be roughly the same. Click on All Tools in the header menu. From the All Tools menu pane, choose “Prepare for Accessibility.” Note that it may be necessary to select “View More” on the menu pane if Prepare for Accessibility is not immediately visible. In the Prepare for Accessibility menu, choose “Check for Accessibility.” A dialog box of Accessibility Checker Options will open. Set the desired parameters and click the “Start Checking” button. An Accessibility Checker pane will appear on the opposite side of the window. It will catalog all of the accessibility issues it detects. Open each item to get more information. Some items must be manually approved. These include Logical Reading Order and Color Contrast. The checker cannot check these for you. To manually pass something, right-click on the item and choose “Pass” from the context menu (i.e., the right-click menu). It is vital to check the checker. All checkers start with the assumption that the document or page in question has been created already using best practices and cannot check some elements as thoroughly as a human can. They are a great starting place, but should not be considered the final word. Tags Tags are the structure of a PDF. They should be the first stop when remediating a document. To open the tags, check the far side of the Accessibility Checker pane. There will be a button with an icon shaped like a gift tag. Click on the icon and the Accessibility Tags will replace the checker results in the pane. All tags should be listed under a top-level Tags item with the PDF icon next to it. Under that will be a Document tag — in almost every instance, the rest of a PDF’s tags will live under the Document tag as well. Tips Clicking on a tag in the structure will highlight the corresponding section in the document. The relevant area will be enclosed in a purple box. Make sure the document structure is correct. This means: Headings are used in order, none are skipped. In almost every case, there will be only one H1 per PDF. H2s should be used as section headings, H3s as subsections, and so on, down to H6. Empty tags can and should be deleted. Right-click on an empty tag and select Delete Tag from the context menu. The context menu has an option to Delete Empty Tags. This is faster, but it is important to check the results. Creating New Tags in the Tags Pane All page content should have a corresponding tag. If a tag is missing, create a new one. Click on a tag near where the new one should go. Click the three dots in the upper right corner of the Tags pane. Select “New Tag” from the context menu. Set the correct tag type by using the dropdown field. In the demonstration video, it is Section. The empty Sect tag will appear in the Tags pane. If it is not in the right place, click on the tag and drag it to the correct location. Add content to the new tag by clicking on the relevant content and dragging it into the new tag. If this is done correctly, the content will appear under and slightly to the right of the new tag (much like a subitem in a list). Nested Tags: Lists Lists are an example of when to use nested tags. The top-level tag in a list should be List, which shows up in the tag order as an L. Under that, each list item should be labeled LI. Within each LI should be two sub-tags: Lbl (or label — a bullet or a number) and LBody, which will contain the text for that list item. Create new tags, change tag type, and/or drag-and-drop content to correct any tagging errors. Nested Tags: Tables Tables are another common type of nested tag. When evaluating tables: Make sure everything is nested under a Table tag. The top row of content should always be nested under a heading tag (THead). Though the sub-tag for the row will be a normal TR, the individual header cells in the row should be tagged as TH. The rest of the table content should be nested under a TBody tag. These will be split up by row (TR). Individual cells should be tagged as TD. Note that if the first column should also be treated as a heading, the tags will still be nested under TBody and inside a TR tag, but the first cell in the row will be a TH. Only use tables for data, not for styling. Try to avoid empty and merged cells. Screen readers go through tables top-to-bottom, left-to-right, one cell at a time. Changing Tag Types Incorrectly categorized tags can be changed (e.g., the title is tagged as a regular paragraph when it should be an H1). Right-click on the existing tag and choose Properties from the context menu to open the Object Properties dialog box. Use the dropdown menu in the Type field to select the correct tag type. Note that tag types are listed alphabetically. Select the “Close” button to save the changes. Reading Order Reading order should be adjusted after the Tags. Typically, it will mirror what you see in the Tag pane, but not always. As the name implies, it is the order in which a screen reader will read the document. To access the Reading Order pane, look at the far end of the Tags pane and there should be an icon that looks a bit like a Z — that is the Reading Order button. Click on it and Reading Order will replace the Tags. The Reading Order content is divided up by page, which makes it easier to stay on track. Removing Items from the Reading Order In the demonstration example, there are three decorative lines inserted in the content to help visually break up the content. Each is marked as a Figure and each generated a flag from the accessibility checker because there was no associated alt text. No alt text is needed for these lines because they are decorative (meaning they do not give the reader any additional information). The best way to remove them from the reading order is to mark them as “background/artifact.” Right-click the decorative item in the Reading Order pane. Choose “tag as background/artifact” from the context menu. The item will disappear from the reading order, but the decorative line will remain visible on the page. Note that sometimes this does not work and you end up with empty or erroneous items in the reading order. Known Conversion Errors It is possible to create a completely accessible document in Microsoft Word and still have errors when it is converted to a PDF. Some of these problem areas may be the result of known conversion errors, such as: Images (or figures) moving to the bottom of the reading order, regardless of where they are placed on the page. Empty P tags where the author has used the Enter/Return key to move to a new line. Unfortunately, these are not preventable issues. Any fixes have to be done by Adobe, so it is important to watch out for them when remediating a document. article yes