Have you spent hours after hours browsing the structure of your PDF document just to ensure that it is Section 508 compliant?
Did you ever get frustrated because it took you to patch it up longer than writing the original document?
You can save yourself some major time and headache when you get the legwork done in the source document.
Accessibility should be top of mind when considering the list of current and emerging concerns in enterprise content management (ECM). High-volume transactional
output environments (HVTO) in particular are challenged more than ever to provide accessible content to all users.
PDF files are still the primary mechanism to store transactional information in ECM systems. Yet unfortunately, they are almost always inaccessible to a
key subset of users: people with visual impairments using screen readers.
When posting documents on web sites, they have to follow the same accessibility requirements that the site does. For example, when the web site needs to comply with Section 508, PDF documents do too. There are a few things which I find are often overlooked when creating accessible PDF documents, in the following you can read about those and ensure that you address those issues as well.