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

Re: radio button & drop-down

From: <Kieran_M_O'Brien@national.com.au>
Date: Tue, 28 Oct 2003 10:46:47 +1100
To: w3c-wai-ig@w3.org
Message-ID: <OFF085CA3D.7EFDF24D-ONCA256DCC.00824A00-CA256DCC.008335E4@au.thenational.com>


Matthew,

Thanks for your response. But unfortunately tabindex has no impact on radio
buttons. I tested this myself just to make sure I wasn't reading
incorrectly. It is a bit of a pain the way radio buttons work. Part of the
problem is that when my test user was using it, he didn't realise there
were more than one radio button because jaws doesn't announce radio button
1 of 10 or something like that, so he instincitvely hit tab, which then
took him to the drop-down associated with another radio button. I will have
to rethink this screen I think.

Thanks anyway.

Regards,
Kieran.




                                                                                                                                       
                      w3c-wai-ig@w3.org                                                                                                
                      Sent by:                 To:       WAI Interest Group <w3c-wai-ig@w3.org>                                        
                      w3c-wai-ig-reques        cc:                                                                                     
                      t@w3.org                 Subject:  Re: radio button & drop-down                                                  
                                                                                                                                       
                                                                                                                                       
                      27/10/2003 06:10                                                                                                 
                      PM                                                                                                               
                                                                                                                                       





Kieran_M_O'Brien@national.com.au wrote:
> I ask this question because in testing this app with a visually impaired
> person, he tabbed from the first radio button into the second drop-down
and
> selected an option thinking that he was selecting an interest rate for
that
> loan where in fact he was choosing it for a different one.

My question is: are you using a logical tab order?  That is, should the
fields be read in the order in which they appear in the HTML code?   If
not, maybe you should consider using tabindex.

Cheers

M

--
Matthew Smith
Kadina Business Consultancy
South Australia
http://www.kbc.net.au
Received on Monday, 27 October 2003 18:53:17 GMT

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