WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: print to PDF functionality and accessibility

for

From: Jerra Strong
Date: Oct 7, 2021 12:33PM


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> > 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>
> — — —
> PubCom: Technologists for Accessible Design + Publishing
> consulting • training • development • design • sec. 508 services
> Upcoming classes at www.PubCom.com/classes
> — — —
> Latest blog-newsletter – Simple Guide to Writing Alt-Text
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Jerra Strong
> Sent: Thursday, October 7, 2021 1:39 PM
> To: WebAIM Discussion List < <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> >
> 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
> > > >
> > > at http://webaim.org/discussion/archives
> >
> > > > >