WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: print to PDF functionality and accessibility

for

From: chagnon@pubcom.com
Date: Oct 7, 2021 3:00PM


Jerra, that's a terrific idea that should be logged at www.Acrobat.UserVoice.com <http://www.Acrobat.UserVoice.com>;



Adobe could design its browser plugins to recognize the tags and DOM of a webpage to create a Print-to-PDF version that retains the accessibility. Nothing preventing any other PDF-creation software from doing this, too, such as FoxIt and CairoGraphics.



When you post at UserVoice, let us know on the list so we can vote for the feature.



— — —

Bevi Chagnon | Designer, Accessibility Technician | <mailto: <EMAIL REMOVED> > <EMAIL REMOVED>

— — —

PubCom: Technologists for Accessible Design + Publishing

consulting • training • development • design • sec. 508 services

Upcoming classes at <http://www.pubcom.com/classes>; www.PubCom.com/classes

— — —

<https://mailchi.mp/e694edcdfadd/class-discount-3266574> Latest blog-newsletter – <https://www.pubcom.com/blog/2020_07-20/alt-text_part-1.shtml> Simple Guide to Writing Alt-Text



From: Jerra Strong < <EMAIL REMOVED> >
Sent: Thursday, October 7, 2021 2:34 PM
To: <EMAIL REMOVED> ; WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] print to PDF functionality and accessibility



Bevi speaks the truth. What if they want to keep a second copy for their reference? Personally, I would like to see a straightforward way to get a tagged pdf from (already tagged and structured) HTML content become the norm.



On Thu, Oct 7, 2021 at 10:47 AM < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> > > wrote:

Seconding this method Jerra S suggests:
" you could have them fill the form online, and then generate an already-filled PDF, which is okay that it's print-only, because they are just going to print it and stick it in an envelope."

PDFs for print are exempt from accessibility requirements.

However, it would be much more beneficial and useful to users if it was digitally accessible as well.

— — —
Bevi Chagnon | Designer, Accessibility Technician | <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
— — —
PubCom: Technologists for Accessible Design + Publishing
consulting • training • development • design • sec. 508 services
Upcoming classes at www.PubCom.com/classes <http://www.PubCom.com/classes>;
— — —
Latest blog-newsletter – Simple Guide to Writing Alt-Text

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> > > On Behalf Of Jerra Strong
Sent: Thursday, October 7, 2021 1:39 PM
To: WebAIM Discussion List < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> > >
Subject: Re: [WebAIM] print to PDF functionality and accessibility

Depends on what you want that end-user to be doing with the PDF.

The "print to PDF" function is pretty much guaranteed to make a print-only PDF with no tags, so you would have to have some separate tool that generates a PDF which is meeting the standards you want, or provide an already-created PDF for download at some link. Or, you could have them fill the form online, and then generate an already-filled PDF, which is okay that it's print-only, because they are just going to print it and stick it in an envelope.

On Thu, Oct 7, 2021 at 10:32 AM Logan Trafford < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> > >
wrote:

> Bit of an odd question perhaps and I'll try to describe the scenario
> as distinctly as possible.
>
> Our developers have created an accessible HTML payment form.
> There are two options
> 1. continue to pay online, which takes the user to a 3rd party payment
> tool.
> 2. select the option to mail in the payment, with the form filled in
> and printed off.
>
> As stated, the HTML form itself is WCAG conformant, BUT if a user
> decides to save (or print) as PDF, is there any way to control the PDF
> that is generated automatically? In other words, currently it is a
> non-accessible PDF that is produced.
> Is there another step in the process that we would need to invoke somehow?
>
> thanks in advance for any thoughts or input.
>
> Logan
> > > archives at http://webaim.org/discussion/archives
> >