E-mail List Archives

Re: Accessible conditional form fields


From: Jim Allan
Date: Oct 27, 2010 8:42AM

H3 are only read when not in forms mode, i.e. when using the arrow key
to read through the document or using the say all command. when in
forms mode (Jaws 10 and before) everything other than form controls is
skip. Even in Jaws 11+ most users will navigate using the tab key to
navigate between form controls again skipping H3.
Fieldset/Legend will be read by Jaws if you move into a group of
controls that has them. The controls will be explicitly associated
with the fieldset/legend that contains them.


On Tue, Oct 26, 2010 at 11:10 PM, adam solomon
< <EMAIL REMOVED> > wrote:
> You have provided some sound reasoning, however wcag specs on the fieldset
> issue <http://www.w3.org/TR/2008/WD-WCAG20-TECHS-20080430/H82.html>;do
> specify that related or logically grouped form fields should have a fieldset
> around them (there are also the condtional fields) - how is your example
> different?
> On Tue, Oct 26, 2010 at 10:08 PM, D A < <EMAIL REMOVED> > wrote:
>> > In any event, as long as the conditional field comes after the
>> > associated radio button (in the html sequence) you shouldn't have a
>> problem,
>> > since the conditional content will appear after the user's selection and
>> > will not be missed.
>> Good to know. Thanks!
>> > Don't forget fieldset/legend.
>> oof. Well, now that you've opened that can of worms... ;o)
>> In my previous research, the opinion of the fieldset/legend for
>> radiobutton lists seems to end up with hung juries.
>> I've opted to go for h3 instead of a legend for a few reasons:
>> 1. Legends are really hard to deal with via CSS
>> 2. My understanding is that fieldsets are read prior to each
>> radiobutton option and that for many folks, that, itself, can be
>> annoying and lead to accessibility issues--especially when the the
>> fieldset would be a complete sentence (or group of sentences).
>> I'm still open to being convinced one way or the other, of course.
>> -DA