Techniques for WCAG 2: F42

Refer to Common Failure F42 on
http://www.w3.org/TR/2007/WD-WCAG20-TECHS-20070517/Overview.html#F42
At present the description states:
"... or they may be recognized as interactive controls
but still not recognized as links. Such elements do
not appear in the links list generated
by user agents or assistive technology."

Comment: A control or link created in this  manner
cannot be tabbed to from the keyboard and does not
gain keyboard focus. Stating these are not
tab-navigable is a more direct way of conveying the
issue  than stating "does not appear inn a link list".
 I think this is important and missing from the
description. Yes one cannot perceive this to be a
control or a link but it is also an 'operability'
failure under 2.4.1.
Suggestion:
1. State these are not tab-navigable  and cannot be
accessed from the keyboard like other controls / links

2. Consider this to be a failure under 2.4.1 as well.
Thanks,
Sailesh Panchang 
spanchang02@yahoo.com
or sailesh.panchang@deque.com


       
____________________________________________________________________________________
Got a little couch potato? 
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz

Received on Sunday, 10 June 2007 03:22:03 UTC