How to make an XDP accessible using form desinger

[SmrithiG1]

Hi,

I am new to Form Designer app and I have a requirement to make fields in an XDP file accessible. Is there any way to make fields accessible on an XDP file and not using a tagged PDF file. Thank you.

[Pranay_M]

Hi @SmrithiG1,

If you want to make the form accessible then you can use the Accessibility tab to set the specific tooltip for the the specified fields on the forms. You can also select the screen reader preference to set the values for the form fields.

Thanks

Pranay

[SmrithiG1]

Thank you I can see the Accessibility as you showed in form designer app.

Do you have an example for a tooltip script, on how to make a text field accessible. Thank you

[Vijay_Katoch]

You can add below snippet in initialize event of the field.

this.assist.toolTip = "Hello tooltip";

[SmrithiG1]

DO you have a example snippet for making a text field accessible, after initialization.

[Pranay_M]

Hi @SmrithiG1,

Can you please let me know the exact use case you are trying to achieve as Accessibility for the form is not dependent on the field or form initialization. It is mostly concerned with the readability of the form and works at the form level.

Thanks
Pranay 

[Khushwant_Singh]

@SmrithiG1, I just wanted to check in—has the issue been resolved, or are you still in the process of gathering information?

[SmrithiG1]

No, the issue is not yet resolved, as we are not able to make XDP accessible just by adding tooltip assist. 

[Pranay_M]

Hi @SmrithiG1,

To make the XDP accessible you only have this method. INcase you have additional queries request you raise a support case with us and the team will be happy to assist you based on your usecase.

Thanks
Pranay 

[workflowuser]

The rendered pdf will be accessible 

[SmrithiG1]

Happy to hear that, is there any way I can message you separately to check on the issue? May be it could be a minor one. The things I tried:

1. Added this.assit.toolTip= "message " for a single field on XDP using form designer.

2. save the file as PDF on my machine

3. opened it using acrobat Pro to check if the tags are added, and they are not.

Please check and let me know if its correct, as this a huge blocker for us right now. Appreciate any support on this matter. 

[Pranay_M]

Hi @SmrithiG1,

Can you please attach the Accessibility report from Acrobat and the PDF to the chat and I can review the information that you have shared.

Thanks
Pranay

[SmrithiG1]

Sure, I will share it soon. 

[SmrithiG1]

For the generated PDF, I can see that many features in accessibility check are disabled. So, I am unable to send the report. Trying to check why the features are disabled for the PDF. 

[VijaySr1]

Hi @SmrithiG1 ,

I have reviewed the thread. Could you please try the following options:

1. Write the script to runAt server, then save the output as a static PDF. Verify if it functions as expected.
2. If the above does not work, add a tooltip via the property sheet, save it again as a static PDF, and check if the issue persists.
3. If neither approach resolves the issue, kindly share the PDF files generated during the above steps for further analysis.

Query:
Could you please clarify the type of PDF you are aiming for—static or dynamic?

Thank you.

[SmrithiG1]

Hi @VijaySr1 , Thanks a lot for your suggestion. 

On saving the XDP as static PDF, i could see the accessibility tags when opened in Acrobat Pro.

I was always trying to save it as dynamic PDF, because as per our use case, the generated PDF can be edited later for updating the form data.

One thing I noticed as saving as a static PDF, is that, the PDF is still dynamic. i.e I can still edit the PDF and save the values entered in each field. 

[SmrithiG1]

Could you please let me know what is the difference when we save it as static and when we save it as dynamic

The reason for asking is that, we are trying to programmatically render the PDF from XDP / Adaptive form and trying to make it accessible.  

[SmrithiG1]

Hi @VijaySr1 , I can see the tags in static PDF for field labels, but not for field values. Do you know why this is happening. Can you please help understand how to make the field values also tagged in PDF? Thank you.