>If no fieldset is used for the individual questions, how does a
>screen reader associate the question with the radio group? The label
>will differentiate the options, but what about the questions?
Essentially it does not as their is no explicit structural association
between the radio buttons and the question. while there is an implicit
association [they are within the same container element/ they are
contiguous visually and or in the reading order]
for the most part the screen reader only knows what you tell it through the
code.
>If fieldsets are nested, how does a screen reader handle the
>legends? Are they concatenated for each form control or is only the
>legend from the parent fieldset used?
using JAWS 4.51 the legends are not concatenated.
>It sounds like a long legend is a bad idea - correct?
I'd agree with this.
>In a page where there is only one form and one semantically linked
>set of form controls is a fieldset necessary/desirable?
I think while desirable it is not necessary, unless you have a radio button
or checkbox group.
But why not use the fieldset element to structure the form instead of
putting in a div or some other container? remeber the legend is optional.
with regards
Steven Faulkner
Web Accessibility Consultant
National Information & Library Service (NILS)
454 Glenferrie Road
Kooyong Victoria 3144
Phone: (613) 9864 9281
Fax: (613) 9864 9210
Email: [EMAIL PROTECTED]
National Information Library Service
A subsidiary of RBS.RVIB.VAF Ltd.
Damian Sweeney
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
.edu.au> cc:
Sent by: Subject: RE: [WSG] Help with fieldset
in a li
[EMAIL PROTECTED]
group.org
29/10/2004 10:29
AM
Please respond to
wsg
Thanks to Susan, Steven and Roger for the replies so far.
A couple of questions for clarification:
* If no fieldset is used for the individual questions, how does a
screen reader associate the question with the radio group? The label
will differentiate the options, but what about the questions?
* It sounds like a long legend is a bad idea - correct?
* In a page where there is only one form and one semantically linked
set of form controls is a fieldset necessary/desirable?
* If fieldsets are nested, how does a screen reader handle the
legends? Are they concatenated for each form control or is only the
legend from the parent fieldset used?
Cheers,
Damian
>One benefit of using fieldset and legend for screen reader users is that
>nearly all readers will read the legend before every input label within a
>fieldset. This can be very helpful with forms that require the same
>information within different sections of the form. For example, if you
need
>put in name, phone number etc for a number of different people, the form
>input labels for each person will be the same - the layout of the form may
>make the different sections of the form obvious for visual users of the
>site, but the difference may not be obvious if you can't see. However,
when
>you use fieldset and legend (with say a legend of purchaser for one
person)
>then the reader will read the labels within this fieldset as purchaser
name,
>purchaser phone number etc.
>
>An article with some more information about form accessibility can be
found
>at http://www.usability.com.au/resources/forms.cfm
>
>Hope this is helpful
>Roger
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Behalf Of Susan R. Grossman
>Sent: Friday, 29 October 2004 1:28 AM
>To: [EMAIL PROTECTED]
>Subject: Re: [WSG] Help with fieldset in a li
>
>
>> > Firstly, am I using fieldset and legend in the correct semantic
manner?
>
>My understanding is that fieldset is meant to group all the similar
>form elements together, not to diferentiate each input. A group of
>numbered questions are all related to each other, and the entire
>thing should be in one fieldset with one legend. If you were to add
>a second group of numbered questions starting the numbers over again
>because they are related to each other, but not to the first group of
>numbered questions, then you would use a second fieldset and legend.
>(a new one, not nested)
>
>At least this is how I've interepreted and used the fieldset. An
>everyday example is a login form. The fieldset goes around the
>username and password text boxes as well as the radio button for
>remembering your password, with the legend on the login text. Any
>other fields like submitting for a lost password would be in a
>separate fieldset with new legend of forgotten password.
>
>--
>Susan R. Grossman
>[EMAIL PROTECTED]
--
Damian Sweeney
Instructional Designer, AIRport Project
Equity, Language and Learning Programs
University of Melbourne
723 Swanston St
Parkville 3010
www.services.unimelb.edu.au/ellp/
ph 03 8344 9370, fax 03 9349 1039
This email and any attachments may contain personal information or
information that is otherwise confidential or the subject of
copyright. Any unauthorised use, disclosure or copying of any part of
it is prohibited. The University does not warrant that this email or
any attachments are free from viruses or defects. Please check any
attachments for viruses and defects before opening them. If this
email is received in error please delete it and notify us by return
email or by phoning (03) 8344 9370.
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
