- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Mon, 10 Apr 2006 08:30:31 -0500
- To: "Loretta Guarino Reid" <lguarino@adobe.com>, "Cynthia Shelly" <cyns@exchange.microsoft.com>, "Gez Lemon" <gez.lemon@gmail.com>
- Cc: "Becky Gibson" <Becky_Gibson@notesdev.ibm.com>, "Ben Caldwell" <caldwell@trace.wisc.edu>, "Christophe Strobbe" <christophe.strobbe@esat.kuleuven.be>, "Michael Cooper" <michaelc@watchfire.com>, <public-wcag-teamb@w3.org>, "Katie Haritos-Shea" <ryladog@earthlink.net>
Loretta's proposal makes sense to me. John "Good design is accessible design." Dr. John M. Slatin, Director Accessibility Institute University of Texas at Austin FAC 248C 1 University Station G9600 Austin, TX 78712 ph 512-495-4288, fax 512-495-4524 email jslatin@mail.utexas.edu Web http://www.utexas.edu/research/accessibility -----Original Message----- From: public-wcag-teamb-request@w3.org [mailto:public-wcag-teamb-request@w3.org] On Behalf Of Loretta Guarino Reid Sent: Friday, April 07, 2006 3:10 PM To: Cynthia Shelly; Gez Lemon Cc: Becky Gibson; Ben Caldwell; Christophe Strobbe; Michael Cooper; public-wcag-teamb@w3.org; Katie Haritos-Shea Subject: RE: SC 1.3.1 Failure: Using Scripting Events instead of anchors to create links Can we define "emulating a link" as *only* loading a new web unit or repositioning the current web unit? If the control has other actions, like saving the current state or changing the current contents, then it is not emulating a link and this failure does not apply. Loretta Guarino Reid lguarino@adobe.com Adobe Systems, Acrobat Engineering > -----Original Message----- > From: Cynthia Shelly [mailto:cyns@exchange.microsoft.com] > Sent: Friday, April 07, 2006 9:46 AM > To: Gez Lemon; Loretta Guarino Reid > Cc: Becky Gibson; Ben Caldwell; Christophe Strobbe; Michael > Cooper; public-wcag-teamb@w3.org; Katie Haritos-Shea > Subject: RE: SC 1.3.1 Failure: Using Scripting Events instead > of anchors to create links > > These are issues of UI design, on which reasonable people can > disagree. They are not issues of accessibility. > > Buttons and links throw events when clicked that allow them > to interoperate with AT. Other elements don't. That is an > accessibility issue. In many respects, that is THE > accessibility issue with Web applications. > > -----Original Message----- > From: Gez Lemon [mailto:gez.lemon@gmail.com] > Sent: Friday, April 07, 2006 9:11 AM > To: Loretta Guarino Reid > Cc: Cynthia Shelly; Becky Gibson; Ben Caldwell; Christophe > Strobbe; Michael Cooper; public-wcag-teamb@w3.org; Katie Haritos-Shea > Subject: Re: SC 1.3.1 Failure: Using Scripting Events instead > of anchors to create links > > On 07/04/06, Loretta Guarino Reid <lguarino@adobe.com> wrote: <quote> > So, how can we characterize the difference between processing > information and pure navigation in our test procedure, so > that it is clear that this failure doesn't prohibit Next and > Prev buttons in wizards? > </quote> > > Does it need characterising? If the next and previous buttons > are purely navigational, they should be a failure. If they're > part of the wizard (the user is performing an action), > they're not emulating links and wouldn't fail. > > Best regards, > > Gez > > -- > _____________________________ > Supplement your vitamins > http://juicystudio.com >
Received on Monday, 10 April 2006 13:30:55 UTC