WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Expected behavior for description text of a toggle button

for

From: Cliff Tyllick
Date: May 20, 2015 1:11PM

Alexander, if I understand your question correctly, the answer is "Neither."

When I touch the text, I probably want to swipe up or down, or perhaps zoom in with a two-finger motion. I don't expect a form control to toggle, because that isn't what text—even when it's a form label—does.

I don't expect a checkbox to get checked or a radio button to get selected unless I actually touch or click inside the control itself—because that's how they work.

I'm curious: Why isn't the default behavior of the native control adequate? For usability as well as accessibility, it's best to use native controls whenever possible.

Cliff Tyllick
Texas Department of Assistive and Rehabilitative Services

Sent from my iPhone
Although its spellcheck often saves me, all goofs in sent messages are its fault.

> On May 20, 2015, at 12:42 PM, Alexander Schmitz < <EMAIL REMOVED> > wrote:
>
> Hi
> We ( jQuery UI and Mobile ) are working on a new checkboxradio widget. This
> takes a checkbox or radio input and styles the label to create a toggle
> button, this way all the proper associations are handled by the browser.
>
> One issue we have run into, is what the expected behavior is when you have
> a form with a layout similar to http://jsbin.com/muceye/1/edit?html,output
> . Should the descriptive text on the left activate the button on the right
> ( be an actual label like the top example, and other inputs in the form )
> or just be associated maybe with a fieldset and legend like the second
> example.
>
> Any advice would be appreciated!
>
> Alexander Schmitz
> jQuery Foundation
> > > >