WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: A List of Form Elements?

for

From: Lewis, Sunshine T.
Date: Mar 14, 2012 11:36AM


Does the dislike of lists for forms also apply to lists for checkboxes
and radio buttons?
<fieldset><legend>
<ul>
<li><input ></li>
<li><input ></li>
</ul>
</fieldset>

Markup seems semantically appropriate to me but I'm curious if that
would introduce the same issues?




Florida is headed in the right direction! View Florida's Jobs Growth Chart: http://www.flgov.com/photoview/jobcreationchart.jpg
The Department of State is leading the commemoration of Florida's 500th anniversary in 2013. For more information, please go to www.fla500.com.
The Department of State is committed to excellence. Please take our Customer Satisfaction Survey: http://survey.dos.state.fl.us/index.aspx?email= <EMAIL REMOVED>
-----Original Message-----
From: Steve Green [mailto: <EMAIL REMOVED> ]
Sent: Tuesday, March 13, 2012 1:33 PM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] A List of Form Elements?

I am also totally opposed to the use of lists for forms. It's
semantically incorrect and it's an appalling user experience for screen
reader users - the additional verbiage decreases comprehensibility
rather than increasing it.

Steve Green
Managing Director
Test Partners Ltd

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Jennifer
Sutton
Sent: 13 March 2012 00:43
To: WebAIM Discussion List
Subject: Re: [WebAIM] A List of Form Elements?

I'm not a fan of list-items in forms, either. I've rarely seen it done
and have often argued against it. When I'm in a form, I find the
indication of list-items distracting and disorienting from the task at
hand. Honestly, it just feels semantically wrong to me.

Jennifer

At 04:18 PM 3/12/2012, you wrote:
>I'm not a fan of lists to differentiate form items. You adequately note

>the disadvantages, which I think outweigh any perceived benefits.
>In most cases, the form is navigated from form control to form control
>anyway (i.e., hitting the Tab key), so the only real advantage (that
>the number of items is identified) often doesn't occur anyway.
>
>The <div> markup could probably be simplified even more with <form
>class="aform"> <div>...<label>...<input>...</div>
></form>
>and
>.aform div { }
>to define the necessary styling.
>
>Jared Smith
>WebAIM.org
>