Hello,

I understand that Nuance make a PDF converter:

http://shop.nuance.com/store?Action=DisplayPage&Env=BASE&Locale=en_AU&SiteID=scsoftAP&id=ProductDetailsPage&productID=208595700

Have not used it myself however, it may be an improvement on the Acrobat batch convert that Damien talks about. Perhaps others could offer comments.

Regards,

Grant Bailey


On 9/02/2011 4:33 PM, Samuel Santana wrote:
Hi all,
This is not a solution to your problem as these documents have already been created but just wanted to add my two-cents. Generally publications are created/developed using a word processing file (MS-Word or equivalent). Word processors have the ability to work with their own internal stylesheets which aside from providing visual consitency in relation to headings etc. it can also be used to provide a structure to the document. This can be used to automatically generate table of contents etc. but more importantly in the context of this question it also provides a heading hierarchy (just like that required by accessible HTML). Preparing a corporate document(s) template for staff to use in the preparation of documents can take some negotiating and a slight shift in how people work with programs like Word (not just selecting a piece of text and making it 20-point Arial but instead formatting is as a heading 2 for example) but it provides many advantages including two very important ones such as the ability to export that document as a web page (with a CSS section rather than inline markup) but also allowing the document (along with other requirements such as providing alternative text to images etc.) to be fully accessible to screen readers.
Sam

On 9 February 2011 15:48, Geary, Damien <[email protected] <mailto:[email protected]>> wrote:

    Just to touch on the OP's question, Adobe Acrobat Pro has the
    ability to batch export many pdfs to HTML. Select File > Export >
    Multiple Files. Select the files you want batch converted, choose
    html as your output. Proceed to laugh \ cry at the lack of
    formatting \ structure retained in the html version.

    -----Original Message-----
    From: [email protected]
    <mailto:[email protected]>
    [mailto:[email protected]
    <mailto:[email protected]>] On Behalf Of Webb, KerryA
    Sent: Wednesday, 9 February 2011 3:33 PM
    To: [email protected] <mailto:[email protected]>
    Subject: RE: [WSG] PDF Conversion

    Dave wrote:
    >
    > On 09/02/11 16:55, Russ Weakley wrote:
    > > Hi Kerry. Neither the blind user or I were suggesting that
    > > alternatives were not a good idea, or even a requirement. I'd
    always
    > > recommend providing an HTML alternative if possible along with
    > > accessible (tagged) PDF. The question was about Word as as a
    viable
    > > alternative to PDF. I am not sure it is. Though others may
    disagree!
    >
    > I'm not an accessibility expert, but it seems pretty obvious
    that if the
    > PDF isn't well structured (which would presumably make it more
    > accessible), I can't imagine that converting it to an MS Word
    document
    > will add any sensible structure that wasn't there before.
    >

    Neither am I an accessibility expert, but I'm of necessity taking
    more interest in it these days.

    There are a number of reasons - not just about structure - why a
    blind user might have trouble with a PDF.  An MS Word (or an RTF)
    document may be a more accessible alternative to a PDF.

    > Using standards compliant HTML as an alternative accessible standard
    > makes much more sense (again, assuming the source document wasn't
    > generated from your typical poorly structured MS Word document).
    >

    And few Web managers will find the time and resources to create a
    readable standards compliant HTML version of a multi-multi-page
    PDF, whereas a Word document will in many cases be more doable.

    Kerry
    -----------------------------------------------------------------------
    This email, and any attachments, may be confidential and also
    privileged. If you are not the intended recipient, please notify
    the sender and delete all copies of this transmission along with
    any attachments immediately. You should not copy or use it for any
    purpose, nor disclose its contents to any other person.
    -----------------------------------------------------------------------


    *******************************************************************
    List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
    Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
    Help: [email protected]
    <mailto:[email protected]>
    *******************************************************************



    *******************************************************************
    List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
    Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
    Help: [email protected]
    <mailto:[email protected]>
    *******************************************************************


    ______________________________________________________________________
    This email has been scanned by the MessageLabs Email Security System.
    For more information please visit http://www.messagelabs.com/email
    ______________________________________________________________________



*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************

Reply via email to