W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2003

RE: radio button & drop-down

From: Derek Featherstone <feather@wats.ca>
Date: Tue, 28 Oct 2003 18:44:08 -0500
To: <gdeering@acslink.net.au>, <w3c-wai-ig@w3.org>
Message-ID: <004201c39dad$6182c910$fe01a8c0@faottcan001>

Geoff wrote:
> But if you are mixing table cells across controls, as your example shows,
> when using fieldset you won't get a valid document (from memory).  Also
> fieldset can cause problems when using EMCA/Javascript on form controls in
> certain user agents (well, I shouldn't say fieldset is causing the
problems,
> it's the user agent's buggy implementation of those specifications).

Hmmm... Of course, forgot about those tables for form layout in the example
code...

You might try to:

1. Use CSS with careful use of floats and widths for formatting the form
controls contained within the fieldsets, with appropriate amount of testing,

-or-

2. Use a table inside each fieldset with CSS to format the table cell widths
accordingly, so that you'd achieve the appearance of having all the same
table, with labels lined up and form controls lined up as in your example.

Now -- I'm not a big fan of using tables for layout, however, there are some
times when it is just easier to do so -- provided the rest of your markup is
solid and carries the logical structure, and the tables linearlize
correctly, I can't think of many accessibility problems this will cause...
JAWS will likely announce that there is a table there with 2 columns and 1
row, but I believe that should be relatively harmless.

Cheers,
Derek.
--
Derek Featherstone  feather@wats.ca
Web Accessibility Specialist / Co-founder of WATS.ca
Web Accessibility Testing and Services
http://www.wats.ca   1.866.932.4878 (North America)
Received on Tuesday, 28 October 2003 18:48:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:12 GMT