Hi DocuSign Community
We have noticed that the system or backend of DocuSign has changed--we first noticed this change in November of 2024. We have been using DocuSign for at least 3 years and our documents/envelopes use a lot of radio buttons. The User Experience used to be that the “auto-navigation” of the envelope would take the ‘signer’ to each individual RADIO BUTTON GROUP. As of Nov. 2024, we have noticed that something on the backend has changed and the auto-nav of our envelopes is requiring the ‘signer’ to “choose” and simultaneously required to click through EACH INDIVIDUAL RADIO BUTTON, regardless of whether they are choosing it or not. This is super frustrating and we have gone back and forth with the customer support team and they refuse to acknowledge that this is a change in the UX.
To illustrate the problem explained above. Please see a sample of a DocuSign envelope we might set up:

Pre November 2024
The Auto-Navigation would take the signer in the following order of the fields. For each of the Radio Button Groups, the ‘signer’ would only have to click “choose” for the pre-selected radio button or they could change their selection and click the “choose” button. They would only need to click through the auto-navigation with 6 clicks following the below sequence:
- “full Name”
- Signature
- Date Signed
- Radio Button Group for question 1
- Radio Button Group for question 2
- Radio Button Group for question 3
NOW
The auto-navigation takes the ‘signer’ and requires them to click the “choose” button FOR EACH RADIO BUTTON REGARDLESS OF WHETHER THEY ARE SELECTING THAT CHOICE.
- “full Name”
- Signature
- Date Signed
- Radio Button for oranges
- Radio button for Pizza
- Radio Button for Bagels
- Radio Button for Texas
- Radio Button for Georgia
- Radio Button for Hawaii
- Radio Button for 10
- Radio Button for 12
- ETC.
I hope you all can see where our frustration and confusion is coming from. Please let me know if you have any clarifying questions or if you have experienced a similar problem and have found a solution.
Thanks,
Abby