W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2003

Re: onKeyPress activates link in Opera

From: Alan Chuter <achuter@teleservicios.com>
Date: Fri, 4 Jul 2003 14:13:04 +0200
Message-ID: <005f01c34225$a4faaa20$0bb8c90a@NTWKS72>
To: "Jon Hanna" <jon@spin.ie>, <w3c-wai-ig@w3.org>

Thanks, that (UAAG) is what I had in mind. I've tried checking the keycode
and mouse button in the event to filter out the A key in Opera and it works,
although it seems a bit complicated.

Alan



----- Original Message -----
From: "Jon Hanna" <jon@spin.ie>
To: <w3c-wai-ig@w3.org>
Sent: Friday, July 04, 2003 1:40 PM
Subject: RE: onKeyPress activates link in Opera


>
> > I asumed that the implementation of onclick is interpreted to
> > mean activated
> > in any way, but is it specified anywhere?
>
> The User-Agent accesibility guideline 1.2
>
<http://www.w3.org/TR/UAAG10/guidelines.html#tech-device-independent-handler
> s> states:
>
> "Allow the user to activate, through keyboard input alone, all input
device
> event handlers that are explicitly associated with the element designated
by
> the content focus."
>
> So this behaviour could be seen as an implementation of that point. Of
> course you as an author are meant to take some measure to deal with
failures
> of user agents, but I think that pretty much all browsers with onclick
> handlers react to direct (not via a menu) keyboard access of a link in
this
> manner.
>
> I'm sure someone on this list would know of exceptions.
>
>  If it is then I understand that
> > there's no need for redundant event handlers. WCAG techniques say
> > (http://www.w3.org/TR/WCAG10-HTML-TECHS/#directly-accessible-scripts)
> >     Use "onclick" with "onkeypress"
> > But this suggests that the technique is no longer necessary, because the
> > browsers have overcome the probleam.
>
> It is still necessary where onclick isn't over-riding a default behaviour.
> For instance if you provide an onclick handler to a div you should make it
> selectable and provide an onkeypress as such onclicks are literally "on
> click".
>
> > Opera doesn't use the tab key for link navigation. It uses A and
> > Q instead.
>
> Which would make it more important that you can't trigger the link by
> pressing "A". An onkeypress handler should check which key was pressed.
>
>
Received on Friday, 4 July 2003 08:11:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:10 GMT