Open rnacken opened 3 years ago
Natural language can be set like this:
<Document language="fi">
@siren
I don't know about that - from what I can tell in the source code, language
does not seem to be a valid prop for Document:
Adding it also does not seem to change anything for the validation tools.
Is your feature request related to a problem? Please describe. I want PDFs that will pass an WCAG 2.0 a11y test (see https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/pdf.html)
When I try to validate the accessibility of a generated PDF with a tool like PAC 3 (https://www.access-for-all.ch/ch/pdf-werkstatt/pdf-accessibility-checker-pac.html), or http://checkers.eiii.eu/en/pdfcheck/ some issues come up that can nnot be taken care of with the current set of options provided by the @react-pdf API:
Specifically what seems to be missing is:
Describe the solution you'd like
Documents
:Natural language
Text
component, the option ofDisplayDocTitle
Furthermore, these other issues popped up while validating with PAC 3:
Link
can not have an alternative descriptiontagged
, but this will probably mean a larger overhaul of components to control how you can navigate through the document with tool-assistance. Just marking the doc as 'tagged' will not be enoughDescribe alternatives you've considered Currently, I believe a valid alternative to a11y-validated PDFs is to provide a link as the very first focusable element in the PDF that will link back to a webpage that does contain all the a11y features.
Additional context