We want to build accessibility in PDF documents embedded in a website. In the View Document mode within our website, the screen reader such as NVDA is not able to read the contents of the document.
Please suggest what do we need to do in order for the screen reader to read the contents of the PDF doc embedded within the Website and also identify any editable fields which may need to be filled in by the end user.
Copy link to clipboard
The contents of the PDF in an embedded view are currently not available to screen readers but I'll forward this post to our product team as a feature request.
Thank you for the prompt response Joel. This is quite helpful to know.
Please do, there are many websites for which ADA compliancy is an absolute must. Thank you!!! 🙂
Really should be a third option for these questions. The problem isn't solved. It should be listed as an open issue. ADA compliance is more important than anything else you are working on. Get this done.
OK I did more research. It turns out that indeed ACCESSIBILTY IS AVAILABLE IN THE PDF EMBED!!!!!!!!!!
It turns out that it is a hidden feature that is almost accessible to screen readers after navigating through a bunch of controls!!!!!!!!
This feature should be able to be enabled programatically or better yet turned on by default via the code if desired.
<input class="Accessibility__elementInvisible___3eGvf __web-inspector-hide-shortcut__" type="checkbox" id="accscreen" aria-disabled="false" value="Enable Accessibility for screen reader.">
but there is no code to make the checkbox visible.
And once again I have to insist. WEBSITE ACCESSIBILITY IS THE LAW OF THE LAND
That a feature is already available, but remains somewhat hidden or hard to get to is frankly ridiculous Especially when all we need is the code to set the the default or make a check box visible.
Also for accessibility there needs to be an attribute to name the iframe that is generated by the script.
Hi Lawrence, we are working on bringing accessibility to PDF Embed. While you were able to see some aspects of previous work by digging into the code (I do that too 🙂 - we have not made it generally available because we want to ensure that everyone gets the expected performance and reading experience. We *absolutely* recognize how important this is. We will update our docs as soon as possible.
THANKS VERY MUCH FOR THIS RESPONSE!
Just to let you know that the ability isn't that hidden, I recognized it was there because when using a screen reader it was a surprise option when I was tabbing through. I imagine many people didn't find it because when tabbing through there are a lot of buttons that have no names, (something else that should be addressed) so they got lost if they weren't as persitent as I. The other thing I noticed is that pagination doesn't work. No matter what page one is on it starts reading from the top.
My dream though for maximum accessibility would be a pdf reader that rendered compliant html on the fly. Now That would be a game changer! 🙂