We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
VeraPDF now supports PDF/UA verification:
~/verapdf/verapdf --format xml --flavour ua1 /tmp/test.pdf > /tmp/out.xml
We should fix the problems that it finds with our PDFs, I suspect that this will also help with the problems that Adobe finds.
This means at least:
The text was updated successfully, but these errors were encountered:
On alt text: https://stackoverflow.com/questions/34036200/add-alternative-text-for-an-image-in-tagged-pdf-pdf-ua-using-itext
The PDF spec chapter 10.6 and 10.7 are relevant: https://ghostscript.com/~robin/pdf_reference17.pdf
Sorry, something went wrong.
The natural language for text blocks could be determined from the hOCR lang attributes, perhaps
https://blog.adobe.com/en/publish/2017/07/25/accessible-pdfs-in-acrobat-dc-tagging-content-as-an-artifact.html https://www.uottawa.ca/respect/sites/www.uottawa.ca.respect/files/fss-fixing-accessibility-errors-in-pdfs.pdf
No branches or pull requests
VeraPDF now supports PDF/UA verification:
We should fix the problems that it finds with our PDFs, I suspect that this will also help with the problems that Adobe finds.
This means at least:
The text was updated successfully, but these errors were encountered: