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 dangerous is XSS
How does a dynamic QR code work?
What's the meaning of "Sollensaussagen"?
Can compressed videos be decoded back to their uncompresed original format?
What is this scratchy sound on the acoustic guitar called?
How can I prove that a state of equilibrium is unstable?
GFCI outlets - can they be repaired? Are they really needed at the end of a circuit?
How to install cross-compiler on Ubuntu 18.04?
Is it "common practice in Fourier transform spectroscopy to multiply the measured interferogram by an apodizing function"? If so, why?
Placement of More Information/Help Icon button for Radio Buttons
When handwriting 黄 (huáng; yellow) is it incorrect to have a disconnected 草 (cǎo; grass) radical on top?
What is the fastest integer factorization to break RSA?
Why was the shrink from 8″ made only to 5.25″ and not smaller (4″ or less)
What are the G forces leaving Earth orbit?
Why didn't Boeing produce its own regional jet?
Could the museum Saturn V's be refitted for one more flight?
How to coordinate airplane tickets?
Why can't we say "I have been having a dog"?
How do conventional missiles fly?
Why is it a bad idea to hire a hitman to eliminate most corrupt politicians?
Avoiding the "not like other girls" trope?
Am I breaking OOP practice with this architecture?
Is it a bad idea to plug the other end of ESD strap to wall ground?
Forgetting the musical notes while performing in concert
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
asked 6 hours ago
L. LemmerL. Lemmer
1067
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
asked 6 hours ago
L. LemmerL. Lemmer
1067
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
asked 6 hours ago
L. LemmerL. Lemmer
1067
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 6 hours ago
L. LemmerL. Lemmer
1067
asked 6 hours ago
L. LemmerL. Lemmer
1067
asked 6 hours ago
L. LemmerL. Lemmer
1067
asked 6 hours ago
L. LemmerL. Lemmer
1067
asked 6 hours ago
L. LemmerL. Lemmer
1067
1067
add a comment |
add a comment |
3 Answers
3
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:
answered 5 hours ago
Mike MMike M
11.1k12331
add a comment |
Think of a logical order and good placement
Instead you may use this:
answered 2 hours ago
Mo'athMo'ath
486211
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
1 hour ago
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.
answered 5 hours ago
Juan Jesús MilloJuan Jesús Millo
1516
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 |
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
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:
answered 5 hours ago
Mike MMike M
11.1k12331
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:
answered 5 hours ago
Mike MMike M
11.1k12331
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:
answered 5 hours ago
Mike MMike M
11.1k12331
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:
answered 5 hours ago
Mike MMike M
11.1k12331
edited 2 hours ago
answered 5 hours ago
Mike MMike M
11.1k12331
answered 5 hours ago
Mike MMike M
11.1k12331
answered 5 hours ago
Mike MMike M
11.1k12331
11.1k12331
add a comment |
add a comment |
Think of a logical order and good placement
Instead you may use this:
answered 2 hours ago
Mo'athMo'ath
486211
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
1 hour ago
add a comment |
Think of a logical order and good placement
Instead you may use this:
answered 2 hours ago
Mo'athMo'ath
486211
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
1 hour ago
add a comment |
Think of a logical order and good placement
Instead you may use this:
answered 2 hours ago
Mo'athMo'ath
486211
Think of a logical order and good placement
Instead you may use this:
answered 2 hours ago
Mo'athMo'ath
486211
edited 2 hours ago
answered 2 hours ago
Mo'athMo'ath
486211
answered 2 hours ago
Mo'athMo'ath
486211
answered 2 hours ago
Mo'athMo'ath
486211
486211
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
1 hour 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
1 hour 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
1 hour 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
1 hour ago
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.
answered 5 hours ago
Juan Jesús MilloJuan Jesús Millo
1516
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.
answered 5 hours ago
Juan Jesús MilloJuan Jesús Millo
1516
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.
answered 5 hours ago
Juan Jesús MilloJuan Jesús Millo
1516
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.
answered 5 hours ago
Juan Jesús MilloJuan Jesús Millo
1516
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 5 hours ago
answered 5 hours ago
Juan Jesús MilloJuan Jesús Millo
1516
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 5 hours ago
Juan Jesús MilloJuan Jesús Millo
1516
answered 5 hours ago
Juan Jesús MilloJuan Jesús Millo
1516
1516
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 |
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
