Accessibility: Problems with form fields

[Wolfgang Reckel]

01_Einzel-Lieferantenerklärung_DIHK-barrierefrei_Juli 2026.pdf

When you open the attached PDF and check the accessibility, the form fields are not compliant.

Does assigning the "Form" structure type in the Reading Order tool automatically create the required OBJR (Object Reference) linking the widget annotation to the document structure, or is an additional step required?

While examining the tag tree, I noticed that some Form tags contain an MCID (for example "21: Path"), whereas others contain no content at all and therefore have no MCID. Nevertheless, the accessibility checker reports "Form Fields Tagging – Failed" for all form fields.

Is PDF-XChange Editor expected to create a Form tag containing an MCID, or should it instead create an OBJR reference to the widget annotation according to the PDF/UA specification?

How can I solve the problem?

[Daniel - PDF-XChange]

Hello, Wolfgang Reckel

Thank you for the report, I saw your email on this topic come in yesterday - I am just awaiting a reply from the Dev team on the topic - but as soon as I have heard from them we will be back to you either by email or here.

Kind regards,

[Wolfgang Reckel]

Hello Dan,

Is there any reply from the Dev team to solve the issue?

Kind regards

Wolfgang

[Sean - PDF-XChange]

Hi Wolfgang,

We will get back to you as soon as we have something from the development team on this.

Kind regards,

[Wolfgang Reckel]

Hello,

I would like to kindly follow up on my question above regarding the accessibility check “Form Fields Tagging – Failed”.

I have not yet received a response and would appreciate any clarification on this issue.

In particular, I would like to know whether assigning the “Form” tag to each form field in the Reading Order/Structure tool is sufficient, or whether an additional structural association between the Form tag and the actual form field (widget annotation) is required.

All 11 form fields in my document:

● have been tagged as Form,
● have individual field names,
● have tooltips,
● and are included in the correct tab order.

Nevertheless, PDF-XChange Editor reports “Form Fields Tagging – Failed” for all 11 fields.

Could you please advise what exactly the accessibility checker expects for this test and how the reported issue can be corrected in PDF-XChange Editor?

Thank you very much in advance for your assistance.

Kind regards,

[Daniel - PDF-XChange]

Hello, Wolfgang Reckel

Sorry for the delay - I needed to confer with the Dev team about this, as the process is admittedly not particularly intuitive or obvious, and I had personally not interacted with these submenus as much as I should have.

To start, for this task, it is best to have the "Tags" and "fields" panes both opened - and enable the "Select fields" tool, from the Form tab.
Once you have those, perform your accessibility check as normal, then you can right click on one of the error entries, and choose "show in fields pane":

image.png

From there, click directly on the highlighted field, to "select" it, and then switch to the Tags pane, where you can use the dropdown menu, to "add tag from selection:

image(1).png

In the window that appears, choose "field" and add a description if needed:

image(2).png

You will need to do this with each error in the check, but they should all pass following that.

Kind regards,