Select Page
counselor

PAC 2024 – “Widget” annotation not within a “Form” structural element

PAC 2024 error details

appearance

category

Logical Structure > Structural Elements > Annotations > Nesting of “Widget” Annotations

Error message

“Widget” annotation not within a “Form” structural element

Matterhorn error condition

28-010 (A widget annotation is not subordinate to a form tag.)

explanation

The document contains an interactive form field that has not been tagged with a form.

solution in Adobe Acrobat Pro

solution approach

To fix the error, all form fields must be tagged with a form tag.

video tutorial

You are currently viewing a placeholder content from default. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

More Information

picture instructions

1. In the search bar, search for the tool “Automatically tag form fields” and open it

Note: Unfortunately, automatic tagging does not always work completely. In such a case, tagging must be done manually (see step 4 ff.).

2. In the search bar, search for the “Accessibility Tags” tool and open it

3. Find the automatically created form tag and, if necessary, correct the positioning within the structure tree

4. If the form tag was not created automatically in step 1, open the options of the tag structure tree >
Click "Search..."

5. Select “Unmarked Annotations” (in the “Search” dropdown) >
Click “Search” (until the form field is found)

6. Once the form field is found, click “Tag Element”

Note: The object found is usually highlighted in color in the document. This makes it relatively easy to see whether you have found the correct form field.

7. Select “Form” (in the “Type” dropdown) >
Click “OK”

8. Find the automatically created form tag and, if necessary, correct the positioning within the structure tree

As soon as you save the document and check it again with the PDF Accessibility Checker, the error message “Widget” annotation not within a “Form” structural element disappeared.

When saving, make sure to give the document a new name (e.g. Document Title_Rev2) and not oversave the previous version of the document. This way, you can go back to the previous version of the document if something goes wrong.

Contact, save time

Working smarter together – support that takes you further

Use tried-and-tested methods and smart tools to optimize your processes independently. We support you with knowledge, tips and solutions - and are available to help you with the final implementation if necessary. Let's talk!

Accessibility