E-mail List Archives
Thread: problems with dynamic forms created with LiveCycle when exported to pdf
Number of posts in this thread: 2 (In chronological order)
From: Farough, David (CFP/PSC)
Date: Thu, Sep 26 2019 8:32AM
Subject: problems with dynamic forms created with LiveCycle when exported to pdf
No previous message | Next message →
I have the following issues with our LiveCycle dynamic forms.
For some reason, when these forms are exported to PDF, the language settings for text and form fields are not indicated properly in the form. As a result, the screen reader reads all text using English phonetic rules . Listening to French text can be unpleasant and in some cases difficult to understand.
Forms which use radio buttons are also a problem because the checked status is not conveyed to the user. To make this point perfectly clear, all radio buttons are reported to be checked, even when they are not.
I have asked that the use of radio buttons be avoided with these forms and that dropdowns or list fields be used instead, but the client wants all options to be visible on the form when printing.
The client is willing to provide static versions of these forms which don't have these issues, so this may well be the outcome.
Needless to say, I am not happy with this prospect, but I don't see a better solution.
Any suggestions?
From: Karlen Communications
Date: Thu, Sep 26 2019 9:04AM
Subject: Re: problems with dynamic forms created with LiveCycle when exported to pdf
← Previous message | No next message
By default, LiveCycle now known as Form Designer creates XFA forms (dynamic
and not PDF). The language issue is a long standing one as LiveCycle/Form
Designer adds language by country rather than by language (Canada, United
States, France rather than English or French. This could be part of the
language issue.
The inaccurate reading of radio button Tooltips is also a long standing
issue with XFA forms from LiveCycle/Form Designer) even if you save the form
as a static PDF.
Both have been extensively logged as bugs over the years.
I recommend creating forms in Acrobat in order to have optimal access to any
accessibility features/techniques/tools.
Cheers, Karen
-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of
Farough, David (CFP/PSC)
Sent: Thursday, September 26, 2019 10:32 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] problems with dynamic forms created with LiveCycle when
exported to pdf
I have the following issues with our LiveCycle dynamic forms.
For some reason, when these forms are exported to PDF, the language
settings for text and form fields are not indicated properly in the form.
As a result, the screen reader reads all text using English phonetic rules .
Listening to French text can be unpleasant and in some cases difficult to
understand.
Forms which use radio buttons are also a problem because the checked status
is not conveyed to the user. To make this point perfectly clear, all
radio buttons are reported to be checked, even when they are not.
I have asked that the use of radio buttons be avoided with these forms and
that dropdowns or list fields be used instead, but the client wants all
options to be visible on the form when printing.
The client is willing to provide static versions of these forms which don't
have these issues, so this may well be the outcome.
Needless to say, I am not happy with this prospect, but I don't see a better
solution.
Any suggestions?
http://webaim.org/discussion/archives