RE: SC 1.3.1 Failure: Using Scripting Events instead of anchors to create links

<loretta>Should we discuss the distinctions between
links and buttons, to help people understand how to apply the test
procedure? Should we keep Example 4 or not? 
</loretta>

Thanks for all of the work on this, Loretta!  I don't think we need to 
make the distinction between links and buttons.  The test case covers 
someone using a button to act as a link even though we don't have an 
explicit example for it.   I would propose a modification to the first 
check to specify that scripting is used to navigate to a new location. 
This would still allow scripting on a button that did pre-processing 
before submitting a form.  A submit button might have an event handler and 
the ultimate result of submitting is to navigate to a new page. That is 
fine as long as scripting isn't used to do the navigation (via the 
location.href object). 

<proposed>
 1. Check whether there are JavaScript event handlers on any element other 
than an a or area element that use scripting to navigate to a new 
location. 
</proposed>

I don't think we need to include example 4 but can live with it as it is a 
legitimate failure.    I have to write the failure for 4.1.1, Failure due 
to using script to make div or span a user interface control in HTML and 
could use a modified version of this example (it would need to be modified 
because I don't think that technically a link is a user interface control 
but I'm sure some might disagree). 

-becky

Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com

Received on Thursday, 6 April 2006 18:59:23 UTC