"Widget" annotation not nested inside a "Form" structure element PDF

[CyndyB836]

Hello all!

Reposting with different title hoping to get help. Cannot figure this out!

In the attached document I get an error in Pac3 for a Save and Reset button on page 1 of this document.

The error is: "Widget" annotation not nested inside a "Form" structure element PDF

Can someone please tell me how to fix this?

I've tried:

• Deleting the tags and the buttons and putting them back
• Deleting the buttons (this makes the ones on page 2 then have the same error); when I re-add in the buttons the error moves back to page 1 buttons
• Having a colleague do the same things.
• Using Foxit instead of Adobe (which oddly is the only way I can select options on the "Reset" button to select what fields I want to reset).
• I don't want to restart just to have the same issue at the end.

PLEASE HELP!!!!!

Thank you anyone who can help!

Cyndy

[ls_rbls]

Can you confirm what was the source document that produced this PDF?

Also, does the save button using any type of document-level script or an Acrobat built-in feature?

You also mentioned that on Foxit you're able to use a reset button, but your screenshot shows a button labeled as "Save".

Do all the button widgets assigned a unique field name in that PDF?

[CyndyB836]

Hi there!!

The source document was a Word doc. The Save and Reset buttons were added in Foxit using the push button feature.

There is no script atrtached both buttons use the Adobe built-in features.

Yes all the buttons have different names (usually the same name with a different number)

What I was speaking about in terms of the Reset button in Foxit is the popup in the screenshot below. In Foxit I am capable of selecting those boxes were as in Adobe I cannot.

Thank you for any help you can provide!

Cyndy

[ls_rbls]

Based on the screenshot provided, I think the problem with Acrobat is direactly related to the field objects naming conventions that were used with Foxt's JavaScript for Java, and how  the Adobe Acrobat's JavaScript core interpreter fails to interpret such field names. But this is my guess only... I may be entirely wrong.

But for the sake of proving my assumption, for example, I see a few field names in that list that have special characters combined with empty blank spaces.

Since the PDF field objects were originally created with Foxit PDF, I would assume that the Adobe Acrobat Core API JavaScript interpreter is having issues with field names and how they interact with other elements that are supposed to work well with Foxit PDF's own JavaScript for  Core API in C++, C#, and Java implementation, for example.

If the fields in that PDF have field calculations and is throwing errors, a quick fix would be to delete or edit  those fields with Adobe Acrobat and also rename the fields... IMHO.

[Ganesh_JI]

Hi Cyndy
Select that Tag and go to Find option in Accessibility Tag in that Select Unmarked Annotation from that list and click find it will go that button then click Tag Element and select Form. It will fix you issue. You need to move that Form tag to appropriate location

[Doug5FD4]

The first instruction - "Select that tag" is confusing. I'm looking at all of my accessibility tags, but the error I'm trying to fix (the first checkbox out of five in my document) and there are three tags I'm looking at, so I am at a loss of which of these three to select to follow these instructions.

When attempting to just guess and follow these instructions, I click FIND and select UNMARKED ANNOTATION and then click FIND IT and then click TAG ELEMENT but cannot select FORM from the dropdown menu.

[Ganesh_JI]

Hi 
Would you please share your files if possible we will have a look to fix your issue.

[Doug5FD4]

Wow. Thanks for taking a look at this.

I believe I have isolated the Widget/Nesting problem to section 2 of the attached PDF, where I have a list of 9 items (each with a fillable field), starting with School Name (1) and ending with (9) School Owner’s Name.

I’ve attached two versions of this same document with the same problem.

Ignore the older one if you wish or perhaps start there and I will ignore my subsequent attempts to fix it (filename ending = ADA 2.9 fillable.pdf). It is the first version of my COMPLIANT document turned FAILED by adding forms. The latest version (filename ending = ADA 2.9.7.pdf) shows several attempts to fix the problem – like adding links and an OBJR tag nested underneath it. I thought this might work, because this is the method I was able to make the checkbox forms in section 1 work. No luck so far.

Thanks in advance for any help.

[Ganesh_JI]

Hi

I just went through your PDF, in most of the places the Form was not in proper structure, Link tag is not necessary. I fixed 1 occurrence you need to fix rest of the form tag as below. Moreover in Form should not comes directly inside section tag.

[Doug5FD4]

Thanks so much! I will check this out.

[Doug5FD4]

Thanks. That did the trick.