Best practices for Adobe LiveCycle forms
There's a new document to check out if you develop interactive forms using LiveCycle Designer, whether you do so in an environment where you simple save the forms to PDF in Designer or you make use of Adobe's LiveCycle Forms ES product to produce your forms from the XDP XML file that LiveCycle creates. The new document is available at http://www.adobe.com/accessibility/products/livecycle/pdf/LiveCycle8_2AccessibilityGuidelines.pdf. Please let us know if you have comments, questions, or suggestions.
Comments
I've had trouble with the suggested use of "Custom Text". (NB: I'm generally working with a PDF from InDesign that I'm adding form elements to).
I often get issues where the parent tag of the form element is given alt text, masking the form element.
That causes form elements to become unusable in something like JAWs, and it is (correctly) identified as an issue by the Acrobat accessibility checker.
I've been sticking to using Camel case for the form label and making 'Name' the precedent thing.
Is there a better way?
Posted by: AlastairC | August 6, 2009 5:11 AM
Also, if you're creating a radio button group and you try to use the captions rather than item values, (as recommended), Livecycle gives an error about there being items with identical values.
Is that a problem?
Following the advice on "using a specified item value", I can't double-click the Object > Field > item, it's greyed out.
Did you mean the Binding tab?
Posted by: AlastairC | August 6, 2009 5:53 AM
As far as I know, it is impossible to add link objects or audio/video content to the form with LC Designer so sections 2.5.6 and 2.12 in the document doesn't give anything to the form developers using Designer. Hopefully someday it will be possible..
Posted by: M | August 6, 2009 6:36 AM
trying
Posted by: Zack | August 7, 2009 6:33 AM
This is extremely useful - thanks!
Posted by: Mike | August 8, 2009 5:29 AM