There is certainly a semantic difference between switches and checkboxes. As much of a difference as between buttons and links.
A checkbox is part of a checklist, something you use to indicate or track the states of things. You put a series of checkmarks on a form, then bring it to the reception desk. A switch, like a button, is a mechanical control that actuates something. You flick a switch to turn the light on. Technically, a switch could be implemented as a styled checkbox with JavaScript attached. But as a website visitor, I would rather not deal with a dozen websites offering a dozen different switch appearances and behaviours attached to mousedown, mouseup, click, tap, drag, and swipe. MZ. -- Michael Zajac http://zajac.ca/ +1-204-943-6596 On 2013-11-19, at 8:39, Anne van Kesteren <ann...@annevk.nl> wrote: > On Tue, Nov 19, 2013 at 2:25 PM, Domenic Denicola > <dome...@domenicdenicola.com> wrote: >> "Use a toggle switch for binary settings when changes become effective >> immediately after the user changes them." >> >> "Use a checkbox when the user has to perform extra steps for changes to be >> effective." > > On the other hand, we have these two type of experiences on the web > already and they are not limited to checkboxes. Introducing different > controls for effectively the same action with the only difference > being whether you need to hit submit seems somewhat contrived. > > > -- > http://annevankesteren.nl/
