You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 0.0.1-RC18 openhtmltopdf has added accessibilty features such as titles, language and description meta data as well as tagged content. This brings it into compliance with the PDF/UA, Section 508 and WCAG 2 accessibility standards.
These added features would be greatly appreciated so we can produce accessible documents for our users via this service.
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for raising this; you're absolutely right that we should be supporting PDF/UA. We will look into extending the api to support all (current) standards up to and including PDF/UA.
The PDF/UA functionality is now covered in v1.5.0 and extends the current set of document conformance levels to include the PDF/UA format for accessibility. The accessible-test.html test file (src/test/resources) was tested using Adobe Pro with the following outputs to confirm UA.
As of 0.0.1-RC18 openhtmltopdf has added accessibilty features such as titles, language and description meta data as well as tagged content. This brings it into compliance with the PDF/UA, Section 508 and WCAG 2 accessibility standards.
These added features would be greatly appreciated so we can produce accessible documents for our users via this service.
Thanks!
The text was updated successfully, but these errors were encountered: