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?
Do creatures with a speed 0ft., fly 30ft. (hover) ever touch the ground?
Why didn't Boeing produce its own regional jet?
Where would I need my direct neural interface to be implanted?
How to prevent "they're falling in love" trope
Convert seconds to minutes
files created then deleted at every second in tmp directory
How can a day be of 24 hours?
How do conventional missiles fly?
Send out email when Apex Queueable fails and test it
Bullying boss launched a smear campaign and made me unemployable
Is there a hemisphere-neutral way of specifying a season?
What's the meaning of "Sollensaussagen"?
Notepad++ delete until colon for every line with replace all
Obtaining database information and values in extended properties
How seriously should I take size and weight limits of hand luggage?
What is the most common color to indicate the input-field is disabled?
Pact of Blade Warlock with Dancing Blade
Is it possible to create a QR code using text?
What are the G forces leaving Earth orbit?
How obscure is the use of 令 in 令和?
Mathematica command that allows it to read my intentions
Why were 5.25" floppy drives cheaper than 8"?
Standard deduction V. mortgage interest deduction - is it basically only for the rich?
How can I deal with my CEO asking me to hire someone with a higher salary than me, a co-founder?
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?
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
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 7 hours ago
L. LemmerL. Lemmer
1117
1117
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Think of a logical order and good placement
Instead you may use this:
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
3 hours ago
If it is mandatory to keep the label and the options next to each other, then maybe you could have a tooltip displays when the Label itself is hovered (the label could also be underlined). Once the user hovers the Label, it displays the info/help. I can update the answer above to include an example if needed.
– Mo'ath
1 hour ago
How about if you raise the label a little bit? So the label and options are not exactly at the same horizontal level, that way placing the info icon to the right of the label won't be confused as an info icon for the option.
– Mo'ath
11 mins ago
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 |
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
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
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Think of a logical order and good placement
Instead you may use this:
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
3 hours ago
If it is mandatory to keep the label and the options next to each other, then maybe you could have a tooltip displays when the Label itself is hovered (the label could also be underlined). Once the user hovers the Label, it displays the info/help. I can update the answer above to include an example if needed.
– Mo'ath
1 hour ago
How about if you raise the label a little bit? So the label and options are not exactly at the same horizontal level, that way placing the info icon to the right of the label won't be confused as an info icon for the option.
– Mo'ath
11 mins ago
add a comment |
Think of a logical order and good placement
Instead you may use this:
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
3 hours ago
If it is mandatory to keep the label and the options next to each other, then maybe you could have a tooltip displays when the Label itself is hovered (the label could also be underlined). Once the user hovers the Label, it displays the info/help. I can update the answer above to include an example if needed.
– Mo'ath
1 hour ago
How about if you raise the label a little bit? So the label and options are not exactly at the same horizontal level, that way placing the info icon to the right of the label won't be confused as an info icon for the option.
– Mo'ath
11 mins ago
add a comment |
Think of a logical order and good placement
Instead you may use this:
Think of a logical order and good placement
Instead you may use this:
edited 4 hours ago
answered 4 hours ago
Mo'athMo'ath
506211
506211
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
3 hours ago
If it is mandatory to keep the label and the options next to each other, then maybe you could have a tooltip displays when the Label itself is hovered (the label could also be underlined). Once the user hovers the Label, it displays the info/help. I can update the answer above to include an example if needed.
– Mo'ath
1 hour ago
How about if you raise the label a little bit? So the label and options are not exactly at the same horizontal level, that way placing the info icon to the right of the label won't be confused as an info icon for the option.
– Mo'ath
11 mins ago
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
3 hours ago
If it is mandatory to keep the label and the options next to each other, then maybe you could have a tooltip displays when the Label itself is hovered (the label could also be underlined). Once the user hovers the Label, it displays the info/help. I can update the answer above to include an example if needed.
– Mo'ath
1 hour ago
How about if you raise the label a little bit? So the label and options are not exactly at the same horizontal level, that way placing the info icon to the right of the label won't be confused as an info icon for the option.
– Mo'ath
11 mins ago
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
3 hours ago
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
3 hours ago
If it is mandatory to keep the label and the options next to each other, then maybe you could have a tooltip displays when the Label itself is hovered (the label could also be underlined). Once the user hovers the Label, it displays the info/help. I can update the answer above to include an example if needed.
– Mo'ath
1 hour ago
If it is mandatory to keep the label and the options next to each other, then maybe you could have a tooltip displays when the Label itself is hovered (the label could also be underlined). Once the user hovers the Label, it displays the info/help. I can update the answer above to include an example if needed.
– Mo'ath
1 hour ago
How about if you raise the label a little bit? So the label and options are not exactly at the same horizontal level, that way placing the info icon to the right of the label won't be confused as an info icon for the option.
– Mo'ath
11 mins ago
How about if you raise the label a little bit? So the label and options are not exactly at the same horizontal level, that way placing the info icon to the right of the label won't be confused as an info icon for the option.
– Mo'ath
11 mins ago
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:
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 4 hours ago
answered 7 hours ago
Mike MMike M
11.1k12331
11.1k12331
add a comment |
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
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
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
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
edited 7 hours ago
New contributor
answered 7 hours ago
Juan Jesús MilloJuan Jesús Millo
1716
1716
New contributor
New contributor
add a comment |
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