W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2000

Re: PDFs and Link

From: Charles McCathieNevile <charles@w3.org>
Date: Thu, 7 Dec 2000 13:07:38 -0500 (EST)
To: Al Gilman <asgilman@iamdigex.net>
cc: <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0012071253140.8299-100000@tux.w3.org>
Sorry, by officially I was understanding the question as "is this an official
thing Adobe offers?", and so far, I understand the answer as yes. (Al is
right about the fact that there aren't "official WAI answers" to this kind of

Adobe publishes information on how to use PDF accesssibly -
http://access.adobe.com/information.html has some links.


Charles McCathieNevile

On Wed, 6 Dec 2000, Al Gilman wrote:

  >At 10:19 PM 12/05/2000, Charles McCathieNevile wrote:
  >>Officially, the Adobe thing works. Practically it works too - it translates
  >>PDF into HTML.

  I fear these answers may not reflect what was intended by the questions.

  There is no answer to "offically" in the WAI-IG context because there is no
  official W3C position on this question.

  Also, "it generates HTML" is not how I would evaluate "does it work,

  My interpretation of the questions would lead to answers:

  Practically: sometimes; try before you buy.  Talk to Adobe for what to try.

  Officially: no answer; you must determine this for your own definition of what
  is 'official.'

  Don't be ignorant of what is happening in the Federal arena on this question,
  but don't fail to do your own analysis independent of what is happening
  If you are involved in a state agency, the accessibility SWAT team of the
  national association of state CIOs may be a network you want to work
  through in
  addressing this issue.

  There are PDF publishing practices which improve the results when the PDF so
  produced is then transformed to HTML or text by the available PDF conversion
  processes.  Adobe can and will gladly tell you about them.  But try before you
  buy.  Only you can see if they are workable in your document production
  environment, and effective for the kinds of documents you produce.

  A successful document production practice which generates both PDF and
  accessible HTML may require either or both of a) a constrained set of document
  templates in the original authoring environment and/or b) extraction of the
  HTML from a point in the authoring process prior to the PDF form.

  If people are using contract print shops and getting the PDF form from them,
  then we need to get the people who run these enterprises involved in
  consolidating the best practice for this requirement.  I am not aware, myself,
  of best-practice literature that covers all you have to do and has been
  independently validated as working by real content providers and consumers


  At 10:18 AM 2000-12-06 -0500, Massey, Nancy wrote:
  >I am intrigued by your comment of "good PDF". Up until recently I have not
  >had occasion to need to create PDF's for clients, but will be very shortly.
  >Can you suggest any resources where I might learn more about good vs bad PDF.
  >At 10:19 PM 12/05/2000, Charles McCathieNevile wrote:
  >>Officially, the Adobe thing works. Practically it works too - it translates
  >>PDF into HTML. How useful the resulting HTML is depends a lot on the
  >>PDF - some PDF can be translated into extremely useful content, other PDF
  >>turns out more or less pointless.
  >>Authoring good HTML or authoring good PDF is preferable - it is possible to
  >>use both formats to make something that is more or less useless to readers.

Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
W3C Web Accessibility Initiative                      http://www.w3.org/WAI
Location: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
September - November 2000:
W3C INRIA, 2004 Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France
Received on Thursday, 7 December 2000 13:07:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:10 UTC