WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: PDF - when spcifying the language of a form using Lifecycle, is it enough to use the locale property?

for

From: Rabab Gomaa
Date: Oct 15, 2013 4:50PM

Hi Logan and Birkir,=20
=20
I forwarded your emails to Ruth Vanwyk my colleague, she is working
with Adobe livecycle.=20
I am sending this reply on her behalf (please put Ruth in CC when
replying on this thread, she is not on WebAIM mailing list.) =20
=20
--------------
Forms created with Adobe LiveCycle ES are PDF-XFA forms. They cannot be
altered with Adobe Acrobat to set accessibility as the underlying
structure of the files is not compatible.
=20
The tags for the document and form objects should be set with Adobe
LiveCycle ES. When the file is saved to PDF (design files are often
saved in XDP and only saved as Adobe Dynamic XML form (*.pdf) when ready
to produce and before reader enabling), the dynamic PDF file needs to
have the =22Form Properties, Save Options, Generate Accessibility
Information (Tags) for Acrobat=22 option set to on.
=20
There is an bug which has been submitted to Adobe (October 2013) which
is preventing JAWS from switching the speaker to the language other than
English.
=20
I believe most people who work with LiveCycle ES have support from
Adobe, they should report their issues to Adobe through their support so
that bugs like this can be fixed.
=20
(For clarity=27s sake, what Logan Trafford is referring to setting in
Acrobat Pro is not possible with a PDF-XFA form, perhaps he is
referring to PDF ACRO forms. PDF ACRO forms are not developed/created
with LiveCycle ES.)
=20
Ruth
------------------
=20
Thank you,
Rabab
>>> =22Trafford, Logan=22 <Logan.Trafford=40ottawa.ca> 2013-09-24 2:03 PM
>>>
Hi Birkir

By reapplying the language in Acrobat Pro after the document has been
saved out is the only way we have been successful. I am also anxious to
know if there is a tried/true method within LiveCycle itself without
having to add the extra step. Like you, we have found that the language
attribute applied within LiveCycle does NOT get applied to the PDF when
saved.

Logan Trafford