E-mail List Archives

Thread: Accessible PDFs from Google Doc/Presentation

for

Number of posts in this thread: 20 (In chronological order)

From: Mickey Williamson
Date: Thu, Jan 07 2016 9:13AM
Subject: Accessible PDFs from Google Doc/Presentation
No previous message | Next message →

Has anyone had success in creating accessible PDFs out of a Google Doc or
Google Presentation? I download the document as a PDF and it opens fine.
But when I attempt to add tags, I get "Bad PDF; error in processing fonts.
<cannot find CMap resource file>" or "Bad PDF; error in processing fonts.
<bad Type0 font>" depending on whether it comes from Docs or Presentation.
My test document I'm using for this has nothing but one word in the Arial
font. A google search has yielded nothing. :-(

Any ideas?

Thanks,
Mickey

From: Kelly Lupo
Date: Thu, Jan 07 2016 9:29AM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

I don't know about the accessibility of doing it this way, but have you
tried "printing" the document to PDF using something like Foxit Reader or
Adobe Reader's printer option?

As an aside, are there better PDF printing options? I haven't looked at
this yet, but I definitely need to implement a better PDF printer program
and PDF converter program (preferably free/low-cost) for our office...

Kelly

On Thu, Jan 7, 2016 at 11:13 AM, Mickey Williamson <
= EMAIL ADDRESS REMOVED = > wrote:

> Has anyone had success in creating accessible PDFs out of a Google Doc or
> Google Presentation? I download the document as a PDF and it opens fine.
> But when I attempt to add tags, I get "Bad PDF; error in processing fonts.
> <cannot find CMap resource file>" or "Bad PDF; error in processing fonts.
> <bad Type0 font>" depending on whether it comes from Docs or Presentation.
> My test document I'm using for this has nothing but one word in the Arial
> font. A google search has yielded nothing. :-(
>
> Any ideas?
>
> Thanks,
> Mickey
> > > > >

From: Duff Johnson
Date: Thu, Jan 07 2016 9:32AM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

> Has anyone had success in creating accessible PDFs out of a Google Doc or
> Google Presentation? I download the document as a PDF and it opens fine.
> But when I attempt to add tags, I get "Bad PDF; error in processing fonts.
> <cannot find CMap resource file>" or "Bad PDF; error in processing fonts.
> <bad Type0 font>" depending on whether it comes from Docs or Presentation.
> My test document I'm using for this has nothing but one word in the Arial
> font. A google search has yielded nothing. :-(
>
> Any ideas?

Google makes crappy PDF files. Sod but true.

Making good-quality PDF files is not a mystery. It’s simply a question of the software developer’s priorities.

Please complain to them about it. It’s the only way to make these things change.

Duff.

From: Chagnon | PubCom.com
Date: Thu, Jan 07 2016 10:34AM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

Printing to the virtual PDF printer that's installed with Acrobat and other Acrobat-clones (File/Print/Acrobat PDF) creates a very different document than other methods, such as an export to PDF utility.

When you select print to PDF, you are encoding the document the same way it gets physically printed on a laser printer; the architectural structure of the document that's "under the hood" is very different from what we need in a accessible or digital PDF. Visual appearance is the same, but not the coding.

So use Print to PDF as a last resort, knowing that you'll need to spend quite a bit of time to remediate it for accessibility. Instead, use the source software's export, save as, or convert to PDF, which triggers a different engine that makes the PDF than the Print to PDF method.

At this time, Adobe's products still reign supreme for PDFs, whether you need a press-quality one for sending to the print shop, or an accessible one for electronic distribution. The PDF format is in the ISO public domain, but no company has matched Adobe's commitment and expertise...regardless of how much money the others spend on advertising to convince the public otherwise.

—Bevi Chagnon

— — —
Bevi Chagnon | www.PubCom.com | = EMAIL ADDRESS REMOVED =
Technologists, Consultants, Trainers, Designers, and Developers
for publishing & communication
| PRINT | WEB | PDF | EPUB | Sec. 508 ACCESSIBILITY |
— — —



-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Kelly Lupo
Sent: Thursday, January 7, 2016 11:29 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation

I don't know about the accessibility of doing it this way, but have you tried "printing" the document to PDF using something like Foxit Reader or Adobe Reader's printer option?

As an aside, are there better PDF printing options? I haven't looked at this yet, but I definitely need to implement a better PDF printer program and PDF converter program (preferably free/low-cost) for our office...

Kelly

On Thu, Jan 7, 2016 at 11:13 AM, Mickey Williamson < = EMAIL ADDRESS REMOVED = > wrote:

> Has anyone had success in creating accessible PDFs out of a Google Doc
> or Google Presentation? I download the document as a PDF and it opens fine.
> But when I attempt to add tags, I get "Bad PDF; error in processing fonts.
> <cannot find CMap resource file>" or "Bad PDF; error in processing fonts.
> <bad Type0 font>" depending on whether it comes from Docs or Presentation.
> My test document I'm using for this has nothing but one word in the
> Arial font. A google search has yielded nothing. :-(
>
> Any ideas?
>
> Thanks,
> Mickey

From: Duff Johnson
Date: Thu, Jan 07 2016 10:45AM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

> At this time, Adobe's products still reign supreme for PDFs, whether you need a press-quality one for sending to the print shop, or an accessible one for electronic distribution.

With respect… not so. There are other products that do as good and in some cases a much better job of creating tagged PDF from MS Word files (for example) than Acrobat in its current incarnation.

Moreover, some of these tools - typically the ones oriented specifically towards accessibility - include far, far better resources than Acrobat provides for ensuring accessibility of PDF documents.

It’s not my role to identify these vendors here.. but they exist, they aren’t hiding and their products are available for sale today.

Duff.

From: Mickey Williamson
Date: Thu, Jan 07 2016 11:12AM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

@Duff - I'd be interesting in knowing which tools those are. Please email
me directly if you don't want to post here.

And back to my original question...I have a Google Presentation document
that I need to make into an accessible PDF. The two methods of turning
that into a PDF (Google's "download as" and print to PDF) both give me a
PDF that will not allow tagging. When I try to add tagging, I get the
errors mentioned in my original post. Redoing the document using a proper
Word-InDesign-PDF workflow is not an option at this point. If I can't
somehow get a taggable PDF of the Google Presentation doc, it's going to
have to go out without tagging. :-( I am currently downloading a trial
version of Powerpoint in hopes of being able to "download as PPTX" and
convert to a taggable PDF from there but I don't have high hopes. Does
anyone have any other suggestions to try or knowledge about how to resolve
the error I'm getting?

Thanks,
Mickey

On Thu, Jan 7, 2016 at 12:45 PM, Duff Johnson < = EMAIL ADDRESS REMOVED = > wrote:

> > At this time, Adobe's products still reign supreme for PDFs, whether you
> need a press-quality one for sending to the print shop, or an accessible
> one for electronic distribution.
>
> With respect… not so. There are other products that do as good and in some
> cases a much better job of creating tagged PDF from MS Word files (for
> example) than Acrobat in its current incarnation.
>
> Moreover, some of these tools - typically the ones oriented specifically
> towards accessibility - include far, far better resources than Acrobat
> provides for ensuring accessibility of PDF documents.
>
> It’s not my role to identify these vendors here.. but they exist, they
> aren’t hiding and their products are available for sale today.
>
> Duff.
> > > > >



--


Michelle Williamson
Drupal Developer
T 678.580.1690 x205 F 770.360.5776
twitter <http://twitter.com/micnap>; • linkedin
<http://www2.mediacurrent.com/l/10072/2012-03-23/3qknq>; • mediacurrent
<http://www2.mediacurrent.com/l/10072/2012-03-23/3qkpd>;

Awarded Best SMB
<https://t.yesware.com/tl/6228584989751eec7f7efd759b5a3987de150a8e/2db8247480f6e405a199c3227c223214/40a213898e1bbb2949c481a66986bb61?ytl=http%3A%2F%2Fwww.mediacurrent.com%2Fblog%2Fdrupal-agency-mediacurrent-awarded-best-overall-smb-salesforce>
by Salesforce.com

From: Duff Johnson
Date: Thu, Jan 07 2016 11:17AM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

> @Duff - I'd be interesting in knowing which tools those are. Please email
> me directly if you don't want to post here.

Only if you promise to complain to Google! :-)

> And back to my original question…

> I am currently downloading a trial
> version of Powerpoint in hopes of being able to "download as PPTX" and
> convert to a taggable PDF from there but I don't have high hopes.

Actually, that is exactly the right way to go (for now).

Duff.

From: Mickey Williamson
Date: Thu, Jan 07 2016 12:35PM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

An FYI that downloading as PPTX and then converting in Powerpoint to PDF
worked. I am now able to tag the PDF. Wow, what a painful, painful
process. Shame on you, Google. Where can I complain that it will actually
make a difference?

On Thu, Jan 7, 2016 at 1:17 PM, Duff Johnson < = EMAIL ADDRESS REMOVED = > wrote:

> > @Duff - I'd be interesting in knowing which tools those are. Please
> email
> > me directly if you don't want to post here.
>
> Only if you promise to complain to Google! :-)
>
> > And back to my original question…
>
> > I am currently downloading a trial
> > version of Powerpoint in hopes of being able to "download as PPTX" and
> > convert to a taggable PDF from there but I don't have high hopes.
>
> Actually, that is exactly the right way to go (for now).
>
> Duff.
> > > > >



--


Michelle Williamson
Drupal Developer
T 678.580.1690 x205 F 770.360.5776
twitter <http://twitter.com/micnap>; • linkedin
<http://www2.mediacurrent.com/l/10072/2012-03-23/3qknq>; • mediacurrent
<http://www2.mediacurrent.com/l/10072/2012-03-23/3qkpd>;

Awarded Best SMB
<https://t.yesware.com/tl/6228584989751eec7f7efd759b5a3987de150a8e/2db8247480f6e405a199c3227c223214/40a213898e1bbb2949c481a66986bb61?ytl=http%3A%2F%2Fwww.mediacurrent.com%2Fblog%2Fdrupal-agency-mediacurrent-awarded-best-overall-smb-salesforce>
by Salesforce.com

From: John E. Brandt
Date: Thu, Jan 07 2016 12:47PM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

We were not able to create an accessible PDF using any of the Google products so at the University I am consulting with, we informed everyone in the university system not to use them. I'm sure everyone paid attention.

The only solution we found was to drop the Google document in to MS-Office on PC and add the appropriate tags as needed and then save as PDF.

I guess it just another one of those things the folks in GoogleLand have not got around to fixing and making accessible.

~j

John E. Brandt
jebswebs.com

= EMAIL ADDRESS REMOVED =
jebswebs.com



-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Mickey Williamson
Sent: Thursday, January 7, 2016 11:13 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] Accessible PDFs from Google Doc/Presentation

Has anyone had success in creating accessible PDFs out of a Google Doc or Google Presentation? I download the document as a PDF and it opens fine.
But when I attempt to add tags, I get "Bad PDF; error in processing fonts.
<cannot find CMap resource file>" or "Bad PDF; error in processing fonts.
<bad Type0 font>" depending on whether it comes from Docs or Presentation.
My test document I'm using for this has nothing but one word in the Arial font. A google search has yielded nothing. :-(

Any ideas?

Thanks,
Mickey

From: Chagnon | PubCom.com
Date: Thu, Jan 07 2016 1:46PM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

With respect, Duff, is it Acrobat that makes lousy files? Or is it the lousy construction of the source Word (or Office) document that's the problem?

We're getting very good accessible PDFs from Word and PPT when the source files are constructed correctly and exported correctly with Acrobat's PDF Maker plug-in. I admit, there are some of the more complex items in Word that fail the conversion, but they are being addressed.

Plus, none of those extra programs make complaint PRESS files for those of us who must communicate both in print and digitally.

—Bevi Chagnon

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Duff Johnson
Sent: Thursday, January 7, 2016 12:46 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation

> At this time, Adobe's products still reign supreme for PDFs, whether you need a press-quality one for sending to the print shop, or an accessible one for electronic distribution.

With respect… not so. There are other products that do as good and in some cases a much better job of creating tagged PDF from MS Word files (for example) than Acrobat in its current incarnation.

Moreover, some of these tools - typically the ones oriented specifically towards accessibility - include far, far better resources than Acrobat provides for ensuring accessibility of PDF documents.

It’s not my role to identify these vendors here.. but they exist, they aren’t hiding and their products are available for sale today.

Duff.

From: Lucy Greco
Date: Thu, Jan 07 2016 1:55PM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

hello:"
sorry i need to chime in here why save as a pdf any way why not save
the docs or slides presentation to html google does a good job of making
that accessable. what reason is there for a pdf of some thing that was
born on the web.

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Thu, Jan 7, 2016 at 12:46 PM, Chagnon | PubCom.com < = EMAIL ADDRESS REMOVED = >
wrote:

> With respect, Duff, is it Acrobat that makes lousy files? Or is it the
> lousy construction of the source Word (or Office) document that's the
> problem?
>
> We're getting very good accessible PDFs from Word and PPT when the source
> files are constructed correctly and exported correctly with Acrobat's PDF
> Maker plug-in. I admit, there are some of the more complex items in Word
> that fail the conversion, but they are being addressed.
>
> Plus, none of those extra programs make complaint PRESS files for those of
> us who must communicate both in print and digitally.
>
> —Bevi Chagnon
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> Behalf Of Duff Johnson
> Sent: Thursday, January 7, 2016 12:46 PM
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>
> > At this time, Adobe's products still reign supreme for PDFs, whether you
> need a press-quality one for sending to the print shop, or an accessible
> one for electronic distribution.
>
> With respect… not so. There are other products that do as good and in some
> cases a much better job of creating tagged PDF from MS Word files (for
> example) than Acrobat in its current incarnation.
>
> Moreover, some of these tools - typically the ones oriented specifically
> towards accessibility - include far, far better resources than Acrobat
> provides for ensuring accessibility of PDF documents.
>
> It’s not my role to identify these vendors here.. but they exist, they
> aren’t hiding and their products are available for sale today.
>
> Duff.
> > > at http://webaim.org/discussion/archives
> >
> > > > >

From: Kelly Lupo
Date: Thu, Jan 07 2016 2:03PM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

I literally just had this conversation about 2 hours ago in my office, but
a lot of the time, people feel that their information is 'secure' because
the PDF file cannot be directly edited by others... That was why they
wanted the documents in that format on the website - no matter how it was
initially created.

(I'm not sure they believed me when I told them I could take one of their
(currently inaccessible) PDFs, or even an image of text, and then make it
into an editable document in a few steps...)

Kelly

On Thu, Jan 7, 2016 at 3:55 PM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:

> hello:"
> sorry i need to chime in here why save as a pdf any way why not save
> the docs or slides presentation to html google does a good job of making
> that accessable. what reason is there for a pdf of some thing that was
> born on the web.
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
> On Thu, Jan 7, 2016 at 12:46 PM, Chagnon | PubCom.com < = EMAIL ADDRESS REMOVED = >
> wrote:
>
> > With respect, Duff, is it Acrobat that makes lousy files? Or is it the
> > lousy construction of the source Word (or Office) document that's the
> > problem?
> >
> > We're getting very good accessible PDFs from Word and PPT when the source
> > files are constructed correctly and exported correctly with Acrobat's PDF
> > Maker plug-in. I admit, there are some of the more complex items in Word
> > that fail the conversion, but they are being addressed.
> >
> > Plus, none of those extra programs make complaint PRESS files for those
> of
> > us who must communicate both in print and digitally.
> >
> > —Bevi Chagnon
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> > Behalf Of Duff Johnson
> > Sent: Thursday, January 7, 2016 12:46 PM
> > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> > Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
> >
> > > At this time, Adobe's products still reign supreme for PDFs, whether
> you
> > need a press-quality one for sending to the print shop, or an accessible
> > one for electronic distribution.
> >
> > With respect… not so. There are other products that do as good and in
> some
> > cases a much better job of creating tagged PDF from MS Word files (for
> > example) than Acrobat in its current incarnation.
> >
> > Moreover, some of these tools - typically the ones oriented specifically
> > towards accessibility - include far, far better resources than Acrobat
> > provides for ensuring accessibility of PDF documents.
> >
> > It’s not my role to identify these vendors here.. but they exist, they
> > aren’t hiding and their products are available for sale today.
> >
> > Duff.
> > > > > > at http://webaim.org/discussion/archives
> > > >
> > > > > > > > > >
> > > > >

From: Kelly Lupo
Date: Thu, Jan 07 2016 2:12PM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

Sorry, to be clear - I'm not stating that anyone here specifically thinks
this (they may or may not), but it's possible that it was mandated by
superiors or other such similar situations. (Such as mine - where we go
from PowerPoint presentation to PDF for the website.)

Kelly

On Thu, Jan 7, 2016 at 4:03 PM, Kelly Lupo < = EMAIL ADDRESS REMOVED = > wrote:

> I literally just had this conversation about 2 hours ago in my office, but
> a lot of the time, people feel that their information is 'secure' because
> the PDF file cannot be directly edited by others... That was why they
> wanted the documents in that format on the website - no matter how it was
> initially created.
>
> (I'm not sure they believed me when I told them I could take one of their
> (currently inaccessible) PDFs, or even an image of text, and then make it
> into an editable document in a few steps...)
>
> Kelly
>
> On Thu, Jan 7, 2016 at 3:55 PM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
>
>> hello:"
>> sorry i need to chime in here why save as a pdf any way why not save
>> the docs or slides presentation to html google does a good job of
>> making
>> that accessable. what reason is there for a pdf of some thing that was
>> born on the web.
>>
>> Lucia Greco
>> Web Accessibility Evangelist
>> IST - Architecture, Platforms, and Integration
>> University of California, Berkeley
>> (510) 289-6008 skype: lucia1-greco
>> http://webaccess.berkeley.edu
>> Follow me on twitter @accessaces
>>
>>
>> On Thu, Jan 7, 2016 at 12:46 PM, Chagnon | PubCom.com < = EMAIL ADDRESS REMOVED =
>> >
>> wrote:
>>
>> > With respect, Duff, is it Acrobat that makes lousy files? Or is it the
>> > lousy construction of the source Word (or Office) document that's the
>> > problem?
>> >
>> > We're getting very good accessible PDFs from Word and PPT when the
>> source
>> > files are constructed correctly and exported correctly with Acrobat's
>> PDF
>> > Maker plug-in. I admit, there are some of the more complex items in Word
>> > that fail the conversion, but they are being addressed.
>> >
>> > Plus, none of those extra programs make complaint PRESS files for those
>> of
>> > us who must communicate both in print and digitally.
>> >
>> > —Bevi Chagnon
>> >
>> > -----Original Message-----
>> > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
>> > Behalf Of Duff Johnson
>> > Sent: Thursday, January 7, 2016 12:46 PM
>> > To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>> > Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>> >
>> > > At this time, Adobe's products still reign supreme for PDFs, whether
>> you
>> > need a press-quality one for sending to the print shop, or an accessible
>> > one for electronic distribution.
>> >
>> > With respect… not so. There are other products that do as good and in
>> some
>> > cases a much better job of creating tagged PDF from MS Word files (for
>> > example) than Acrobat in its current incarnation.
>> >
>> > Moreover, some of these tools - typically the ones oriented specifically
>> > towards accessibility - include far, far better resources than Acrobat
>> > provides for ensuring accessibility of PDF documents.
>> >
>> > It’s not my role to identify these vendors here.. but they exist, they
>> > aren’t hiding and their products are available for sale today.
>> >
>> > Duff.
>> > >> > >> archives
>> > at http://webaim.org/discussion/archives
>> > >> >
>> > >> > >> > >> > >> >
>> >> >> >> >>
>
>

From: Duff Johnson
Date: Thu, Jan 07 2016 2:33PM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

> With respect, Duff, is it Acrobat that makes lousy files? Or is it the lousy construction of the source Word (or Office) document that's the problem?

The latter problem is generic and would affect all PDF producing software. I didn't say Acrobat makes lousy files...

> We're getting very good accessible PDFs from Word and PPT when the source files are constructed correctly and exported correctly with Acrobat's PDF Maker plug-in.

Yes, good results in many cases - I use it too. I’m simply saying that there are other solutions that do as good or better of a job.

> I admit, there are some of the more complex items in Word that fail the conversion, but they are being addressed.

Yes…

> Plus, none of those extra programs make complaint PRESS files for those of us who must communicate both in print and digitally.

VERY true. I was referring only to accessibility considerations…

Duff.

From: Chagnon | PubCom.com
Date: Thu, Jan 07 2016 2:37PM
Subject: Re: Accessible PDFs from Google Doc/Presentation
← Previous message | Next message →

Many reasons why PDFs are needed.

Governments, corporations, and institutionals generally need a copy of everything they create that can be easily archived and established as a snapshot; that is, this was the document's state at this particular point in time.
Often it must be secured or locked from further edits or changes.
And it must be stored someplace where they have total control of the information, such as on their own servers, not Google's.

HTML versions are often spread across several webpages making it difficult to refer to "one" document. Google Docs are on Google's servers.

Other considerations:
One file that can be attached to an email, burned to a flash drive, and distributed.
Once they are downloaded to the device, PDFs don't require an active internet connection or fast bandwidth.

—Bevi Chagnon

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Lucy Greco
Sent: Thursday, January 7, 2016 3:55 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation

hello:"
sorry i need to chime in here why save as a pdf any way why not save
the docs or slides presentation to html google does a good job of making
that accessable. what reason is there for a pdf of some thing that was born on the web.

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces

From: Kroon, Kurtis@FTB
Date: Fri, Jan 08 2016 12:57PM
Subject: Re: Web-native presentations (was: Accessible PDFs from Google Doc/Presentation)
← Previous message | Next message →

For web-native presentations that (since they use HTML / CSS / JS) are easier to make accessible, does anyone use S5[1] or HTML Slidy[2]?

Thank you!
                          
Kurtis Kroon
CA:GO:FTB:ASD:CSB:WSS:WUXU:AssocISA
916-845-5603

Reference:
[1]: http://meyerweb.com/eric/tools/s5/
[2]: http://www.w3.org/Talks/Tools/Slidy2/



-----Original Message-----
From: Chagnon | PubCom.com [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Thursday, January 07, 2016 13:38
To: 'WebAIM Discussion List' < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation

Many reasons why PDFs are needed.

Governments, corporations, and institutionals generally need a copy of everything they create that can be easily archived and established as a snapshot; that is, this was the document's state at this particular point in time.
Often it must be secured or locked from further edits or changes.
And it must be stored someplace where they have total control of the information, such as on their own servers, not Google's.

HTML versions are often spread across several webpages making it difficult to refer to "one" document. Google Docs are on Google's servers.

Other considerations:
One file that can be attached to an email, burned to a flash drive, and distributed.
Once they are downloaded to the device, PDFs don't require an active internet connection or fast bandwidth.

—Bevi Chagnon

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Lucy Greco
Sent: Thursday, January 7, 2016 3:55 PM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation

hello:"
sorry i need to chime in here why save as a pdf any way why not save
the docs or slides presentation to html google does a good job of making
that accessable. what reason is there for a pdf of some thing that was born on the web.

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces



CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email.

From: Karl Groves
Date: Sat, Jan 09 2016 9:05AM
Subject: Re: Web-native presentations (was: Accessible PDFs from Google Doc/Presentation)
← Previous message | Next message →

Those are pretty old. Personally I use Shower: http://shwr.me/ but
Reveal is also supposed to be good. http://lab.hakim.se/reveal-js/#/

On Fri, Jan 8, 2016 at 2:57 PM, Kroon, Kurtis@FTB
< = EMAIL ADDRESS REMOVED = > wrote:
> For web-native presentations that (since they use HTML / CSS / JS) are easier to make accessible, does anyone use S5[1] or HTML Slidy[2]?
>
> Thank you!
>
> Kurtis Kroon
> CA:GO:FTB:ASD:CSB:WSS:WUXU:AssocISA
> 916-845-5603
>
> Reference:
> [1]: http://meyerweb.com/eric/tools/s5/
> [2]: http://www.w3.org/Talks/Tools/Slidy2/
>
>
>
> -----Original Message-----
> From: Chagnon | PubCom.com [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Thursday, January 07, 2016 13:38
> To: 'WebAIM Discussion List' < = EMAIL ADDRESS REMOVED = >
> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>
> Many reasons why PDFs are needed.
>
> Governments, corporations, and institutionals generally need a copy of everything they create that can be easily archived and established as a snapshot; that is, this was the document's state at this particular point in time.
> Often it must be secured or locked from further edits or changes.
> And it must be stored someplace where they have total control of the information, such as on their own servers, not Google's.
>
> HTML versions are often spread across several webpages making it difficult to refer to "one" document. Google Docs are on Google's servers.
>
> Other considerations:
> One file that can be attached to an email, burned to a flash drive, and distributed.
> Once they are downloaded to the device, PDFs don't require an active internet connection or fast bandwidth.
>
> —Bevi Chagnon
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Lucy Greco
> Sent: Thursday, January 7, 2016 3:55 PM
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>
> hello:"
> sorry i need to chime in here why save as a pdf any way why not save
> the docs or slides presentation to html google does a good job of making
> that accessable. what reason is there for a pdf of some thing that was born on the web.
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
>
> > CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email.
> > > > --

Karl Groves
www.karlgroves.com
@karlgroves
http://www.linkedin.com/in/karlgroves
Phone: +1 410.541.6829


www.tenon.io

Sign up for the Tenon Mailing List:
http://eepurl.com/bcV8C9

From: Chaals McCathie Nevile
Date: Mon, Jan 11 2016 2:15AM
Subject: Re: Web-native presentations (was: Accessible PDFs from Google Doc/Presentation)
← Previous message | Next message →

On Sat, 09 Jan 2016 19:05:02 +0300, Karl Groves < = EMAIL ADDRESS REMOVED = >
wrote:

> Those are pretty old. Personally I use Shower: http://shwr.me/ but
> Reveal is also supposed to be good. http://lab.hakim.se/reveal-js/#/

I also use shower. It's still less than perfect last I checked, about 6
months ago. Lots of stuff seemed to get lost big time - but it had been
improved, and Vadim is likely to accept pull requests that make it better
if you have a sense of how.

cheers

> On Fri, Jan 8, 2016 at 2:57 PM, Kroon, Kurtis@FTB
> < = EMAIL ADDRESS REMOVED = > wrote:
>> For web-native presentations that (since they use HTML / CSS / JS) are
>> easier to make accessible, does anyone use S5[1] or HTML Slidy[2]?
>>
>> Thank you!
>>
>> Kurtis Kroon
>> CA:GO:FTB:ASD:CSB:WSS:WUXU:AssocISA
>> 916-845-5603
>>
>> Reference:
>> [1]: http://meyerweb.com/eric/tools/s5/
>> [2]: http://www.w3.org/Talks/Tools/Slidy2/
>>
>>
>>
>> -----Original Message-----
>> From: Chagnon | PubCom.com [mailto: = EMAIL ADDRESS REMOVED = ]
>> Sent: Thursday, January 07, 2016 13:38
>> To: 'WebAIM Discussion List' < = EMAIL ADDRESS REMOVED = >
>> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>>
>> Many reasons why PDFs are needed.
>>
>> Governments, corporations, and institutionals generally need a copy of
>> everything they create that can be easily archived and established as a
>> snapshot; that is, this was the document's state at this particular
>> point in time.
>> Often it must be secured or locked from further edits or changes.
>> And it must be stored someplace where they have total control of the
>> information, such as on their own servers, not Google's.
>>
>> HTML versions are often spread across several webpages making it
>> difficult to refer to "one" document. Google Docs are on Google's
>> servers.
>>
>> Other considerations:
>> One file that can be attached to an email, burned to a flash drive, and
>> distributed.
>> Once they are downloaded to the device, PDFs don't require an active
>> internet connection or fast bandwidth.
>>
>> —Bevi Chagnon
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
>> Behalf Of Lucy Greco
>> Sent: Thursday, January 7, 2016 3:55 PM
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>>
>> hello:"
>> sorry i need to chime in here why save as a pdf any way why not save
>> the docs or slides presentation to html google does a good job of
>> making
>> that accessable. what reason is there for a pdf of some thing that was
>> born on the web.
>>
>> Lucia Greco
>> Web Accessibility Evangelist
>> IST - Architecture, Platforms, and Integration University of
>> California, Berkeley
>> (510) 289-6008 skype: lucia1-greco
>> http://webaccess.berkeley.edu
>> Follow me on twitter @accessaces
>>
>>
>>
>> >> CONFIDENTIALITY NOTICE: This email from the State of California is for
>> the sole use of the intended recipient and may contain confidential and
>> privileged information. Any unauthorized review or use, including
>> disclosure or distribution, is prohibited. If you are not the intended
>> recipient, please contact the sender and destroy all copies of this
>> email.
>> >> >> >> >
>
>


--
Charles McCathie Nevile - web standards - CTO Office, Yandex
= EMAIL ADDRESS REMOVED = - - - Find more at http://yandex.com

From: Karl Groves
Date: Mon, Jan 11 2016 5:07AM
Subject: Re: Web-native presentations (was: Accessible PDFs from Google Doc/Presentation)
← Previous message | Next message →

"Vadim is likely to accept pull requests that make it better if you
have a sense of how."

+1. He accepted two of my PRs pretty readily.

While we're at it, can I get comments from the WebAIMers on this?
https://github.com/shower/shower/issues/220

On Mon, Jan 11, 2016 at 4:15 AM, Chaals McCathie Nevile
< = EMAIL ADDRESS REMOVED = > wrote:
> On Sat, 09 Jan 2016 19:05:02 +0300, Karl Groves < = EMAIL ADDRESS REMOVED = > wrote:
>
>> Those are pretty old. Personally I use Shower: http://shwr.me/ but
>> Reveal is also supposed to be good. http://lab.hakim.se/reveal-js/#/
>
>
> I also use shower. It's still less than perfect last I checked, about 6
> months ago. Lots of stuff seemed to get lost big time - but it had been
> improved, and Vadim is likely to accept pull requests that make it better if
> you have a sense of how.
>
> cheers
>
>
>> On Fri, Jan 8, 2016 at 2:57 PM, Kroon, Kurtis@FTB
>> < = EMAIL ADDRESS REMOVED = > wrote:
>>>
>>> For web-native presentations that (since they use HTML / CSS / JS) are
>>> easier to make accessible, does anyone use S5[1] or HTML Slidy[2]?
>>>
>>> Thank you!
>>>
>>> Kurtis Kroon
>>> CA:GO:FTB:ASD:CSB:WSS:WUXU:AssocISA
>>> 916-845-5603
>>>
>>> Reference:
>>> [1]: http://meyerweb.com/eric/tools/s5/
>>> [2]: http://www.w3.org/Talks/Tools/Slidy2/
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Chagnon | PubCom.com [mailto: = EMAIL ADDRESS REMOVED = ]
>>> Sent: Thursday, January 07, 2016 13:38
>>> To: 'WebAIM Discussion List' < = EMAIL ADDRESS REMOVED = >
>>> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>>>
>>> Many reasons why PDFs are needed.
>>>
>>> Governments, corporations, and institutionals generally need a copy of
>>> everything they create that can be easily archived and established as a
>>> snapshot; that is, this was the document's state at this particular point in
>>> time.
>>> Often it must be secured or locked from further edits or changes.
>>> And it must be stored someplace where they have total control of the
>>> information, such as on their own servers, not Google's.
>>>
>>> HTML versions are often spread across several webpages making it
>>> difficult to refer to "one" document. Google Docs are on Google's servers.
>>>
>>> Other considerations:
>>> One file that can be attached to an email, burned to a flash drive, and
>>> distributed.
>>> Once they are downloaded to the device, PDFs don't require an active
>>> internet connection or fast bandwidth.
>>>
>>> —Bevi Chagnon
>>>
>>> -----Original Message-----
>>> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
>>> Behalf Of Lucy Greco
>>> Sent: Thursday, January 7, 2016 3:55 PM
>>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>>> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>>>
>>> hello:"
>>> sorry i need to chime in here why save as a pdf any way why not save
>>> the docs or slides presentation to html google does a good job of
>>> making
>>> that accessable. what reason is there for a pdf of some thing that was
>>> born on the web.
>>>
>>> Lucia Greco
>>> Web Accessibility Evangelist
>>> IST - Architecture, Platforms, and Integration University of California,
>>> Berkeley
>>> (510) 289-6008 skype: lucia1-greco
>>> http://webaccess.berkeley.edu
>>> Follow me on twitter @accessaces
>>>
>>>
>>>
>>> >>> CONFIDENTIALITY NOTICE: This email from the State of California is for
>>> the sole use of the intended recipient and may contain confidential and
>>> privileged information. Any unauthorized review or use, including disclosure
>>> or distribution, is prohibited. If you are not the intended recipient,
>>> please contact the sender and destroy all copies of this email.
>>> >>> >>> >>> >>
>>
>>
>>
>
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> = EMAIL ADDRESS REMOVED = - - - Find more at http://yandex.com
>
> > > > --

Karl Groves
www.karlgroves.com
@karlgroves
http://www.linkedin.com/in/karlgroves
Phone: +1 410.541.6829


www.tenon.io

Sign up for the Tenon Mailing List:
http://eepurl.com/bcV8C9

From: David Farough
Date: Mon, Jan 11 2016 9:12AM
Subject: Re: Web-native presentations (was: Accessible PDFs from Google Doc/Presentation)
← Previous message | No next message

I liked Leonie's suggestion on this. she suggested providing a
Presentation mode switch in the content which would allow a user to
change modes while in the presentation. This would allow a screen
reader user to switch modes in order to gain the benefits of using brows
mode when the content required it and use the conventional mode so as to
facilitate slide navigation and other Javascript provided functionality
when necessary.

In my opinion, Application mode would certainly help, but I have found
that getting out of application mode can be a problem at times.

Incidentally, I think the article that Leonie provided is the best
explanation of Screen reader interaction modes that I have seen.
http://tink.uk/understanding-screen-reader-interaction-modes/




David Farough

Coordonnateur de l'accessibilité des applications, Services intégrés de
gestion des TI
Commission de la fonction publique du Canada / Gouvernement du Canada
= EMAIL ADDRESS REMOVED = Tél: 819-420-8418 Télécopieur :
819-420-8408

Application Accessibility Co-ordinator, Corporate IT Management
Public Service Commission of Canada / Government of Canada
= EMAIL ADDRESS REMOVED = Tel: 819-420-8418 / Fax: 819-420-8408


>>> Karl Groves < = EMAIL ADDRESS REMOVED = > 07:07 AM Monday, January 11, 2016
>>>
"Vadim is likely to accept pull requests that make it better if you
have a sense of how."

+1. He accepted two of my PRs pretty readily.

While we're at it, can I get comments from the WebAIMers on this?
https://github.com/shower/shower/issues/220

On Mon, Jan 11, 2016 at 4:15 AM, Chaals McCathie Nevile
< = EMAIL ADDRESS REMOVED = > wrote:
> On Sat, 09 Jan 2016 19:05:02 +0300, Karl Groves < = EMAIL ADDRESS REMOVED = >
wrote:
>
>> Those are pretty old. Personally I use Shower: http://shwr.me/
but
>> Reveal is also supposed to be good. http://lab.hakim.se/reveal-js/#/

>
>
> I also use shower. It's still less than perfect last I checked, about
6
> months ago. Lots of stuff seemed to get lost big time - but it had
been
> improved, and Vadim is likely to accept pull requests that make it
better if
> you have a sense of how.
>
> cheers
>
>
>> On Fri, Jan 8, 2016 at 2:57 PM, Kroon, Kurtis@FTB
>> < = EMAIL ADDRESS REMOVED = > wrote:
>>>
>>> For web-native presentations that (since they use HTML / CSS / JS)
are
>>> easier to make accessible, does anyone use S5[1] or HTML Slidy[2]?
>>>
>>> Thank you!
>>>
>>> Kurtis Kroon
>>> CA:GO:FTB:ASD:CSB:WSS:WUXU:AssocISA
>>> 916-845-5603
>>>
>>> Reference:
>>> [1]: http://meyerweb.com/eric/tools/s5/
>>> [2]: http://www.w3.org/Talks/Tools/Slidy2/
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Chagnon | PubCom.com [mailto: = EMAIL ADDRESS REMOVED = ]
>>> Sent: Thursday, January 07, 2016 13:38
>>> To: 'WebAIM Discussion List' < = EMAIL ADDRESS REMOVED = >
>>> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>>>
>>> Many reasons why PDFs are needed.
>>>
>>> Governments, corporations, and institutionals generally need a copy
of
>>> everything they create that can be easily archived and established
as a
>>> snapshot; that is, this was the document's state at this particular
point in
>>> time.
>>> Often it must be secured or locked from further edits or changes.
>>> And it must be stored someplace where they have total control of
the
>>> information, such as on their own servers, not Google's.
>>>
>>> HTML versions are often spread across several webpages making it
>>> difficult to refer to "one" document. Google Docs are on Google's
servers.
>>>
>>> Other considerations:
>>> One file that can be attached to an email, burned to a flash drive,
and
>>> distributed.
>>> Once they are downloaded to the device, PDFs don't require an
active
>>> internet connection or fast bandwidth.
>>>
>>> —Bevi Chagnon
>>>
>>> -----Original Message-----
>>> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ]
On
>>> Behalf Of Lucy Greco
>>> Sent: Thursday, January 7, 2016 3:55 PM
>>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>>> Subject: Re: [WebAIM] Accessible PDFs from Google Doc/Presentation
>>>
>>> hello:"
>>> sorry i need to chime in here why save as a pdf any way why not
save
>>> the docs or slides presentation to html google does a good job
of
>>> making
>>> that accessable. what reason is there for a pdf of some thing that
was
>>> born on the web.
>>>
>>> Lucia Greco
>>> Web Accessibility Evangelist
>>> IST - Architecture, Platforms, and Integration University of
California,
>>> Berkeley
>>> (510) 289-6008 skype: lucia1-greco
>>> http://webaccess.berkeley.edu
>>> Follow me on twitter @accessaces
>>>
>>>
>>>
>>>
>>> CONFIDENTIALITY NOTICE: This email from the State of California is
for
>>> the sole use of the intended recipient and may contain confidential
and
>>> privileged information. Any unauthorized review or use, including
disclosure
>>> or distribution, is prohibited. If you are not the intended
recipient,
>>> please contact the sender and destroy all copies of this email.
>>> >>> >>> >>> >>
>>
>>
>>
>
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> = EMAIL ADDRESS REMOVED = - - - Find more at http://yandex.com
>
> > > > --

Karl Groves
www.karlgroves.com
@karlgroves
http://www.linkedin.com/in/karlgroves
Phone: +1 410.541.6829


www.tenon.io

Sign up for the Tenon Mailing List:
http://eepurl.com/bcV8C9
Ce courriel est destiné exclusivement au destinataire mentionné en titre
et peut contenir de l'information privilégiée, confidentielle ou
soustraite à la communication aux termes des lois applicables. Toute
divulgation non autorisée, toute reproduction ou réacheminement est
interdit. Si vous n'êtes pas le destinataire de ce courriel, ou n'êtes
pas autorisé par le destinataire visé, ou encore, si vous l'avez reçu
par erreur, veuillez le mentionner immédiatement à l'expéditeur et
supprimer le courriel et les copies.

This e-mail message is intended for the named recipient(s) and may
contain information that is privileged, confidential and/or exempt from
disclosure under applicable law. Unauthorized disclosure, copying or
re-transmission is prohibited. If you are not a named recipient or not
authorized by the named recipient(s), or if you have received this
e-mail in error, then please notify the sender immediately and delete
the message and any copies.