Placement of More Information/Help Icon button for Radio ButtonsReplace radio-input with “buttons”? (web forms)Radio Buttons in the header?Form design and placement of action buttonsUse of Radio Buttons (Identification Context)Best placement for “ultimate” page actionsBest approach to presenting collapsible/expandable panels with radio button headersHow to show static (user initiated) and dynamic help text for radio buttons and dropdowns?Placement for next, prev and complete form later actionsIs it better to use Checkboxes or Radio Buttons, when there are two or more fields and at least one of them must be filled out to pass validation?Should read-only fields hide or disable icons?
How can I make a cone from a cube and view the cube with different angles?
Why "Having chlorophyll without photosynthesis is actually very dangerous" and "like living with a bomb"?
Why doesn't H₄O²⁺ exist?
US citizen flying to France today and my passport expires in less than 2 months
Why is 150k or 200k jobs considered good when there's 300k+ births a month?
Fencing style for blades that can attack from a distance
a relationship between local compactness and closure
What variety is this tomato with long, milky green branches?
What do the dots in this tr command do: tr .............A-Z A-ZA-Z <<< "JVPQBOV" (with 13 dots)
How does one intimidate enemies without having the capacity for violence?
Pattern match does not work in bash script
Smoothness of finite-dimensional functional calculus
What typically incentivizes a professor to change jobs to a lower ranking university?
Why does Kotter return in Welcome Back Kotter?
What's the point of deactivating Num Lock on login screens?
Why not use SQL instead of GraphQL?
How to add double frame in tcolorbox?
Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?
How to calculate partition Start End Sector?
How to put math symbol rotated with 90 degree in table cell?
What's the output of a record cartridge playing an out-of-speed record
Mage Armor with Defense fighting style (for Adventurers League bladeslinger)
What would happen to a modern skyscraper if it rains micro blackholes?
Are the number of citations and number of published articles the most important criteria for a tenure promotion?
Placement of More Information/Help Icon button for Radio Buttons
Replace radio-input with “buttons”? (web forms)Radio Buttons in the header?Form design and placement of action buttonsUse of Radio Buttons (Identification Context)Best placement for “ultimate” page actionsBest approach to presenting collapsible/expandable panels with radio button headersHow to show static (user initiated) and dynamic help text for radio buttons and dropdowns?Placement for next, prev and complete form later actionsIs it better to use Checkboxes or Radio Buttons, when there are two or more fields and at least one of them must be filled out to pass validation?Should read-only fields hide or disable icons?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Throughout our system we are going to be standardizing when and how more information/help is used on specific input fields.
In general the standard will be to have the icon/button follow the field like so:

I am wondering where the placement should be for radio buttons? The more information/help will be referencing the radio set as a whole.
These are the potential options and I am wondering what would follow best practices for radio buttons and more information/help?

buttons input-fields radio-buttons help placement
add a comment |
Throughout our system we are going to be standardizing when and how more information/help is used on specific input fields.
In general the standard will be to have the icon/button follow the field like so:

I am wondering where the placement should be for radio buttons? The more information/help will be referencing the radio set as a whole.
These are the potential options and I am wondering what would follow best practices for radio buttons and more information/help?

buttons input-fields radio-buttons help placement
How about below main label?
– Yong Quan
Apr 3 at 2:30
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.
– L. Lemmer
2 days ago
add a comment |
Throughout our system we are going to be standardizing when and how more information/help is used on specific input fields.
In general the standard will be to have the icon/button follow the field like so:

I am wondering where the placement should be for radio buttons? The more information/help will be referencing the radio set as a whole.
These are the potential options and I am wondering what would follow best practices for radio buttons and more information/help?

buttons input-fields radio-buttons help placement
Throughout our system we are going to be standardizing when and how more information/help is used on specific input fields.
In general the standard will be to have the icon/button follow the field like so:

I am wondering where the placement should be for radio buttons? The more information/help will be referencing the radio set as a whole.
These are the potential options and I am wondering what would follow best practices for radio buttons and more information/help?

buttons input-fields radio-buttons help placement
buttons input-fields radio-buttons help placement
asked Apr 2 at 15:33
L. LemmerL. Lemmer
1268
1268
How about below main label?
– Yong Quan
Apr 3 at 2:30
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.
– L. Lemmer
2 days ago
add a comment |
How about below main label?
– Yong Quan
Apr 3 at 2:30
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.
– L. Lemmer
2 days ago
How about below main label?
– Yong Quan
Apr 3 at 2:30
How about below main label?
– Yong Quan
Apr 3 at 2:30
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.
– L. Lemmer
2 days ago
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.
– L. Lemmer
2 days ago
add a comment |
5 Answers
5
active
oldest
votes
There is a difference in the understanding at the level of the concept (label) vs. the available choices. You may need a couple of patterns for flexibility.
If you are trying to impart understanding regarding the label and it's choices, you can put the i close to the label, and give some info on hover, with some links to documentation for further understanding if need be.
Think of scale and complexity, and have a resilient system.
I realize I'm not giving a straightforward 'Do it this way!', but providing a way of thinking of prioritized contexts, so you have some flexibility. Here's a couple of situations I've seen come up.
Unfamiliar label, few choices that can be somewhat familiar:

Unfamiliar label, many choices, some complex:
Either way, the ? (or i) is close to what it needs to describe.

If you top align your forms:

You'll also see this in some dropdown menus (which function the same as a long list of radio buttons). Here's an example from Google Analytics:

add a comment |
Think of a logical order and good placement

Instead you may use this:

UPDATE
Based on the comments from the OP (Original Poster):
"So I am limited to the options that I have provided. It's standard in
our system to have the controls go to the right of the label, not
beneath it"
Two Scenarios:
1- You are NOT limited on horizontal space:

2- You are limited on horizontal space:

*Last option maybe to underline the Label itself, and when it is hovered, you display the Tooltip. The underline would be your visual clue here (it is not as clear as the info icon, and some might confuse it as a clickable text)
END OF UPDATE
So I am limited to the options that I have provided. It's standard in our system to have the controls go to the right of the label, not beneath it (like you have in your suggestion). If all the options I presented are going to provide a poor user experience then maybe this as a standard: If a more information needs to be used for a radio set (it should be uncommon) instead of using a radio set use a combo box. Thoughts?
– L. Lemmer
Apr 2 at 20:24
I updated the answer accordingly.
– Mo'ath
yesterday
add a comment |
I would use the info at the right centered in the label.
Why? The wrist tends to the right so, It will be easier for the user to click and it doesnt break the layout of the questions.
Radio buttons works best if they are vertically align because the eye can scan from top to bottom than going from left to right, going down and to the left and continuing scanning.
BUT, after testing it, if the user is prompt to check the info tooltip, use it at left, aligned to the radio buttons. You can see the mouse movement in each case.

You can read more about the Fitt's Law here: https://en.wikipedia.org/wiki/Fitts%27s_law.
if you use a grid for the label and the radio buttons, the user will learn the pattern and complete the form asap.
In my opinion, it depends about the frequency of tooltip use. If the user are going to use this information frequently, left, if not, right.
New contributor
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
After radio options on the top.
Given your additional context that you can't stack label and options, I think this would be ideal in context of other inputs. Users would be used to seeing it there.
It would be more consistent than vertical centering.
New contributor
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Can you please provide a little screenshot of where you think it works better?
– Mo'ath
2 days ago
@Mo'ath See the original screenshot. The third element in the screenshot. "After radio options on the top." which you'll see is visually similar to the existing options.
– Dustin Graham
yesterday
add a comment |
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.

Hmm, this does not answer a question reads: "Placement of More Information/Help Icon button for RADIO BUTTONS". You are changing the controller completely although you earlier mentioned that you cannot make the change on the Radio buttons structure and you are limited. What confuses me though is do you want the info icon to provide help for the Label or the radio button options? or both? Your design (combo-box) provides help for the radio button options.
– Mo'ath
yesterday
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "102"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f124819%2fplacement-of-more-information-help-icon-button-for-radio-buttons%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is a difference in the understanding at the level of the concept (label) vs. the available choices. You may need a couple of patterns for flexibility.
If you are trying to impart understanding regarding the label and it's choices, you can put the i close to the label, and give some info on hover, with some links to documentation for further understanding if need be.
Think of scale and complexity, and have a resilient system.
I realize I'm not giving a straightforward 'Do it this way!', but providing a way of thinking of prioritized contexts, so you have some flexibility. Here's a couple of situations I've seen come up.
Unfamiliar label, few choices that can be somewhat familiar:

Unfamiliar label, many choices, some complex:
Either way, the ? (or i) is close to what it needs to describe.

If you top align your forms:

You'll also see this in some dropdown menus (which function the same as a long list of radio buttons). Here's an example from Google Analytics:

add a comment |
There is a difference in the understanding at the level of the concept (label) vs. the available choices. You may need a couple of patterns for flexibility.
If you are trying to impart understanding regarding the label and it's choices, you can put the i close to the label, and give some info on hover, with some links to documentation for further understanding if need be.
Think of scale and complexity, and have a resilient system.
I realize I'm not giving a straightforward 'Do it this way!', but providing a way of thinking of prioritized contexts, so you have some flexibility. Here's a couple of situations I've seen come up.
Unfamiliar label, few choices that can be somewhat familiar:

Unfamiliar label, many choices, some complex:
Either way, the ? (or i) is close to what it needs to describe.

If you top align your forms:

You'll also see this in some dropdown menus (which function the same as a long list of radio buttons). Here's an example from Google Analytics:

add a comment |
There is a difference in the understanding at the level of the concept (label) vs. the available choices. You may need a couple of patterns for flexibility.
If you are trying to impart understanding regarding the label and it's choices, you can put the i close to the label, and give some info on hover, with some links to documentation for further understanding if need be.
Think of scale and complexity, and have a resilient system.
I realize I'm not giving a straightforward 'Do it this way!', but providing a way of thinking of prioritized contexts, so you have some flexibility. Here's a couple of situations I've seen come up.
Unfamiliar label, few choices that can be somewhat familiar:

Unfamiliar label, many choices, some complex:
Either way, the ? (or i) is close to what it needs to describe.

If you top align your forms:

You'll also see this in some dropdown menus (which function the same as a long list of radio buttons). Here's an example from Google Analytics:

There is a difference in the understanding at the level of the concept (label) vs. the available choices. You may need a couple of patterns for flexibility.
If you are trying to impart understanding regarding the label and it's choices, you can put the i close to the label, and give some info on hover, with some links to documentation for further understanding if need be.
Think of scale and complexity, and have a resilient system.
I realize I'm not giving a straightforward 'Do it this way!', but providing a way of thinking of prioritized contexts, so you have some flexibility. Here's a couple of situations I've seen come up.
Unfamiliar label, few choices that can be somewhat familiar:

Unfamiliar label, many choices, some complex:
Either way, the ? (or i) is close to what it needs to describe.

If you top align your forms:

You'll also see this in some dropdown menus (which function the same as a long list of radio buttons). Here's an example from Google Analytics:

edited Apr 2 at 19:30
answered Apr 2 at 16:05
Mike MMike M
11.5k12433
11.5k12433
add a comment |
add a comment |
Think of a logical order and good placement

Instead you may use this:

UPDATE
Based on the comments from the OP (Original Poster):
"So I am limited to the options that I have provided. It's standard in
our system to have the controls go to the right of the label, not
beneath it"
Two Scenarios:
1- You are NOT limited on horizontal space:

2- You are limited on horizontal space:

*Last option maybe to underline the Label itself, and when it is hovered, you display the Tooltip. The underline would be your visual clue here (it is not as clear as the info icon, and some might confuse it as a clickable text)
END OF UPDATE
So I am limited to the options that I have provided. It's standard in our system to have the controls go to the right of the label, not beneath it (like you have in your suggestion). If all the options I presented are going to provide a poor user experience then maybe this as a standard: If a more information needs to be used for a radio set (it should be uncommon) instead of using a radio set use a combo box. Thoughts?
– L. Lemmer
Apr 2 at 20:24
I updated the answer accordingly.
– Mo'ath
yesterday
add a comment |
Think of a logical order and good placement

Instead you may use this:

UPDATE
Based on the comments from the OP (Original Poster):
"So I am limited to the options that I have provided. It's standard in
our system to have the controls go to the right of the label, not
beneath it"
Two Scenarios:
1- You are NOT limited on horizontal space:

2- You are limited on horizontal space:

*Last option maybe to underline the Label itself, and when it is hovered, you display the Tooltip. The underline would be your visual clue here (it is not as clear as the info icon, and some might confuse it as a clickable text)
END OF UPDATE
So I am limited to the options that I have provided. It's standard in our system to have the controls go to the right of the label, not beneath it (like you have in your suggestion). If all the options I presented are going to provide a poor user experience then maybe this as a standard: If a more information needs to be used for a radio set (it should be uncommon) instead of using a radio set use a combo box. Thoughts?
– L. Lemmer
Apr 2 at 20:24
I updated the answer accordingly.
– Mo'ath
yesterday
add a comment |
Think of a logical order and good placement

Instead you may use this:

UPDATE
Based on the comments from the OP (Original Poster):
"So I am limited to the options that I have provided. It's standard in
our system to have the controls go to the right of the label, not
beneath it"
Two Scenarios:
1- You are NOT limited on horizontal space:

2- You are limited on horizontal space:

*Last option maybe to underline the Label itself, and when it is hovered, you display the Tooltip. The underline would be your visual clue here (it is not as clear as the info icon, and some might confuse it as a clickable text)
END OF UPDATE
Think of a logical order and good placement

Instead you may use this:

UPDATE
Based on the comments from the OP (Original Poster):
"So I am limited to the options that I have provided. It's standard in
our system to have the controls go to the right of the label, not
beneath it"
Two Scenarios:
1- You are NOT limited on horizontal space:

2- You are limited on horizontal space:

*Last option maybe to underline the Label itself, and when it is hovered, you display the Tooltip. The underline would be your visual clue here (it is not as clear as the info icon, and some might confuse it as a clickable text)
END OF UPDATE
edited yesterday
answered Apr 2 at 19:14
Mo'athMo'ath
625213
625213
So I am limited to the options that I have provided. It's standard in our system to have the controls go to the right of the label, not beneath it (like you have in your suggestion). If all the options I presented are going to provide a poor user experience then maybe this as a standard: If a more information needs to be used for a radio set (it should be uncommon) instead of using a radio set use a combo box. Thoughts?
– L. Lemmer
Apr 2 at 20:24
I updated the answer accordingly.
– Mo'ath
yesterday
add a comment |
So I am limited to the options that I have provided. It's standard in our system to have the controls go to the right of the label, not beneath it (like you have in your suggestion). If all the options I presented are going to provide a poor user experience then maybe this as a standard: If a more information needs to be used for a radio set (it should be uncommon) instead of using a radio set use a combo box. Thoughts?
– L. Lemmer
Apr 2 at 20:24
I updated the answer accordingly.
– Mo'ath
yesterday
So I am limited to the options that I have provided. It's standard in our system to have the controls go to the right of the label, not beneath it (like you have in your suggestion). If all the options I presented are going to provide a poor user experience then maybe this as a standard: If a more information needs to be used for a radio set (it should be uncommon) instead of using a radio set use a combo box. Thoughts?
– L. Lemmer
Apr 2 at 20:24
So I am limited to the options that I have provided. It's standard in our system to have the controls go to the right of the label, not beneath it (like you have in your suggestion). If all the options I presented are going to provide a poor user experience then maybe this as a standard: If a more information needs to be used for a radio set (it should be uncommon) instead of using a radio set use a combo box. Thoughts?
– L. Lemmer
Apr 2 at 20:24
I updated the answer accordingly.
– Mo'ath
yesterday
I updated the answer accordingly.
– Mo'ath
yesterday
add a comment |
I would use the info at the right centered in the label.
Why? The wrist tends to the right so, It will be easier for the user to click and it doesnt break the layout of the questions.
Radio buttons works best if they are vertically align because the eye can scan from top to bottom than going from left to right, going down and to the left and continuing scanning.
BUT, after testing it, if the user is prompt to check the info tooltip, use it at left, aligned to the radio buttons. You can see the mouse movement in each case.

You can read more about the Fitt's Law here: https://en.wikipedia.org/wiki/Fitts%27s_law.
if you use a grid for the label and the radio buttons, the user will learn the pattern and complete the form asap.
In my opinion, it depends about the frequency of tooltip use. If the user are going to use this information frequently, left, if not, right.
New contributor
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I would use the info at the right centered in the label.
Why? The wrist tends to the right so, It will be easier for the user to click and it doesnt break the layout of the questions.
Radio buttons works best if they are vertically align because the eye can scan from top to bottom than going from left to right, going down and to the left and continuing scanning.
BUT, after testing it, if the user is prompt to check the info tooltip, use it at left, aligned to the radio buttons. You can see the mouse movement in each case.

You can read more about the Fitt's Law here: https://en.wikipedia.org/wiki/Fitts%27s_law.
if you use a grid for the label and the radio buttons, the user will learn the pattern and complete the form asap.
In my opinion, it depends about the frequency of tooltip use. If the user are going to use this information frequently, left, if not, right.
New contributor
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I would use the info at the right centered in the label.
Why? The wrist tends to the right so, It will be easier for the user to click and it doesnt break the layout of the questions.
Radio buttons works best if they are vertically align because the eye can scan from top to bottom than going from left to right, going down and to the left and continuing scanning.
BUT, after testing it, if the user is prompt to check the info tooltip, use it at left, aligned to the radio buttons. You can see the mouse movement in each case.

You can read more about the Fitt's Law here: https://en.wikipedia.org/wiki/Fitts%27s_law.
if you use a grid for the label and the radio buttons, the user will learn the pattern and complete the form asap.
In my opinion, it depends about the frequency of tooltip use. If the user are going to use this information frequently, left, if not, right.
New contributor
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I would use the info at the right centered in the label.
Why? The wrist tends to the right so, It will be easier for the user to click and it doesnt break the layout of the questions.
Radio buttons works best if they are vertically align because the eye can scan from top to bottom than going from left to right, going down and to the left and continuing scanning.
BUT, after testing it, if the user is prompt to check the info tooltip, use it at left, aligned to the radio buttons. You can see the mouse movement in each case.

You can read more about the Fitt's Law here: https://en.wikipedia.org/wiki/Fitts%27s_law.
if you use a grid for the label and the radio buttons, the user will learn the pattern and complete the form asap.
In my opinion, it depends about the frequency of tooltip use. If the user are going to use this information frequently, left, if not, right.
New contributor
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 2 at 16:02
New contributor
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Apr 2 at 15:56
Juan Jesús MilloJuan Jesús Millo
607110
607110
New contributor
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Juan Jesús Millo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
After radio options on the top.
Given your additional context that you can't stack label and options, I think this would be ideal in context of other inputs. Users would be used to seeing it there.
It would be more consistent than vertical centering.
New contributor
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Can you please provide a little screenshot of where you think it works better?
– Mo'ath
2 days ago
@Mo'ath See the original screenshot. The third element in the screenshot. "After radio options on the top." which you'll see is visually similar to the existing options.
– Dustin Graham
yesterday
add a comment |
After radio options on the top.
Given your additional context that you can't stack label and options, I think this would be ideal in context of other inputs. Users would be used to seeing it there.
It would be more consistent than vertical centering.
New contributor
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Can you please provide a little screenshot of where you think it works better?
– Mo'ath
2 days ago
@Mo'ath See the original screenshot. The third element in the screenshot. "After radio options on the top." which you'll see is visually similar to the existing options.
– Dustin Graham
yesterday
add a comment |
After radio options on the top.
Given your additional context that you can't stack label and options, I think this would be ideal in context of other inputs. Users would be used to seeing it there.
It would be more consistent than vertical centering.
New contributor
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
After radio options on the top.
Given your additional context that you can't stack label and options, I think this would be ideal in context of other inputs. Users would be used to seeing it there.
It would be more consistent than vertical centering.
New contributor
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
Dustin GrahamDustin Graham
1012
1012
New contributor
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Dustin Graham is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Can you please provide a little screenshot of where you think it works better?
– Mo'ath
2 days ago
@Mo'ath See the original screenshot. The third element in the screenshot. "After radio options on the top." which you'll see is visually similar to the existing options.
– Dustin Graham
yesterday
add a comment |
Can you please provide a little screenshot of where you think it works better?
– Mo'ath
2 days ago
@Mo'ath See the original screenshot. The third element in the screenshot. "After radio options on the top." which you'll see is visually similar to the existing options.
– Dustin Graham
yesterday
Can you please provide a little screenshot of where you think it works better?
– Mo'ath
2 days ago
Can you please provide a little screenshot of where you think it works better?
– Mo'ath
2 days ago
@Mo'ath See the original screenshot. The third element in the screenshot. "After radio options on the top." which you'll see is visually similar to the existing options.
– Dustin Graham
yesterday
@Mo'ath See the original screenshot. The third element in the screenshot. "After radio options on the top." which you'll see is visually similar to the existing options.
– Dustin Graham
yesterday
add a comment |
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.

Hmm, this does not answer a question reads: "Placement of More Information/Help Icon button for RADIO BUTTONS". You are changing the controller completely although you earlier mentioned that you cannot make the change on the Radio buttons structure and you are limited. What confuses me though is do you want the info icon to provide help for the Label or the radio button options? or both? Your design (combo-box) provides help for the radio button options.
– Mo'ath
yesterday
add a comment |
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.

Hmm, this does not answer a question reads: "Placement of More Information/Help Icon button for RADIO BUTTONS". You are changing the controller completely although you earlier mentioned that you cannot make the change on the Radio buttons structure and you are limited. What confuses me though is do you want the info icon to provide help for the Label or the radio button options? or both? Your design (combo-box) provides help for the radio button options.
– Mo'ath
yesterday
add a comment |
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.

What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.

answered 2 days ago
L. LemmerL. Lemmer
1268
1268
Hmm, this does not answer a question reads: "Placement of More Information/Help Icon button for RADIO BUTTONS". You are changing the controller completely although you earlier mentioned that you cannot make the change on the Radio buttons structure and you are limited. What confuses me though is do you want the info icon to provide help for the Label or the radio button options? or both? Your design (combo-box) provides help for the radio button options.
– Mo'ath
yesterday
add a comment |
Hmm, this does not answer a question reads: "Placement of More Information/Help Icon button for RADIO BUTTONS". You are changing the controller completely although you earlier mentioned that you cannot make the change on the Radio buttons structure and you are limited. What confuses me though is do you want the info icon to provide help for the Label or the radio button options? or both? Your design (combo-box) provides help for the radio button options.
– Mo'ath
yesterday
Hmm, this does not answer a question reads: "Placement of More Information/Help Icon button for RADIO BUTTONS". You are changing the controller completely although you earlier mentioned that you cannot make the change on the Radio buttons structure and you are limited. What confuses me though is do you want the info icon to provide help for the Label or the radio button options? or both? Your design (combo-box) provides help for the radio button options.
– Mo'ath
yesterday
Hmm, this does not answer a question reads: "Placement of More Information/Help Icon button for RADIO BUTTONS". You are changing the controller completely although you earlier mentioned that you cannot make the change on the Radio buttons structure and you are limited. What confuses me though is do you want the info icon to provide help for the Label or the radio button options? or both? Your design (combo-box) provides help for the radio button options.
– Mo'ath
yesterday
add a comment |
Thanks for contributing an answer to User Experience Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fux.stackexchange.com%2fquestions%2f124819%2fplacement-of-more-information-help-icon-button-for-radio-buttons%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
How about below main label?
– Yong Quan
Apr 3 at 2:30
What we decided on was to just use a combo box if it is an enum. Since it is our practice to only use the more information when it is absolutely needed. Therefore it should be pretty rare for them to show up, but IF it is needed and it is an enum just use the combo box control to avoid all confusion.
– L. Lemmer
2 days ago