Content in PDF format is still viral among many users on the web. However, PDFs are notoriously known for not being accessible to screen readers and other assistive technologies. There are still many common errors that people make during the process of PDF Remediation. This can be frustrating for both content creators as well as consumers who are trying to access and use this content. The good news is that these errors can be easily avoided if you know what they are!
Common PDF Remediation Errors to Avoid
While it’s true that PDF remediation is a necessary part of creating accessible PDFs, it can also be quite tricky. There are several errors that can be common when remediating a PDF. The following is a list of the most common errors:
Error 1: PDFs Should be Read with a Screen Reader
One of the most common errors that we see is not making sure that your document can be read with a screen reader. People with disabilities use screen readers because they allow them to read and navigate documents. There are many different types of screen readers, but they all use software that converts text into speech or braille.
There are two main types of screen readers: auditory (those that read aloud) and non-auditory (those without sound). The most popular auditory ones include JAWS, NVDA, and VoiceOver; while NVDA is used mainly on PCs and Macs, JAWS and VoiceOver are more commonly used on Windows computers.
Non-auditory screen readers rely solely on key presses or clicks to navigate through documents instead of relying on audio cues from the computer’s speakers. The most common non-auditory screen reader is ZoomText, which works with Windows computers only.
Error 2: Headings Need to be Used in a Structured Manner and Not Simply for Formatting
When you’re using headings for organization and navigation, it’s important to make sure that the order of your headings is logical. You should be able to see a path from one heading to another, with no significant gaps in between. This will help users understand how this document is structured so they can find what they need quickly.
Headings are also used for formatting; however, you can still use them for both purposes at once—just ensure all of your headings are consistent and don’t contradict each other! If you have some that are formatted differently than others, such as changing their font size or color scheme, then they may not be as accessible because users might not know which ones are more important than others.
Error 3: A ‘Read Aloud’ Feature is Required When Reading the Entire Document is Time-consuming
The Read-Aloud feature is not a substitute for using a screen reader. The Read-Aloud feature reads aloud the text on the page, but it cannot perform any actions within Adobe Acrobat. For example, you can’t use this feature to navigate through fields in Forms or to fill out forms by listening to instructions read aloud.
This error occurs if you don’t allow users with disabilities to access your PDF file by either:
- Utilizing the Read Aloud feature
- Performing their own navigation of your document’s features and content
Error 4: Tables Need to Be Structured in an Orderly Manner
Tables should be structured in an orderly manner, so the reader can easily read and navigate them. Tables should also be easy to edit, print, and search. For example, it’s a good idea to use columns for headers; these are useful when finding specific information quickly.
Here’s an example of a table that has been structured correctly:
- First Name * Last Name
Error 5: All Images Need to Contain Descriptive Alternative Text (alt-text)
Alt-text is an important part of accessibility, and it should be descriptive and not just a filename. We recommend that all alt texts be no longer than a few words, so as not to make your document more difficult to read.
If you’re including an image in one language but using another for your document as a whole, then make sure that the alt text matches up with the image file name because you don’t want people getting confused! If you’re unsure what language characters are used within an image file name, check out the guides on UTF-8 to learn more.
If you have multiple images on one page and each has its own descriptive alt text field (which we recommend), then make sure none of them overlap or repeat themselves by accident. This can create problems for screen readers and sighted users alike!
Also, note that any links within your document should never be used as alternate text content either. They should always point elsewhere outside of your PDF files so you can access them independently without requiring additional software installations first before opening up anything else inside them.
Error 6: Navigation Must be Consistent and Logical Throughout the Document
In our experience, one of the most common mistakes we observe in remediated documents is a lack of consistency in navigation. By this, we mean that the document’s links are not consistent with each other and do not provide users with a clear path through the document.
Oftentimes, this happens when a PDF has been created using multiple tools or software packages: some links will look like hyperlinks while others are barely visible text; some links may be underlined while others are in color; some will open up new pages while others take you back to where you were before.
While inconsistency makes it harder for screen reader users to get around your document, it can also confuse sighted people who aren’t familiar with how your company’s various platforms work. This means that inconsistencies can cause confusion even if they don’t affect accessibility at all!
To avoid this issue altogether, make sure that every link has clear visual treatment (like underlining) and that all pages have unique titles, so readers know where they are when navigating away from an active page or page section.
Error 7: Make Sure Your PDF has a Language Specified in the Header of the Document
The document must have a language specified in the header of the document. This is important for accessibility (so that screen readers can read it) and also vital for search engines because it helps them to understand what your PDF is about. Once you’ve determined what language code you need, just add it to your header.
Conclusion
Remember, PDFs should be accessible to all users. As long as you follow the guidelines above and keep accessibility in mind, your PDF will be ready to share with all of your intended readers!
