Accessible PDF problem

I need to create accessible PDFs as part of my workflow. I use Indesign 5.5 and have applied "bevel and emboss" to an image. However, the resulting PDF fails the accessibility checker and reports that the offending image is "inaccessible content" and doesn't show up in the structure of the PDF. If the effect is turned off in InDesign, the PDF passes the test. Anyone know a workaround or the reason this is happening?.

Thanks Steve
I don't need to "think" about accessibility and I know all about alt tags as I've been doing this for years. However, I've never used InDesign's bevel/emboss on an image before and therefore have never encountered this error. The PDF is for the consumption of everybody: disabled and non-disabled (the hosting site will only allow the uploading of one PDF, so variations cannot be created). I acknowledge that people with visual impairments will not be able to appreciate the effects, but non-disabled users will.
However, the use of Photoshop is a good workaround (presuming that will get through). Just don't why this particular effect in InDesign would make the image "inaccessible content".
Thanks again

Similar Messages

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:

Replacing pages in accessible PDF's

Hi - Brand new to this forum. Hoping someone can help... I have an existing tagged, tested and accessible PDF - needed content update, so did that in Word, created a new tagged, tested 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?
Thanks greatly!

Hi Bill@VT,
Thanks for your response. Presently, I have AA Pro XI and Word 2007. I am confused - it seems the Adobe help material is saying different things - my pages say the new tags will come with the new pages, and your pages say not?
I am suspecting some of the problem may be coming from the fact that these documents have been created over many years using various versions of Word and Adobe Acrobat - since I got Pro XI, some pdf's that used to work OK for our people using screen reader technology suddenly don't read correctly anymore. I need to repair anything not working, and I need to create a new workflow process for myself to create accessible Word documents from the start. I'm thinking it may be cleaner to just start over and create all brand new Word documents with accessibility, maybe in Word 2010 or 2013, and then run them through Adobe Acrobat "Make Accessible" function and checker.

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...

Accessible pdf alt text read twice by on-screen reader

We are working on a math text book. We are currently creating an accessible pdf in addition to a text book for people who are visually impaired. We have ordered our text such that the on-screen reader reads the pages in the correct order and have tagged sections appropriately. However, some paragraphs contain several symbols that the on-screen reader cannot comprehend and for those we have made figures and inserted alt text that literally explains the equations. The problem is that the on-screen reader will first read the alt text but then will proceed to read the text itself that we are trying to replace. Thus many paragraphs are read twice. Please advise.

Hi,
Alternate Descriptions:
PDF documents may be enhanced by providing alternate descriptions for images, formulas, or other items that do not translate naturally into text.
But, you have content that does translate naturally into text. So, you get the alternate text entry and the content that is naturally renderable.
Consider use Replacement Text (Actual Text) or, when appropriate for abbreviations/acronyms, Expansion Text.
However, if the characters are naturally renderable, there is no need for any of these.
Do apply the PDF element for "formula" to the equation content.
Only use alternate text descriptions for image/graphic objects present in the PDF.
Avoid having other tagged content being associated with a child tag of a tag that has alternate or actual applied.
You may find having a copy of ISO 32000-1:2008 available helpful.
Obtain a free version oF ISO 32000-1.
http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000
Be well...

Alt tag rollovers in accessible pdfs

How can I make the alt tags for vector images (paths) show up upon rollover in my accessible PDF files. My alt tags show up for all raster images, but not for any eps, ai or png files... Is there a fix for this, either in InDesign or in Acrobat XI... a fix that does not involve using raster for everything please!

UPDATE:
I have spent a long time trying to find an answer to this to no avail. I have finally contacted Adobe Tech Support and explained the issue that concerns me and I have had a response from a senior expert on InDesign/Acrobat/Accessibility.
The issue is as follows:
When you prepare an InDesign document so that the generated tagged pdf is fully accessible for screen readers and the like (create TOC, include bookmarks, add document structure, tag untagged items, map styles to tags, tag uneccessary content as artifacts, include alt tags for images etc.) the bullets in bulleted lists cause the pdf to fail the Full Accessibility Check in Acrobat Pro. The full accessibility report will flag bullets as 'Inaccessible Page Content - the element is not contained within the document structure tree'. This is acceptable from the targeted end user audience (viz those with impaired vision using screen readers) because , as Acrobat states "Content that is not attached to the structure tree will not be available via assistive technology like screen readers." Well you don't really want the screen reader saying "Bullet" or similar everytime it comes across one, do you?
The problem is that the pdf "fails" the full accessibility check and when you are being paid to create fully accessible pdf's, this scares the client somewhat.
The solution:
I explained the above to the Adobe expert and asked if there was an efficient way, in InDesign CS2, to tag all "bullets" as artifacts so that they would be ignored by screen readers AND be seen as artifacts by the Acrobat Pro Full Accessibility Checker and hence pass the check. His answer was NO. I said in the past I had tediously, laboriously gone through the documents in Acrobat pro and marked every bullet as 'background' (= an artifact) to make it pass the Full access checker successfully. Surely, I asked, there must be a simpler way to do this? No, was his answer! "It's extremely cumbersome... but it's the only way"
Aaaahhh.

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.

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.

PDF problems in Acrobat 9 Pro

PDF problems in Acrobat 9 Pro
I'm using windows 7, 64 bit version
What can be the cause of dots, where underground otherwise white appearance with small black dots.
They do not come with the pressure. but is rather confusing.
Mox
PDF problems in Acrobat 9 Pro
here's an example of the dots, and yes I have updated acrobat

You're asking a lot of ancient Acrobat to work with an Office that never existed when it was made. "Just updated my office suite" is a massive change, and Window 8 didn't exist at that time either...

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!

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.

PDF problem part 2...

I guess a lot of people are having pdf problems.
When I export a pdf of a Travel Journal doc and view with adobe reader 7.0, the borders on the photos are not there.
What is the word on this?
As you can see I don't have Tiger /PDF-X.
Thanks

Not certain if this is quite the same thing, but.......
I have found problems when exporting to pdf, not when I open in Preview but when the person I am emailing the file to opens it in Acrobat, as all drop shadows are then lost, this makes professional printing difficult.
Resolved it for the moment by:
1. exporting to pdf as normal
2. using Graphic Converter which comes bundled with OSX to create a PSD file and sending that electronically. Slight problem was that the size of the file increased from 3mb to about 27mb, so had to download a free copy of Cyberduck ftp programme too. In fact saving it to jpeg was just about as good.
3. you do have to do one page at a time but it works.

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

Accessible PDF problem

Similar Messages

Maybe you are looking for