Re: Techniques for WCAG 2: F42

Thank you. We have modified the description of F42 to read:

This failure occurs when JavaScript event handlers are attached to
elements to "emulate links." A control or link created in this  manner
cannot be tabbed to from the keyboard and does not gain keyboard focus
like other controls and/or links.

We have also added F42 to the list of common failures in 2.1.1 and have
updated the title to "Failure of SC 1.3.1 and 2.1.1 due to using
scripting events to emulate links."

Regards,

Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact

On behalf of the WCAG Working Group

> 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

Received on Tuesday, 11 December 2007 23:29:01 UTC