You have converted your document into a PDF. It is tagged, yet you still need to know if it is accessible and compliant.<\/p>\n\n\n\n
You *could* test the PDF with a screen reader. However, that may not be a practical testing method if the document is very long or if you do not know how to use a screen reader.<\/p>\n\n\n\n
Just because a document reads one way with one screen reader does not mean it will read correctly with others. The only way to know for sure is to test it against accessibility standards.<\/p>\n\n\n\n
Many people wrongly believe that the Acrobat Check tests against WCAG 2.0. It does not. The PAC-3 checker says it tests against PDF\/UA. However, both checkers fall short in testing things like color use, contrast, accurate alternative text on images and links, the proper use of headings and reading order, plus the accuracy of tooltips.<\/p>\n\n\n\n
CommonLook PDF Validator beats the competition in six key areas:<\/p>\n\n\n\n
The Federal Government took a while to update the Section 508 standard and make it WCAG 2.0 AA. Many organizations, state and local governments\u2019 \u201crules\u201d require websites and documents \u201ccomply with WCAG 2.0AA or a subsequent version<\/em>.\u201d This proactive approach ensures that, as standards change, organizations keep up-to-date. To that end, Allyant is staying current. We make sure that, as standards and requirements are updated, these changes are implemented in our software; a claim neither Adobe Acrobat nor the makers of PAC-3 can make.<\/p>\n\n\n\n WCAG 2.1 AA support complements the robust features that make PDF Validator great \u2013 including its accessibility, ease of use, accuracy and reporting depth. If you haven\u2019t checked out the CommonLook PDF Validator yet, don\u2019t you think it\u2019s time?<\/p>\n\n\n\n