Menu
  • UX Trending
  • UX PODCASTS
    • DESIGN UNTANGLED
    • UX CAKE
  • UX Reading Room
  • UX Portfolio Building
  • UX JOBS
    • Atlanta
    • Dallas
    • Los Angeles
UXShareLab… everything you need to know about UX and more…
for the user experience design community

Search

Browse: Home   /   Choice components Hierarchy (Toggles, radio, checkboxes)

Choice components Hierarchy (Toggles, radio, checkboxes)

by UXStackExchange on July 27, 2017 in uxstackexchange

I'm here to ask about a issue about the hierarchy of the choice components. Let's say we have complicated settings with nested elements. What's the right Hierachy?

I mean.. could we have a radio with nested options as toggle or it should be bettere to avoid these cases using toggles, radio buttons and eventually nested checkboxes or, maybe, other radio buttons?

Thank you!

Tags: UX Stack Exchange

Sign Up for the latest in UX News...

Enter your email address to subscribe to UXShareLab and receive notifications of new posts by email.

Join 834 other subscribers

Related Posts

Is there any reason the discussion is inverted in e-mail threads?
Is there any reason the discussion is inverted in e-mail threads?
How to handle Han Unification with user input?
How to handle Han Unification with user input?
Open source projects UX designers can join? [closed]
Open source projects UX designers can join? [closed]
Should we remove an email from Sent Mail after it is moved to Inbox? [on hold]
Should we remove an email from Sent Mail after it is moved to Inbox? [on hold]

Choice components Hierarchy (Toggles, radio, checkboxes)

by UXStackExchange on July 27, 2017 in uxstackexchange

I'm here to ask about a issue about the hierarchy of the choice components. Let's say we have complicated settings with nested elements. What's the right Hierachy?

I mean.. could we have a radio with nested options as toggle or it should be bettere to avoid these cases using toggles, radio buttons and eventually nested checkboxes or, maybe, other radio buttons?

Thank you!

Tags: UX Stack Exchange

Related Posts

[Don’t] listen to your customers
[Don’t] listen to your customers
Prioritising UX Design Considerations
Prioritising UX Design Considerations
Is Swipe OK for accessibility in Native Apps? WCAG says no
Is Swipe OK for accessibility in Native Apps? WCAG says no
Huge data in table in responsive email
Huge data in table in responsive email
← What is better way of arranging filters?
Placing logout button in menu-less application →

Topics

Web Design User Experience User Interaction Usability UX wordpress User testing UX Jobs Atlanta Universal Design & Accessibility WordPress Plugins UX Design UI uxbooth UX Rockstars web-app UX Jobs in Atlanta WordPress Gutenberg UI design UX Jobs Dallas uxstackexchange UX Toolbox User Research user-behavior Visual Design UX Jobs Los Angeles

Feeds

UI UI design Universal Design & Accessibility Usability user-behavior User Experience User Interaction User Research User testing UX uxbooth UX Design UX Jobs Atlanta UX Jobs Dallas UX Jobs in Atlanta UX Jobs Los Angeles UX Rockstars uxstackexchange UX Toolbox Visual Design web-app Web Design wordpress WordPress Gutenberg WordPress Plugins

<span>recent posts</span>

  • UX in 2018: The human element

    • Anywhere
  • Three Takeaways from the Hawai’i Missile False Alarm

    • Anywhere
  • UX in 2018: Content

    • Anywhere
  • UX in 2018: Design, Development, and Accessibility

    • Anywhere
  • The Power and Danger of Persuasive Design

    • Anywhere

connect to uxsharelab

Enter your email address to subscribe to receive notifications of new posts by email.

UXShareLab. Copyright © 2018. All rights reserved.

  • Contact UXShareLab
  • UXShareLab Community
  • UX PROCESS
  • Recommended Reading
  • UX StackExchange