Accessible PDFs - Identifying and diferences

Using WinXP and Reader X
#1  When a pdf is presented on a website, how does one know if was made to be accessible?
#2  All PDFs are accessible to a certain extent; What is different about one that was made to be accessible?
#3  What help is offered to mahe PDFs accessible to those with low contrast sensitivity?
Will it allow choice of font as set in my browser?
===gm===

An "Accessible" PDF is one that has been Tagged. Tagged PDF makes use of PDF centric markup.
(Starting reference is Section 14 of ISO 32000-1 which the ISO Standard for PDF. The ISO Standard for PDF Universal Accessiblilty, ISO 14289-1, is expected in 2012.)
There is a "quick check" that can be done to see if a PDF is "Tagged".
View the Description tabl of a PDF's Document Properties (Ctrl+D or Cmd+D).
The bottom left has a field "Tagged PDF" which can have a value of "Yes" or "No".
However, this is not "definitive" as one may use Acrobat Pro to set the value to "Yes" for an untagged PDF.
A Tagged PDF may be workable or well-formed.
Workable often means workable for most users of AT most times but, sometimes, lacking due consideration for color contrast or low vision issues.
A well-formed Tagged PDF typically considers these back in the content mastering by the content author/provider.
The "workable" or "well-formed" Tagged PDF starts with the content author/provider when content is mastered.
Without this one can have a Tagged PDF that is unusable.
Properly mastered, the content author/provider must follow-up with requisite post-processing of the Tagged output PDF using Acrobat Pro.
For untagged PDFs Adobe Reader and Acrobat will programmatically provide a "best-guess" tagging when the PDF is accessed by assistive technology software.
A nice feature the very simple PDF content. Not so helpful for more complex content or content that was poorly mastered back in the authoring application. 
How well a PDF performs (or does not perform) when under "Accessibility load"  is a direct function of what the content author / provider mastered and piped out.
Both Adobe Reader and Acrobat facilitate PDF consumption by those with low vision.
In Preferences, go to the Accessibility category. Document Colors Options are available there (e.g.. High-Contrast color usage).
As well, each supports user zoom and selection of a reflow mode. 
But, again, at the end of the day the buck stops with the content author/provided.
No, "choice of fonts" (such as with web pages); this is not an option with PDF.
It is a "PDF" thing not related to applications (see the ISO Standard).
Be well...
Message was edited by: CtDave

Similar Messages

  • Accessible PDF files and forms

    I am beside myself with the lack of help and/or interest in the Accessiblity area. We have been mandated to make all our PDF files accessible on our Web site. We have been able to master many of the issues regarding tags and form fields, but still have questions regarding updating the original PDFs without loosing the tag structure.
    Is there any options on the Adobe site that may concentrate on this area? I called tech support yesterday (Bronze contract), was on hold for 10 mins and got disconnected. After leaving my number, they never called me back again.
    HELP
    KEN PANTHEN, Albany, NY

    Bill
    The point was not having to create the tags again in a new file before
    replacing the pages containing the form fields in the old file. We have
    many forms that get updated right up to the last minute and to go through
    the tagging process is too time consuming. We do not use PDF Maker, but
    produce all the PDFs directly out of InDesignCS3 to Adobe Acrobat
    Professional (Distiller).
    Thanks for your reply.
    KEN PANTHEN
    NYS Tax Department
    Information Technology Specialist 2
    FPM - Composition Services Unit
    (518) 457-1425
    (518) 485-7828 (fax)
    From:
    "Bill@VT" <[email protected]>
    To:
    Kenneth Panthen <[email protected]>
    Date:
    06/24/09 11:19 AM
    Subject:
    Accessible PDF files and forms
    I am really suggesting replacing all of the pages. I was thinking that the
    tag structure would go with the replacement and you would need to create
    the other PDF with PDF Maker to keep the tagging. I may be wrong, but that
    was the view I had. If you replace a single page, I am not sure what might
    happen since that would generally not be done with PDF Maker.
    Since you already have the application process going, it is probably
    easiest for you to try the variations on replacing pages and such --
    basically what I would be doing.

  • How do I create an accessible PDF for Thesaurus with many chapters, from InDesign CS 5.5 and Acrobat

    Hi folks,
    I have redesigned a Thesaurus (controlled vocabulary for an Agency's archives) in InDesign CS 5.5. I am now preparing an accessible PDF from the many files (using a Book created in InDesign). The front cover, front matter and back cover are not part of the Book, to keep the page numbering simple.
    The Book includes two main sections, an Alphabetical display and a Hierarchical display of terms and their relations. I created chapters per alphabet listings, i.e. Alphabetical Display A, B, C, etc. So there are over 50 chapters, including cover, front matter, etc.
    I've successfully made the front cover and front matter PDFs after viewing videos here: http://tv.adobe.com/watch/accessibility-adobe/preparing-indesign-files-for-accessibility/ and downloading and using this recommended Action for Acrobat: InDesign CS5_5 Accessibility Touchup.sequ
    Several questions specific to this project don't seem to be addressed in the videos, however.
    First, I'd like to know if I can create an accessible PDF using the Book function > Export Book to PDF. Or do I need to make a PDF per chapter? The book has over 50 chapters (by alphabet, twice), so creating them one by one will take a lot more time, but I'll do it if that's the best practice.
    After creating the PDFs, if I use (in Acrobat): Create > Combine Files into PDF to make one full PDF (over 600 pages BTW), will the final PDF retain accessibility settings? Do I need to run the Accessibility Report again for the combined PDF?
    I used InTools.com Power Headers plugin to add a page header that automatically shows the new first term used per page. So, one chapter (with Chapter Title as H1) will have a different page header (which will be H2) per page, however the text flows through the whole chapter. I don't see where to add the page headers to the Article Window in InDesign. Do I add in this order: H1, H2, text (for whole chapter), H2, H2, H2, etc. Will I need to work on the PDF in Acrobat, where pages will be shown, in order to get the correct H2 with the correct text on the page? Am I missing something?
    Will I have any issues with Bookmarks that requires a specific workflow?
    I think that's about it, though I might run into more questions as I progress through the project.
    Thanks, Marilyn

    I understand why you need updated running headers in your book. To a sighted reader these serve as a guide to where you are and help you find things quickly.  In addition, if you are exporting your data to XML or HTML from the tagged PDF it would also be important to have these in the proper location. 
    But for accessibility purposes, it doesn't have to be there because the screen reader reads everything in linear order, line by line.  No one is looking at the page.  A user listening to the screen reader read the page is going to hear this heading, just before the actual word itself. So they will hear the first word on the page twice.  It's not the end of the world if it's there, but such headings are not necessary for accessibility unless they are not repetitive and contain information that is not otherwise available.
    So I would say, fine if you need them or want them there, it's just one word. 
    I think you should try exporting your book to PDF (or even just a chapter of the book) and look at the tags panel in Acrobat to see if you are getting the result you want.  I can't tell you exactly what you should do to get those results, you are using a plug-in I don't have. 
    I can tell you I didn't have to add the headers to any article at all, they just automatically export if the other articles in the file are added and you don't select the header style option "not for export as XML."
    You may not experience the same results with your plug-in, but I think it will probably work the same way. 
    Give it a try and best of luck.

  • Accessible PDFs from InDesign CS3 and Acrobat Pro 8

    Is there a good website or book that explains how to create an "accessible" PDF with text and images (no intaractivity or special fields to enter information)? Maybe a book for non-programmers.
    I find a lot of general information and it always states that it's the best to do the tagging from the beginning in InDesign but what else does it ivolve? In what order should I do what?
    Thanks.

    I'm doing one of the exercises provided by Adobe and have a question (InDesign CS3). I just learned that you can assign the "Artifact" tag to a graphic frame in two ways: Either via "New Attribute" in the Structure window (Articat/TRUE) or by right clicking and "Tag Element > Artifact").
    The results are different though. The New-Attribute-way keeps the name "Figure" and adds a Bullet to it saying Artifact=TRUE, while the right-click-option changes it from Figure to Artifact and adds no Bullet.
    Is there any difference for the person receiving the PDF and what is the better version (for what)? Thanks a lot!

  • Updating a PDF form and keeping it accessible... is there an easier way?

    So I have some InDesign files that were converted to PDF files then brought into Acrobat X where they were turned into accessible forms. 
    Now edits need to be made to the content.  I've been trying to figure out what the best approach with the least amount of steps to update these accessible PDF forms.
    So I export the PDF from InDesign, then..
    Option 1:
    Open the newly created PDF and the old version of the accessible form and Copy+paste form fields from old file to new file.
    The good: Tags, Structure, hyperlinks and reading order transfers over from Indesign.
    The bad: Time consuming. Tabbing order for the fields usually needs a lot of manual adjustment. Manually have to add language, title, subject, keywords
    Option 2:
    Open old PDF form and replace the page with the new PDF file.
    The good: Fast! Form tabbing order set. Language, title, subject, keywords all good set.
    The bad: Tags, Structure, hyperlinks and reading order are gone! Manually touchup reading order, add form fields to tags (which sometimes deletes fields and crashes)
    Option 3:
    Open old PDF and use edit document text to fix little issues.
    The good: It works for small issues.
    The bad: Not an option for anything besides a typo. Can't change layout. Have to do the edit again in Indesign, or have out-of-date files.
    Anyone have a better way of doing it?
    BTW I'm using InDesign CS5.5 and Acrobat X on Mac

    You can print it from you My Verizon online account under Documents and Receipts. This option will appear on the left after logging in.

  • Identifying PDF portfolios and OCRed PDFs

    Hi
    We have an application with about 10'000 PDF file attachments.
    Many of those were run through OCR.. Stupidly the users weren't instructed well enough prior doing so. It now occurs that most of those OCR texts have bad quality.
    Another issue is: our application can do fulltext search on the PDFs, many of the files are PDF portfolios which the fulltext enginen cannot "read" (technically, I have been told by the fulltext search engine programmer, PDF portfolios are NOT PDFs ;-) stupid but I can't change that)
    What I now require is help on how to:
    identify PDFs with images which have been run through OCR, so that we can rerun OCR through those PDFs
    identify PDFs which are atually PDF portfolios, so that we can (maybe automatically, maybe manually) convert them to normal PDFs
    I don't expect any prebuilt solution...
    we would even pay someone to help us out here. The data within those PDFs is crucial for our whole enterprise.
    I tried already some of the javascript apis... but no luck... maybe there are other tools which can help us here?
    I am thankful for any pointers and help in this topic
    Michael

    Testing for whether OCR has been performed may be tough. Preflight can report on hidden text objects, but this probably wouldn't be useful to you.
    You can test to see if a document is a portfolio using the collection property of a document (and/or test to see if there are any file attachments). This can be done using JavaScript in a batch sequence.

  • Text Flow in ePUB and Accessible PDF

    I have a newsletter in InDesign.  I have all the text flow marked.  Each article is a separate "story".  Story1 flows onto page 2, with the text flows linked correctly.  On page 2, story2 begins in the text box below the end of story1.
    So on page 2, why does accessble pdf read story2 before the second portion of story1?
    I have the same behavior in the version extracted to EPUB.
    Any ideas what I am doing wrong? or how I can correct it without having to create a single column of text throughout?
    Thank you,
    Joyce

    I've never seen that. In both accessible PDFs and EPUB, when I export all of a story will be read before going on to another object.
    What version of InDesign are you using? If you're using InDesign CS5.5 or later, you can use the Articles panel to set the reading order for accessibility (or for EPUB).

  • Acrobat vs Livecyle - which is better for making accessible PDF's

    I am having a very hard time making my PDF accessible. The source program I use to create my document is InDesign 5.5. I convert to PDF and am attempting to tag it using Acrobat X. I tried tagging my form using the articles panel in InDesign but it doesnt convert to PDF properly (which i learned at this forum is a system glitch). Someone at work suggesting using LiveCycle but I am not familiar with LiveCycle at all. I thougt it was an add-on extension to Acrobat so I'm confused why someone would tell me to use LiveCycle instead of Acrobat X. Can someone please clarify for me what the diff is between Acrobat and Livecyle. I need to make my document accessible by the end of the week and having a lot of problems doing it but i want to make sure that Acrobat is the best adobe product to use before going any further.
    Any help is GREATLY appreciated!

    Hi miss forms,
    I'm out of the country just now and "on-line" time is occasional. However, here are some observations for your consideration.
    All this may sound daunting. It is not (honest). Think of it as becoming a competent cook.
    Some study. Some practice then it is Rachael Ray time.
    ~~~~~~~~~~~
    Here's a short take:
    Use InD CS 5.5 to master the underlying "form text".
    Master content with accessible PDF in mind.
    Example - if any "headings" are to be used then use InD built-in paragraph tags.
    Output the tagged PDF.
    Walk the structure tree. Perform requisite post-processing activities.
    Goal is to acquire that well-formed tagged PDF.
    Next, build the form fields.
    Properly fold these into the structure tree.
    ~~~~~~~~~~~
    Observations:
    "... but i want to make sure that Acrobat is the best adobe product to use before going any further."
    Currently and for the foreseeable future - if  you must provide accessible PDF as a deliverable you must have Acrobat Pro.
    You want the most current version and you want to keep it updated.
    Currently there is no such thing as an accessible PDF that does not require post-processing by a knowledgeable "warm-body".
    As the 'warm-body' you perform the essential V&V prior to release of the deliverable.
    While there are tools to help with they still do not replace the 'warm-body'.
    "I need to make my document accessible by the end of the week ..."
    This could be problematic. Unless you are all ready well versed in what a well-formed tagged PDF is and how to stage it in the authoring file I suspect that you won't have a proper deliverable by 30 November.
    Using InD CS 5.5 is 'good' but it is not (as you've discovered) adequately robust for well-formed tagged PDF output compared to the current release.
    The output PDF needs manual remediation (only possible with Acrobat Pro).
    As to any current authoring application used -
    Whatever is used it needs to provide robust "tag management".
    Currently the first string consists of:
    Adobe FrameMaker,
    Adobe InDesign,
    (n.b., Adobe has invested significant resources in improving mastering content for accessible PDF and output of tagged PDF InDesign versions released since CS5.5. So, if InD is your requisite authoring application I'd recommend you move into the current release.)
    MS Word 2010.
    When using MS Word 2010 one can use the MS Save As PDF - XPS configured to provide accessible PDF or use
    PDFMaker.
    For Word 2010 you'd need at least Acrobat X in order to have a compatible PDFMaker.
    Some other applications are also providing for authoring / tagged PDF output (such as Open Office).
    Regardless of the authoring application used Acrobat Pro is still need for requisite post-processing (structure tree V&V, cleanup, etc).
    What form "type" to use?
    I'd recommend Acrobat forms rather than XFA forms.
    Accessible XFA forms are possible.
    But, As George said - a non-trivial learning curve for the basics. Then comes the learning / practice to develop the accessible XFA form.
    If you go with XFA I suggest obtaining the XFA spec that Adobe provides.
    Considering the improvements Adobe has made in Acrobat XI for Acrobat forms I'd recommend you use that.
    However, if you have an older version you can still get there from here (using Acrobat Pro).
    "Tools" considerations:
    Common Look PDF - An enterprise level tool.
    A plug-in for Acrobat.
    Common Look Office Pro
    (Pro supports PDF forms (Acrobat forms - not XFA forms)
    An add-in / plug-in for MS Office 2007/2010.
    Used with Power Point or Word.
    Provides check points on mastered content. You resolve identified issues then use it to output a tagged PDF.
    Perfom requisite post-processing with Acrobat Pro.
    http://www.commonlook.com/CommonLook-office
    MS Word 2010
    Provides content mastering "coaching" for output of accessible PDF.
    PDF Accessibility Checker
    A "validation" tool.
    http://www.access-for-all.ch/en/pdf-lab/pdf-accessibility-checker-pac.html
    AIIM's PDF/UA, Universal Accessiblity
    http://www.aiim.org/Research-and-Publications/Standards/Committees/PDFUA
    The "Achieving WCAG 2.0 with PDF/UA" is available.
    The Implementation Guides are in the oven.
    ISO 14289-1:2012 (ISO standard for PDF/UA)
    Available for purchase at ANSI's web store.
    ISO 32000-1 (ISO standard for PDF)
    Section 14.8 discusses tagged PDF.
    Free, ISO approved copy available from Adobe.
    http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_200 8.pdf
    I've tried to harvest accessible PDF documentation Adobe's provided since Acrobat 5.
    Have most of it my "eReference Shelves"; but, that's at home.
    What's nice about these documents is that you can harvest activity specific information with confidence that it is an appropriate "reciepe".
    If interested in adding these to your "shelves" let me know.
    Use this forum's PM feature.
    Be well...

  • Hyperlinks do not work when exporting to PDF (Crystal and Visual Cut)

    I have a question about Crystal Reports XI Release 2 and Visual Cut 11. I create reports in Crystal and export them using Visual Cut. Some reports contain hyperlinks to files on a network drive. However, the links only work while in Crystal. The PDF files that are printed through Visual Cut display the links, but they are not clickable. How can this issue be fixed?
    In case it helps, the links also work when I export reports from Crystal to HTML, Word, and Excel, but not when I export to Acrobat. I believe it is a problem with tagging/accessibilityfeatures. So is there a setting/formula in Crystal or Visual Cut that would allow the exported PDF files to be accessible?

    While Crystal exports to pdf indeed lose hyperlink functionality (both in Crystal as well as in Visual CUT), Visual CUT allows you to use Crystal formulas (acting as hidden Tags) to create hyperlinks in the resulting pdf file. Another option supported by Visual CUT it to automatically detect file references in the pdf text and turn them into hyperlinks.  Contact MilletSoftware for more detail.
    Edited by: Ido Millet on Oct 27, 2010 5:11 PM

  • How do I create an accessible PDF that doesn't generate a "tagged annotations - failed" error on the Accessibility Checker?

    I just reported this as a bug to Adobe, as I think it is.
    ******BUG******
    Concise problem statement: URLs generated from InDesign CC failed on Accessibility Checker (problem also exists in 2014)
    Steps to reproduce bug:
    1. Generated URLs using hyperlinks panel in InDesign. When accessibility report is run, they are flagged as "Tagged annotations - Failed," listed as Element 1, 2, etc. The links are live and clickable.
    2. To test, I removed all hyperlinks in Acrobat. It passed the test.
    3. Then I used "Create Links from URLs." The links were re-created. Running the accessibility report brought up the same error message.
    Results: The links created by Acrobat that actually do work fail the "tagged annotations" report. You have provided the tools to check accessibility, but the program itself can't generate URLs that pass the report.
    Expected results: I should be able to easily create an accessible pdf, as your documentation says I can. This, along with the failure of your "articles" panel detailed in another bug report, strike me as a serious problem with InDesign that should be fixed soon, especially given that designers are required more an more to adhere to accessibility guidelines.

    I have call out boxes like this:  All the links work correctly but they are divided with a tag for each line:

  • Create accessible pdf from html pages dynamically

    Hello,
    I am trying to create a 508 compliant Pdf from a simple HTML page using the HTML to Pdf feature in Livecycle ES4 server. I was able to configure the service to generate tabbed Pdf, but the created Pdf has multiple accessibility issues.
    Some of the issues encountered are:  incorrect tab order,  some links are not tabbable while others are,  link text is being read “Blank”,  some text is skipped while tabbing,  missing alt text for images,  page being rendered in the responsive(mobile) view,  etc.
    I have tried both the available approaches, of 1) providing a URL to create the PDF, and 2) to send the html document as a zipped file, with same results.
    Attached is a sample PDF generated from a simple HTML page I created for demo.
    My questions are:
    Is it possible to generate 508 compliant (accessible) Pdf documents using Html to Pdf service from Pdf Generator? If yes, which settings might I be missing?
    Is there any other service provided by Adobe Livecycle Server that can generate 508 compliant Pdf documents from a 508 compliant HTML page?
    Your help is much appreciated.
    Thanks,
    Anup

    I created a tool that does just that (only you will need to enter the page numbers as text, it does not work by selecting them):
    Acrobat -- Extract Non-Sequential Pages: http://try67.blogspot.com/2011/04/acrobat-extract-non-sequential-pages.html

  • Create accessible pdf from html page

    Hello,
    I am trying to create a 508 compliant Pdf from a simple HTML page using the HTML to Pdf feature in Livecycle ES4 server. I was able to configure the service to generate tabbed Pdf, but the created Pdf has multiple accessibility issues.
    Some of the issues encountered are:  incorrect tab order,  some links are not tabbable while others are,  link text is being read “Blank”,  some text is skipped while tabbing,  missing alt text for images,  page being rendered in the responsive(mobile) view,  etc.
    I have tried both the available approaches, of 1) providing a URL to create the PDF, and 2) to send the html document as a zipped file, with same results.
    Attached is a sample PDF generated from a simple HTML page I created for demo.
    My questions are:
    Is it possible to generate 508 compliant (accessible) Pdf documents using Html to Pdf service from Pdf Generator? If yes, which settings might I be missing?
    Is there any other service provided by Adobe Livecycle Server that can generate 508 compliant Pdf documents from a 508 compliant HTML page?
    Your help is much appreciated.
    Thanks,
    Anup

    I don't think it's possible to do this using a standard JavaScript script in Acrobat, since the newDoc function doesn't work with URLs.
    The only option I can think of is to use an external automator that will call the Create PDF From Web Page dialog, paste the address from a file, and after the PDF file is created will continue to the next line.
    I might be able to create such a tool for you. If you're interested, contact me by email (click my username for the address) or PM.

  • Tagging Acronyms/Abbreviations in Indesign for an accessible pdf

    I am trying to figure out the proper way to tag an acronym in an InDesign file to be properly read aloud in accessible pdf. Currently as it stands, the acronymns are being read as words instead of individual letters ( ex. APR is trying to be pronounced as 1 word). The only way I can think of is to outline that text and give it alt text, but this doesn't seem to be the most efficient way, especially since this acronym reoccurs throught the document in the middle of paragraphs. Also, when this is tagged, should it be the full phrase rather than the acronym that is read aloud, such as APR vs Annual Percentage Rate, even if it is defined elsewhere in the document what it stands for?

    I understand why you need updated running headers in your book. To a sighted reader these serve as a guide to where you are and help you find things quickly.  In addition, if you are exporting your data to XML or HTML from the tagged PDF it would also be important to have these in the proper location. 
    But for accessibility purposes, it doesn't have to be there because the screen reader reads everything in linear order, line by line.  No one is looking at the page.  A user listening to the screen reader read the page is going to hear this heading, just before the actual word itself. So they will hear the first word on the page twice.  It's not the end of the world if it's there, but such headings are not necessary for accessibility unless they are not repetitive and contain information that is not otherwise available.
    So I would say, fine if you need them or want them there, it's just one word. 
    I think you should try exporting your book to PDF (or even just a chapter of the book) and look at the tags panel in Acrobat to see if you are getting the result you want.  I can't tell you exactly what you should do to get those results, you are using a plug-in I don't have. 
    I can tell you I didn't have to add the headers to any article at all, they just automatically export if the other articles in the file are added and you don't select the header style option "not for export as XML."
    You may not experience the same results with your plug-in, but I think it will probably work the same way. 
    Give it a try and best of luck.

  • Looking for Accessible PDF creator

    (I'm posting this on behalf of my employer. I looked through terms of service and this sort of posting doesn't appear to be discouraged. If it is, let me know and I'll remove. Thanks!)
    Pacific Educational Press is seeking people with advanced knowledge of Acrobat Pro 9 to help us create an Accessible PDF of a Math textbook.
    Using Acrobat Pro 9, the qualified candidate will need to convert an ordinary PDF file of a math textbook  and convert it into an accessible PDF file that can be used by the visually impaired (using PDF-friendly speech software).
    The PDF document has numerous design aspects to it and the person would need to be able to map out the correct reading flow for the speech function of the Accessible PDF.
    The document would need to include cross-references and tags for alternate text (to describe the content of photographs, formulas and diagrams).
    The person would need to have an understanding of high-school math.
    The person would need to begin working immediately and complete the project by April 9.
    If you are interested, please send a resume highlighting relevant experience. You will be asked to create a sample PDF to show that you have experience using Acrobat 9 Pro.
    No phone calls please.

    A Math book eh?
    Equations/Formulas - fun.
    Regardless, you will want the right "tools" (hardware as well as software).
    Specifically, work machines with stand alone graphics card (at least 250MB - more *is* better).
    If you are authoring in Word, consider Netcentric's "PAWS".
    Might be worth some upfront trials of Word out to tagged PDF via the Office 2007 Save As to PDF.
    It has improved since its first release.
    Alternatively, augment Acrobat Pro 9 with Netcentric's CommonLook.
    The authoring application used will have a significant impact.
    Authoring in a page layout application?
    There are several good ones but, InDesign looks to have the best tag management.
    Tag management and the ability to "stage" for accessibility in the authoring file is significant advantage.
    But, for any large, living, technical - Nothing better than FrameMaker.
    On the whole, rather pleasing tag management.
    Also, does tables like nothing else..
    Add to this the "Book" feature of FrameMaker & things get better.
    Actually, your job is just what Adobe's Technical Communication Suite is all about (but that's getting OT).
    Do not rely upon Acrobat's Read Outload.
    Rather, QC PDFs via JAWS, Windows Eyes, NVDA.
    n.b., CommonLook gets good reviews on its ability to QC the PDF.
    You might want to consider a post to Adobe's Acrobat User Community "Job Board"
    as it may broaden exposure to your request.
    http://www.acrobatusers.com/forums/aucbb/viewforum.php?id=37
    The "tos" is at:
    http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=19437
    Good Luck with your endeavor.
    (just a end-thought - May want someone to spot check as the project goes along.
    Karen MCCall of Karlen Communications (out of Canada) may be one of the individuals that could help with such. Certainly there are others - she comes to mind as she has the knowledge/experience and is out of Canada.)
    Be well...
    Message was edited by: CtDave

  • Using Replace Pages in accessible PDF's

    Hi - Brand new to this forum.  Hoping someone can help... I have an existing tagged and accessible PDF - needed content update, so did that in Word, created a new tagged and accessible PDF, and used Replace pages to insert the new pages into the existing PDF.  Acrobat Help says when you replace pages in a PDF, Acrobat adds the tags from the incoming pages to the end of the tag tree... and keeps the tags for the replaced pages.   That didn't happen - the tags from the incoming pages are not there and, in fact, the tags that were in the existing PDF are not there anymore either - now it just says "Warning, empty page".   Any ideas?

    Hi kvd,
    I guess my nomenclature may be presumptive. All I should have said is that the most appropriate method I have discovered for retaining tagging and all other accessibility functionality has been the Combine command. Replace Pages sometimes works and most of the time (lately) is doesn’t. My experience with Insert Pages has not been consistently successful either.
    What you mean by a workflow I don’t fully understand. Do you mean an automated action? Unless you consistently use the same page numbers in every document, I don't know how you could automate it. Also, I have not been able to find specific process treatment about combining tagged PDFs. This has been a result of testing and experimentation.
    Let me know if you have any other questions.

Maybe you are looking for