These forums are now Read Only. If you have an Acrobat question, ask questions and get help from one of our experts.

Accessibility checking tool for dynamic Livecycle PDFs

Forum Index > Accessibility > Accessibility checking tool for dynamic Livecycle PDFs
2011-04-04 07:50:22
skhalsa
Registered: Jun 4 2008
Posts: 21
Answered

Does anyone know of the a tool that will check the accessibility of dynamic Livecycle PDFs?
 
I'm attempting to make a case for using LiveCycle to create all are PDF forms since adding accessibility seems much easier to maintain than using the typical InDesign/Acrobat combo. However, I'm stuck on not being able to find a tool that will check the accessibility of a dynamic LiveCycle PDF and give a report of errors (similar to the Acrobat full check). I would also like to find one that has the ability to be customized with additional business rules if at all possible. All I can find online is best practices, which is helpful, but doesn't cover the scope of needing to check 100s of PDF forms without manually checking each one using JAWS.

My Product Information:
LiveCycle Designer, Windows
Top
2011-04-04 13:29:53
#1
daka630
Expert
Registered: Mar 1 2007
Posts: 1420
XFA forms that are "wrapped" in PDF would have to be saved to static forms from dynamic forms before being able to obtain a well-formed Tagged PDF. Accessiblity, via AT, comes from a PDF being a well-formed Tagged PDF.
.


Be well...

Top
2011-04-05 07:16:51
#2
skhalsa
Registered: Jun 4 2008
Posts: 21
So if I'm understanding this correctly... dynamic PDFs cannot be made accessible? LiveCycle documentation indicates that it can be so I'm confused.
Top
2011-04-05 09:36:30
#3
daka630
Expert
Registered: Mar 1 2007
Posts: 1420
Accepted Answer
LiveCycle Designer (ES, 7, 8, etc.) provides support for creating accessible XHTML files and PDF forms.
The 'PDF form' would be obtained via saving to an Adobe Static PDF form.
.
The various iterations of LCD afford the content author 'upfront' Tag management such that a Tagged output PDF can be produced.
The resultant PDF would then be provided the requisite grooming via Acrobat Professional to provide a well-formed structure tree, tab order, read order, etc.
.
fwiw (as you may already have these) -
.
LCD reference at Appligent
.
LCD Accessibilty Best Practice PDF
.
Accessible PDF discussion (S. Keegan)
.
Create Forms, LCD 8.2
.
In the above PDF, note item 14 on page 8 - going to a static PDF Form, although not always explicitely stated, is a requisite step in the work flow.
.
--| Build the content in LCD
--| Use the Tag management features provided by LCD
--| Save as a static PDF Form
--| 'Groom' with Acrobat Pro
--| If QC is SAT => deploy
--| if QC is UNSAT => return to LCD, fix, reiterate above
.
.

Be well...

Top