Wrapping Up
Testing PDF for Accessibility
Once the accessibility features of PDF files are clear, it is time to test the PDF file for accessibility. It is recommended that testing come at the end of the development of the document, because the overall design and structure of the document is a key to its accessibility.
There are several approaches you can use to test a PDF file:
- Have an individual who is blind or has a visual impairment examine the PDF file; an individual with a disability usually has a different approach to interacting with the document than you expected, thus exposing errors.v
- Download a screen reader; trial versions of screen reading technology are available and it provides insight as to how an individual who is blind or has a visual impairment might interpret your document.
- Try unplugging the mouse and navigating the document with only the keyboard. This provides insight as to how a keyboard-only user would navigate the PDF file.
Aside from these ways of testing, you can also use the built-in accessibility checker of Acrobat to test your PDF file. However, this tool does not replace the aforementioned approaches of testing a PDF file, but should be used in conjunction with them
Security Settings of Adobe Acrobat
Authors often want their documents to be readable, but not copied or printed. To prevent PDF files from being copied or printed, Adobe Acrobat offers security settings in 40-bit encryption and 128-bit encryption. When 128-bit encryption is used, the author can prevent the copying of content and still maintain accessibility. However, the decision to use 40-bit encryption and select the option to 'eliminate all copying or extraction' results in disabling accessibility.



