Re: Embedded PDFs

The other thing which springs to mind is not so much technical but the
question "Why are you providing content in PDF to begin with?"

Generally the answer to that is something like, the PDF file is a brochure,
or a product manual or something which people might want to refer to or
keep, in which case, a link to it also makes sense - users who want to
quickly view it can click on it and it will open in their browser, or users
who need accessibility, or who want to save it, can download it.

If the content is intended to be viewed online as part of the experience of
browsing that web page (eg a story on a news website, or a basic overview
of a product) - then having it as part of the regular page itself might be
a better option - it flows more smoothly with the page, it's
probably quickly to load, it's easier to search or find (If I do a web
search for a phrase which is only in a PDF on a website, I'm not sure it
will be found, if that phrase isn't also in the text of the site itself).

Regards

Quentin.

On Fri, Jan 29, 2021 at 2:24 AM Jonathan Avila <jon.avila@levelaccess.com>
wrote:

> Chrome has a built in PDF extension that seems to do a decent job at
> providing HTML semantics for tagged PDF content that is embedded - although
> some things such as form filling are not available.   I generally download
> the document and if not a form may also convert to Word depending on how
> often I read the document, etc.
>
> Jonathan
>
> -----Original Message-----
> From: Léonie Watson <lwatson@tetralogical.com>
> Sent: Wednesday, January 27, 2021 11:50 PM
> To: Hayk Mikayelyan <HMikayelyan@benchmarkeducation.com>; W3C WAI ig <
> w3c-wai-ig@w3.org>
> Subject: Re: Embedded PDFs
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> To the best of my knowledge an embedded PDF will lose its structure and
> semantic information, no matter how accessible it is to begin with, and no
> matter which tool is used to present it. I would suggest providing a link
> to download the PDF - as a screen reader user myself, it is always my
> preferred option for reading PDF available from websites.
>
> Léonie.
> On 27/01/2021 23:21, Hayk Mikayelyan wrote:
> > Hi all,
> >
> > I have accessible PDFs that are properly tagged and embedded in HTML
> > using PDFjs library as an iframe. According to the standard /content
> > inside the iframe needs to be accessible/. However, PDFjs doesn't
> > support tagged documents and semantics, even though it's being widely
> used.
> >
> > I am wondering what's your experience on providing fully accessible
> > navigation with embedded PDFs?
> >
> > Having a link to download the original document, would be sufficient?
> > Or any other libraries that you would recommend?
> >
> > Thank you very much,
> >
> > Hayk
> >
> > --
> >
> > Hayk Mikayelyan
> >
> > Digital Accessibility Analyst
> >
> > Benchmark Education Company
> >
> > 145 Huguenot Street
> >
> > New Rochelle, NY 10801
> >
>
> --
> Director @TetraLogical
> https://tetralogical.com/
>
>
>

-- 
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>