Currently publishing a document inventory is only available as an addon to an HTML accessibility scan. Most of the time when I test PDFs the task is exclusive to PDFs - I only want the PDF results and not the HTML results. The HTML portion of the accessibility scan is a waste then. Would it be faster/less overhead to only scan for PDFs and not run all of the web algorithms to test the HTML? Right now we have a button to include the document inventory. It may be useful to also have a button we can deselect to not include HTML content in the scan.
Jordan Wilson
Hi Jordan,
Would you mind giving me a little more context on how the PDF only reports your working on are created, and why there is web testing if your only doing PDF testing?
Attachments Open full size