[WSG] accessibilty: avoid radio buttons?

2011-07-16 Thread tee
I am building a site that must meet wcag 2.0 compliant. A web form has radio 
buttons option, and according to afb.org:

Radio buttons are not supported consistently by all versions of browsers, 
screen readers, and combinations. A correctly labeled and tagged set of radio 
buttons is a very difficult control for users of screen-reading technology. If 
a choose only one situation is called for, a select menu is preferable.

Is this a sound advice?

Thanks!

tee

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] accessibilty: avoid radio buttons?

2011-07-16 Thread Andrew Boyd
On Sun, Jul 17, 2011 at 9:14 AM, tee weblis...@gmail.com wrote:
 I am building a site that must meet wcag 2.0 compliant. A web form has radio 
 buttons option, and according to afb.org:

 Radio buttons are not supported consistently by all versions of browsers, 
 screen readers, and combinations. A correctly labeled and tagged set of radio 
 buttons is a very difficult control for users of screen-reading technology. 
 If a choose only one situation is called for, a select menu is preferable.

 Is this a sound advice?

 Thanks!

 tee

Tee,

does it work with a keyboard only? Can you operate it with a screen
reader like NVDA with your eyes closed? There's a whole lot more to
code-level conformance than those two things, and a whole lot more to
WCAG 2.0 conformance than code-level conformance, but if you get those
two things right then you've made a brilliant start.

Best regards, Andrew

-- 
---
Andrew Boyd
http://uxbookclub.org -- connect, read, discuss


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] accessibilty: avoid radio buttons?

2011-07-16 Thread tee
Andrew,

Keyboard yes, not sure about NVDA as I don't have this software, but accessible 
for VoiceOver. 

Thanks!

tee

On Jul 16, 2011, at 4:34 PM, Andrew Boyd wrote:

 On Sun, Jul 17, 2011 at 9:14 AM, tee weblis...@gmail.com wrote:
 I am building a site that must meet wcag 2.0 compliant. A web form has radio 
 buttons option, and according to afb.org:
 
 Radio buttons are not supported consistently by all versions of browsers, 
 screen readers, and combinations. A correctly labeled and tagged set of 
 radio buttons is a very difficult control for users of screen-reading 
 technology. If a choose only one situation is called for, a select menu is 
 preferable.
 
 Is this a sound advice?
 
 Thanks!
 
 tee
 
 Tee,
 
 does it work with a keyboard only? Can you operate it with a screen
 reader like NVDA with your eyes closed? There's a whole lot more to
 code-level conformance than those two things, and a whole lot more to
 WCAG 2.0 conformance than code-level conformance, but if you get those
 two things right then you've made a brilliant start.
 
 Best regards, Andrew
 
 -- 
 ---
 Andrew Boyd
 http://uxbookclub.org -- connect, read, discuss
 
 
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: memberh...@webstandardsgroup.org
 ***
 



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] accessibilty: avoid radio buttons?

2011-07-16 Thread Steve Green
You are mixing up two unrelated issues. As long as the radio buttons are marked 
up correctly, they will be WCAG 2.0 compliant. The AFB's opinion is irrelevant 
in this respect.
 
The AFB's comments are of interest with regard to the user experience, and it 
would be helpful if they justified their statement. In my opinion, based on 
years of user testing with screen reader users, radio buttons need not be 
difficult to use and are almost never very difficult to use. I would agree 
that they are slightly more difficult to use than a select element, and they 
are definitely more difficult to use if they are contained in a fieldset and 
the legend contains a lot of text (the legend is read out before the label for 
each radio button).
 
You have to balance this against the fact that radio buttons are generally 
preferred by most users because they can see all the options at a glance and 
only one click is necessary instead of two.
 
Steve Green
Director
Test Partners Ltd




From: li...@webstandardsgroup.org on behalf of tee
Sent: Sun 17/07/2011 00:14
To: wsg@webstandardsgroup.org
Subject: [WSG] accessibilty: avoid radio buttons?



I am building a site that must meet wcag 2.0 compliant. A web form has radio 
buttons option, and according to afb.org:

Radio buttons are not supported consistently by all versions of browsers, 
screen readers, and combinations. A correctly labeled and tagged set of radio 
buttons is a very difficult control for users of screen-reading technology. If 
a choose only one situation is called for, a select menu is preferable.

Is this a sound advice?

Thanks!

tee

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***





***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***
winmail.dat