This is a follow-up question from the previous question Case-study for hiding the optional fields?
I have taken all the responses from my previous question and I have come up with this mockup, here's the initial page:
Based on the study of Luke Wroblewski
Literally including the phrase “optional” after a label is much clearer than any visual symbol you could use to mean the same thing. Someone may always wonder 'what does this asterisk mean?' and have to go hunting for a legend that explains things.
I have removed the Indicator for the Required Fields and replaced it by adding and Indicator for the Optional Fields instead, since there were only one visible optional field in the initial page.
The optional fields has a business value so it cannot be removed, but I still hide it because "shorter forms are completed more often than longer forms" as pointed by @JohnGB from his previous answer.
I changed my approach from hiding the optional fields. Now I hide the whole section of the Emergency Contact Information. I also change the label for showing the optional field as
I want to fully secure my claims and fill-up the optional fields. This directly tell the user that the optional fields is for an optional feature (which is an additional security for their claims) as pointed by @Andy from his (or her?) previous answer, which might also encourage the user to actually enter values to those optional fields.
When expanded, the form would be like this:
From UX perspective, is this a good way to encourage the user to enter a value in the optional fields? Are there any UX study (or standards) about encouraging the user to enter a value in the optional fields?
I have found that The Queensland Government Site has a standard about this matter:
Checkpoint 15 - Optional form fields
Where it is not possible to remove an optional field, you must explain why the information is being collected and the situations under which it will be used. This will help users understand the value obtained from their effort and will encourage completion of these optional fields.