W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2005

Re: best practise radio buttons

From: David Woolley <david@djwhome.demon.co.uk>
Date: Mon, 13 Jun 2005 21:34:20 +0100 (BST)
Message-Id: <200506132034.j5DKYK006882@djwhome.demon.co.uk>
To: w3c-wai-ig@w3.org

> Although the page could be redesigned to avoid the layout of radio
** buttons this is the requested design and I want to try and accommodate it.

That's usually a very bad starting point!  However in this case, assuming
that you can get rid of the bogus HTML from the hosting site and the
stray </tr> in your code, I think it may be OK as it is, because
the TH elements identify the options.  You should probably make the
association between cells and headings more explicit.

> One technique I was considering is having text after each radio button
** marking it up with <labels> and using css to hide the text. Another

If labels are needed, they need to be visible.  In any case, this
is often discussed and basically there is no clean way of hiding 
with CSS.  display:none completely suppresses rendering in all media
(AT generally believes it uses visual media, anyway).  visibility: hide
still takes up space.  All such tactics are likely to be perceived as
attempts a keyword stuffing.

** technique I have read is to add title tags to each radio button.

You meant title attributes.  This has also been suggested, but it is
a misuse.  More importantly, title isn't rendered by IE when you 
use keyboard navigation (this ties in with the rule that if a label
is needed it is needed in all media).
Received on Monday, 13 June 2005 20:34:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:25 UTC