Injecting AcroForm Radio Buttons

Hi Charles,

Thanks for the posting and for the good question! If you are implementing an accessible PDF with radio buttons, its field name/ID has a specific naming convention:

{groupName}[{indexWithinGroup}]

So in your case, Yes will be represented as Radio-Signer1[0] and No will be Radio-Signer1[1]

            {
              "binding": null,
              "validation": {
                "enum": [
                  "group1"
                ],
                "required": false
              },
              "id": "Radio-Signer1[0]",
              "subtype": "RADIO",
              "extract": true,
              "type": "INPUT",
              "value": "",
              "name": "Radio-Signer1[0]"
            },
            {
              "binding": null,
              "validation": {
                "enum": [
                  "group1"
                ],
                "required": false
              },
              "id": "Radio-Signer1[1]",
              "subtype": "RADIO",
              "extract": true,
              "type": "INPUT",
              "value": "",
              "name": "Radio-Signer1[1]"
            }

However during my test, I tried to revert the order - make No the first within the group and Yes the second, but the mapping result is still the same: Yes -> Radio-Signer1[0], No->Radio-Signer1[1]. I did another test to make No left top and Yes right bottom, but still the same. So if you preferred, I can create a support ticket on your behalf asking for a clarification on it.

On top of the discussions towards radio buttons, below are some of my suggestions and thoughts regarding to creating an ADA PDF/package:
- I saw you haven't tagged the PDF, don't forget to tag it before uploaded to an accessible package. I was testing with the attached PDF which was auto-tagged out of yours.

- From the best of my knowledge, OneSpan Sign document engine doesn't support List and Dropdown List forms.

- I also attached the complete package JSON I used for testing, just for your reference.

Duo

Thanks Duo -- above and beyond, much appreciated. Especially for the example documents, made things much easier to understand.

The indexing did the trick for the radio buttons. I believe they are indexed by the order they were first created on the form -- most likely I created the button that would become 'Yes' first.

It does seem that Lists are working as expected with this config:

{
                            "type":"INPUT",
                            "subtype":"LIST",
                            "name":"List-Signer1",
                            "id":"List-Signer1",
                            "value":"Option 2",
                            "validation": {
                                "required":true,
                                "enum": [
                                    "Option 1",
                                    "Option 2",
                                    "Option 3"
                                ]
                            }
                        },