E-mail List Archives
Re: Forms as lists
From: Jared Smith
Date: Sep 2, 2010 3:27PM
- Next message: Donald Evans: "Re: Forms as lists"
- Previous message: Donald Evans: "Markup language for Music?"
- Next message in Thread: Donald Evans: "Re: Forms as lists"
- Previous message in Thread: Simius Puer: "Re: Forms as lists"
- View all messages in this Thread
On Thu, Sep 2, 2010 at 2:29 PM, adam solomon wrote:
> I propose
> that the first section, which contains all the filter controls, even though
> they are not radio or checkboxes, should be inside a fieldset, since they
> are related in their common purpose, namely to filter a particular search.
These controls *may* be placed in a fieldset - there's nothing that
precludes this, but I don't believe they "should" be inside a
fieldset. WCAG certainly does not recommend doing so.
Again, using this same logic, you are suggesting that all forms
"should" be in a fieldset because they all are "related in their
common purpose". This would mean that even a simple search form with a
text box and a button would need a fieldset - something that would
provide no benefit to that form.
> The legend might read simply, "search filter", or something of that nature.
> Would you agree?
Sure, but I don't believe that it would be any more accessible than
without the fieldset. In this case, making it a heading would probably
be more appropriate.
Because the screen reader will repeat the legend for all of the form
controls within that fieldset, this would quickly become very
repetitive and potentially confusing. In your example, the user would
hear "Search filter" for every control within that form even though it
would already be very apparent what the form controls are for.
> Another point is hidden legends. In these cases the analyst
> will often refuse to allow a visual legend. Should a hidden legend
> (accessible to the screen reader) then be implemented?
If the form makes perfect sense without the fieldset, why would force
one upon only screen reader users? This very well makes my point - you
should only use a fieldset when a legend is necessary for the user to
determine the function of a group of controls within a form. If it's
accessible without the fieldset and legend, adding the fieldset and
legend will only make the form more time consuming and repetitive.
Jared
- Next message: Donald Evans: "Re: Forms as lists"
- Previous message: Donald Evans: "Markup language for Music?"
- Next message in Thread: Donald Evans: "Re: Forms as lists"
- Previous message in Thread: Simius Puer: "Re: Forms as lists"
- View all messages in this Thread