-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PDF documents are not accessible #62
Comments
@khays9 can you explain this in more detail please. We've reviewed the pdfs and made sure they were formatted correctly, but if we missed anything, would be good to pinpoint exactly what it is that makes it inaccessible. Thank you. |
You can run an accessibility check on the pdf via Acrobat DC. Here is a report and the common mistakes found on the 'set' pdf. AcrobatAccessibilityReport.pdf How to run check in acrobat https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html |
My apologies for not being specific. One example, is that the en-UK version of the autistic-spectrum.pdf poster has multiple issues, including lack of tagged content and alternate text for figures. Other files are tagged accessibly but have issues, such as the en-UK version of the accessibility-posters-set.pdf file, where headings are not nested appropriately (as csogi posted above). It would be good to run the Acrobat accessibility report for all files and correct any issues found. Issues like no title or improper nesting for headings are relatively minor compared to lack of accessible tagging or alternate text. Reading order is another issue that usually requires a manual check. Adobe's documentation on making pdfs accessible is very good. For a more concise tutorial, you can look at the IT Accessibility at Illinois PDF section . |
I noticed the reading order was off on several pages of the English version of the posters and the links in the footer were not properly tagged. Also the Creative Commons language appears to be an image that's embedded in the page somehow so it can't be tagged. |
@jdblundell thanks for getting in touch in regards to this and making us aware of these issues. Could I ask which screen reader and device you used to check the issues you have mentioned? |
thanks. It’s actually been a little while since I submitted the issue so I’m not 100% but I typically test with JAWS or review the tags in the PDF.
Jonathan Blundell@jdblundell
On Tue, Jun 11, 2019 at 9:11 AM -0500, "Sue Spevack" <[email protected]> wrote:
@jdblundell thanks for getting in touch in regards to this and making us aware of these issues. Could I ask which screen reader and device you used to check the issues you have mentioned?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
The PDF documents are not accessible (though you do have a text-only alternative). Consider tagging the PDFs for accessibility.
The text was updated successfully, but these errors were encountered: