E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 4 (In chronological order)

From: Birkir R. Gunnarsson
Date: Tue, Sep 24 2013 9:33AM
Subject: PDF - when spcifying the language of a form using Lifecycle, is it enough to use the locale property?
No previous message | Next message →

Greetings

The conundrum of the day for me is, what needs to happen when
designing forms in Adobe Lifecycle to make sure that the document
language is communicated correctly to screen readers when users open
the form.
There is the mention of the locale of the form which would be fine if
form was an English form, but what if I wanted to design a French or
Icelandic form in Lifecycle, which property would I have to define and
how to ensure that the language is communicated to assistive
technologies.
Thanks
-Birkir
Birkir R. Gunnarsson
Accessibility Subject Matter Expert | Deque Systems

From: Trafford, Logan
Date: Tue, Sep 24 2013 12:03PM
Subject: Re: PDF - when spcifying the language of a form using Lifecycle, is it enough to use the locale property?
← Previous message | Next message →

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

-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: September 24, 2013 11:34 AM
To: WebAIM Discussion List
Subject: [WebAIM] PDF - when spcifying the language of a form using Lifecycle, is it enough to use the locale property?

Greetings

The conundrum of the day for me is, what needs to happen when designing forms in Adobe Lifecycle to make sure that the document language is communicated correctly to screen readers when users open the form.
There is the mention of the locale of the form which would be fine if form was an English form, but what if I wanted to design a French or Icelandic form in Lifecycle, which property would I have to define and how to ensure that the language is communicated to assistive technologies.
Thanks
-Birkir
Birkir R. Gunnarsson
Accessibility Subject Matter Expert | Deque Systems This e-mail originates from the City of Ottawa e-mail system. Any
distribution, use or copying of this e-mail or the information it
contains by other than the intended recipient(s) is unauthorized.
If you are not the intended recipient, please notify me at the
telephone number shown above or by return e-mail and delete
this communication and any copy immediately. Thank you.

Le présent courriel a été expédié par le système de courriels de
la Ville d'Ottawa. Toute distribution, utilisation ou
reproduction du courriel ou des renseignements qui s'y trouvent
par une personne autre que son destinataire prévu est interdite.
Si vous avez reçu le message par erreur, veuillez m'en aviser par
téléphone (au numéro précité) ou par courriel, puis supprimer
sans délai la version originale de la communication ainsi que
toutes ses copies. Je vous remercie de votre collaboration.

From: Andrew Kirkpatrick
Date: Tue, Sep 24 2013 2:25PM
Subject: Re: PDF - when spcifying the language of a form using Lifecycle, is it enough to use the locale property?
← Previous message | Next message →

On each page of the form you will probably have a main subform. Set the language for that in the accessibility palette and you're good to go as all objects within that subform will use the same language unless you specify that one of those objects needs a different language to match content in a different language.

You can think of it in a similar way to language in an HTML file. The difference is that when you assign the language at the form level (similar to assigning the language on the HTML element) the language setting isn't being set in the PDF. However, if you set the language on the top subform (like setting the language on the HTML body or top-level DIV element) then all content within that structure will share the same language.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe Systems

= EMAIL ADDRESS REMOVED =
http://twitter.com/awkawk
http://blogs.adobe.com/accessibility


-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Trafford, Logan
Sent: Tuesday, September 24, 2013 2:04 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] PDF - when spcifying the language of a form using Lifecycle, is it enough to use the locale property?

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

-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: September 24, 2013 11:34 AM
To: WebAIM Discussion List
Subject: [WebAIM] PDF - when spcifying the language of a form using Lifecycle, is it enough to use the locale property?

Greetings

The conundrum of the day for me is, what needs to happen when designing forms in Adobe Lifecycle to make sure that the document language is communicated correctly to screen readers when users open the form.
There is the mention of the locale of the form which would be fine if form was an English form, but what if I wanted to design a French or Icelandic form in Lifecycle, which property would I have to define and how to ensure that the language is communicated to assistive technologies.
Thanks
-Birkir
Birkir R. Gunnarsson
Accessibility Subject Matter Expert | Deque Systems This e-mail originates from the City of Ottawa e-mail system. Any distribution, use or copying of this e-mail or the information it contains by other than the intended recipient(s) is unauthorized.
If you are not the intended recipient, please notify me at the telephone number shown above or by return e-mail and delete this communication and any copy immediately. Thank you.

Le présent courriel a été expédié par le système de courriels de la Ville d'Ottawa. Toute distribution, utilisation ou reproduction du courriel ou des renseignements qui s'y trouvent par une personne autre que son destinataire prévu est interdite.
Si vous avez reçu le message par erreur, veuillez m'en aviser par téléphone (au numéro précité) ou par courriel, puis supprimer sans délai la version originale de la communication ainsi que toutes ses copies. Je vous remercie de votre collaboration.

From: Rabab Gomaa
Date: Tue, Oct 15 2013 4:50PM
Subject: Re: PDF - when spcifying the language of a form using Lifecycle, is it enough to use the locale property?
← Previous message | No next message

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

-----Original Message-----
From: webaim-forum-bounces=40list.webaim.org
=5Bmailto:webaim-forum-bounces=40list.webaim.org=5D On Behalf Of Birkir R.
Gunnarsson
Sent: September 24, 2013 11:34 AM
To: WebAIM Discussion List
Subject: =5BWebAIM=5D PDF - when spcifying the language of a form using
Lifecycle, is it enough to use the locale property?

Greetings

The conundrum of the day for me is, what needs to happen when designing
forms in Adobe Lifecycle to make sure that the document language is
communicated correctly to screen readers when users open the form.
There is the mention of the locale of the form which would be fine if
form was an English form, but what if I wanted to design a French or
Icelandic form in Lifecycle, which property would I have to define and
how to ensure that the language is communicated to assistive
technologies.
Thanks
-Birkir
Birkir R. Gunnarsson
Accessibility Subject Matter Expert =7C Deque Systems
messages to webaim-forum=40list.webaim.org


This e-mail originates from the City of Ottawa e-mail system. Any=20
distribution, use or copying of this e-mail or the information it=20
contains by other than the intended recipient(s) is unauthorized.=20
If you are not the intended recipient, please notify me at the=20
telephone number shown above or by return e-mail and delete=20
this communication and any copy immediately. Thank you.

Le pr=C3=A9sent courriel a =C3=A9t=C3=A9 exp=C3=A9di=C3=A9 par le =
syst=C3=A8me de courriels de=20
la Ville d=27Ottawa. Toute distribution, utilisation ou=20
reproduction du courriel ou des renseignements qui s=27y trouvent=20
par une personne autre que son destinataire pr=C3=A9vu est interdite.=20
Si vous avez re=C3=A7u le message par erreur, veuillez m=27en aviser =
par=20
t=C3=A9l=C3=A9phone (au num=C3=A9ro pr=C3=A9cit=C3=A9) ou par courriel, =
puis supprimer=20
sans d=C3=A9lai la version originale de la communication ainsi que=20
toutes ses copies. Je vous remercie de votre collaboration.


n, visit http://list.webaim.org/